I'm using ReportCaster Legacy API's on another Linux OS server to run reports on our Web Focus server. Every report is working except one and I need tips on how to debug this.

This is the output I normally get on a successful run...

 
LinuxOSserver:~ # CLASSPATH=/opt/sqljdbc_4.1/enu/jre7/sqljdbc41.jar:/opt/ibi/WebFOCUS82/ReportCaster/lib/reportcaster.jar:/usr/java/jdk1.8.0_181/bin:/opt/ibi/WebFOCUS82/ReportCaster/samples/Tools/CompiledCode /usr/java/jdk1.8.0_181/bin/java HLZ_WFSchedulerRunWithID Sb71a8a22sabb2s4d45sa647s3b1ff8e59062
2019-03-26 09:55:54   ScheduleId1=Sb71a8a22sabb2s4d45sa647s3b1ff8e59062
2019-03-26 09:55:55   ScheduleId2=Sb71a8a22sabb2s4d45sa647s3b1ff8e59062
2019-03-26 09:55:55   Schedule=ibi.broker.api.data.schedule.Schedule@17fbfb02
2019-03-26 09:55:55   JobId=J365a60fbjd759j4158ja574j068c12b179a1
HLZ_WFSchedulerRunWithID OK

This is the output I get on one report that keeps failing and we can't figure out why
What more can I do from a command line to try and troubleshoot this? Any trace/debug modes I can learn to enable to see more verbose information as to what's happening?
It's failing on this step where it generates or pulls the JobID

		// run schedule
		String jobId = manager.run(schedule);
		print("JobId=" + jobId);

+ CLASSPATH=/opt/sqljdbc_4.1/enu/jre7/sqljdbc41.jar:/opt/ibi/WebFOCUS82/ReportCaster/lib/reportcaster.jar:/usr/java/jdk1.8.0_181/bin:/opt/ibi/WebFOCUS82/ReportCaster/samples/Tools/CompiledCode
+ /usr/java/jdk1.8.0_181/bin/java HLZ_WFSchedulerRunWithID S1923faeesd758s4e43s8946s32d82261a5e6
HLZ_WFSchedulerRunWithID START
No bundle found
log4j:WARN No appenders could be found for logger (stdout).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
2019-03-26 08:27:59   ScheduleId1=S1923faeesd758s4e43s8946s32d82261a5e6
2019-03-26 08:27:59   ScheduleId2=S1923faeesd758s4e43s8946s32d82261a5e6
2019-03-26 08:27:59   Schedule=ibi.broker.api.data.schedule.Schedule@4e48462d
java.lang.NullPointerException
        at ibi.broker.api.util.converter.ScheduleConverterUtil.convertTaskList(ScheduleConverterUtil.java:1559)
        at ibi.broker.api.util.converter.ScheduleConverterUtil.convert(ScheduleConverterUtil.java:1596)
        at ibi.broker.api.util.converter.ScheduleConverter.getObject(ScheduleConverter.java:1352)
        at ibi.broker.api.cci.interactive.schedule.RunSchedule.processRequest(RunSchedule.java:142)
        at ibi.broker.api.cci.interactive.AbstractInteractive.execute(AbstractInteractive.java:225)
        at ibi.broker.api.cci.interactive.schedule.ScheduleManagerImpl.run(ScheduleManagerImpl.java:228)
        at ibi.broker.api.cci.interactive.schedule.ScheduleManagerImpl.run(ScheduleManagerImpl.java:217)
        at HLZ_WFSchedulerRunWithID.<init>(HLZ_WFSchedulerRunWithID.java:47)
        at HLZ_WFSchedulerRunWithID.main(HLZ_WFSchedulerRunWithID.java:72)
HLZ_WFSchedulerRunWithID FAIL

This message has been edited. Last edited by: FP Mod Chuck,

gsbrown

I don't have any experience with debugging the API. I looked at the manual and it doesn't have info for that either. I suggest you open a case with techsupport.

The old api is set up to use Log4j. You need to setup an appender. If you are running it in the command line you can put your log4j.xml into the same directory where your running from. The following is a sample appender that will dump the traces out to a file and the console.

 <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration debug="true" xmlns:log4j='http://jakarta.apache.org/log4j/'>
	<appender name="console" class="org.apache.log4j.ConsoleAppender">
		<param name="Target" value="System.out"/>
		<layout class="org.apache.log4j.PatternLayout">
			<param name="ConversionPattern" value="%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n" />
		</layout>
	</appender>
 
	<appender name="fileAppender" class="org.apache.log4j.RollingFileAppender">
		<param name="File" value="C:/Client_Info/BI/BMO/Harris/webapps/logs/harris-application.log"/>
		<layout class="org.apache.log4j.PatternLayout">
			<param name="ConversionPattern" value="%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n" />
		</layout>
	</appender>
 
	<root>
		<priority value="trace"></priority>
		<appender-ref ref="console"></appender-ref>
		<appender-ref ref="fileAppender"></appender-ref>
	</root>
</log4j:configuration> 

Oh, thank you! That log4j setup is exactly what I needed to see more information. I'll be able to use this information to better work with support. We think this issue is related to a new "dependency" feature available in the latest WF release that's being used with this particular schedule

2019-03-29 10:01:59 TRACE AbstractInteractive:227 - Exiting: execute()
2019-03-29 10:01:59 TRACE AbstractInteractive:228 - return = ibi.broker.api.data.schedule.Schedule@b8a144e
2019-03-29 10:01:59 TRACE ScheduleManagerImpl:70 - Exiting: getSchedule(String)
2019-03-29 10:01:59 TRACE ScheduleManagerImpl:71 - return = ibi.broker.api.data.schedule.Schedule@b8a144e
2019-03-29 10:01:59   ScheduleId3=S1923faeesd758s4e43s8946s32d82261a5e6
2019-03-29 10:01:59   Schedule=ibi.broker.api.data.schedule.Schedule@b8a144e
2019-03-29 10:01:59 TRACE ScheduleManagerImpl:223 - Entering: run(Schedule, JobOptions)
2019-03-29 10:01:59 TRACE ScheduleManagerImpl:224 - schedule = ibi.broker.api.data.schedule.Schedule@b8a144e
2019-03-29 10:01:59 TRACE ScheduleManagerImpl:225 - jobOptions = null
2019-03-29 10:01:59 TRACE AbstractInteractive:108 - Entering: init()
2019-03-29 10:01:59 TRACE AbstractInteractive:112 - Exiting: init()
2019-03-29 10:01:59 TRACE AbstractInteractive:113 - return = void
2019-03-29 10:01:59 TRACE AbstractInteractive:212 - Entering: execute()
2019-03-29 10:01:59 TRACE AbstractInteractive:221 - Start input data validation...
2019-03-29 10:01:59 TRACE RunSchedule:106 - Entering: dataCheck()
2019-03-29 10:01:59 TRACE RunSchedule:109 - Exiting: dataCheck()
2019-03-29 10:01:59 TRACE RunSchedule:110 - return = void
2019-03-29 10:01:59 TRACE AbstractInteractive:224 - Start processing request...
2019-03-29 10:01:59 TRACE RunSchedule:121 - Entering: processRequest()
2019-03-29 10:01:59 TRACE AbstractInteractive:282 - Entering: getIBFSSessionId()
2019-03-29 10:01:59 DEBUG AbstractInteractive:293 - sid: 7ac579e71fc50489c3896d9f79867f6cfaaea38a20fdd134c97c5eead8c1bf28
2019-03-29 10:01:59 TRACE AbstractInteractive:295 - Exiting: getIBFSSessionId()
2019-03-29 10:01:59 TRACE AbstractInteractive:296 - return = '7ac579e71fc50489c3896d9f79867f6cfaaea38a20fdd134c97c5eead8c1bf28'
2019-03-29 10:01:59 TRACE CreateScheduleConverter:121 - Call createIBFSCasterObject
2019-03-29 10:01:59 TRACE ScheduleConverter:1344 - Entering: getObject(Object)
2019-03-29 10:01:59 TRACE ScheduleConverter:1345 - apiValue = ibi.broker.api.data.schedule.Schedule@b8a144e
2019-03-29 10:01:59 TRACE CASTER_IDUtil:98 - typeString: P
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:1584 - Entering: convert()
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:486 - Entering: convertGeneralData()
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:522 - Exiting: convertGeneralData()
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:523 - return = void
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:529 - Entering: convertNotification()
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:540 - Exiting: convertNotification()
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:541 - return = void
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:1014 - Entering: convertTimeInfoList()
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:1052 - Entering: convertTimeInfo(TimeInfo, CASTER_Interval)
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:1196 - Exiting: convertTimeInfo(TimeInfo, CASTER_Interval)
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:1197 - return = void
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:1046 - Exiting: convertTimeInfoList()
2019-03-29 10:01:59 TRACE ScheduleConverterUtil:1543 - Entering: convertTaskList()
java.lang.NullPointerException
        at ibi.broker.api.util.converter.ScheduleConverterUtil.convertTaskList(ScheduleConverterUtil.java:1559)
        at ibi.broker.api.util.converter.ScheduleConverterUtil.convert(ScheduleConverterUtil.java:1596)
        at ibi.broker.api.util.converter.ScheduleConverter.getObject(ScheduleConverter.java:1352)
        at ibi.broker.api.cci.interactive.schedule.RunSchedule.processRequest(RunSchedule.java:142)
        at ibi.broker.api.cci.interactive.AbstractInteractive.execute(AbstractInteractive.java:225)
        at ibi.broker.api.cci.interactive.schedule.ScheduleManagerImpl.run(ScheduleManagerImpl.java:228)
        at ibi.broker.api.cci.interactive.schedule.ScheduleManagerImpl.run(ScheduleManagerImpl.java:217)
        at HLZ_WFSchedulerRunWithID.<init>(HLZ_WFSchedulerRunWithID.java:47)
        at HLZ_WFSchedulerRunWithID.main(HLZ_WFSchedulerRunWithID.java:72)
HLZ_WFSchedulerRunWithID FAIL

This message has been edited. Last edited by: gsbrown,