NoInitialContextException when re-submitting a message using command line

Question

Hello,
I am trying to re-submit an application message, following discussion in section 18 of the user guide. The command and the exception are shown below., Basically, I am getting a jndi exception. What am I missing / not doing right?
C:\Oracle\Middleware\jdev_home\jdeveloper\ant\bin\ant -f "C:\Oracle\Middleware\11g_home\Oracle_SOA1\bin\ant-b2b-util.xml" b2bresubmit -Ddirection=outbound -Dmsgsource=appMsg -Dmsgid=2d383837363839393330363531393933 -DpayloadPath="BusMsg_Payload_2d383837363839393330363531393933.txt"
Buildfile: C:\Oracle\Middleware\11g_home\Oracle_SOA1\bin\ant-b2b-util.xml
b2bresubmit:
weblogic_dependencies:
[echo]
[echo] Weblogic server location: C:\Oracle\MIDDLE~1\11g_home\WLSERV~1.3
[echo] JNDI properties folder location: C:\Oracle\Middleware\11g_home\Oracle_SOA1\bin
[echo]
utility:
[echo]
[echo] java.naming.provider.url=${java.naming.provider.url}
[echo] java.naming.factory.initial=${java.naming.factory.initial}
[echo] java.naming.security.principal=${java.naming.security.principal}
[echo] java.naming.security.credentials=*****
[echo]
[echo]
[echo] args=resubmit ${propfile}
[echo]
[java] Commandline arguments 2: [resubmit, ${propfile}]
[java] Exception in thread "main" javax.naming.NoInitialContextException: Need to specify class name in environment or system p
roperty, or as an applet parameter, or in an application resource file: java.naming.factory.initial
[java] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
[java] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
[java] at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)
[java] at javax.naming.InitialContext.lookup(InitialContext.java:392)
[java] at oracle.tip.b2b.utility.B2BCommandLineUtility.getB2BUtility(B2BCommandLineUtility.java:197)
[java] at oracle.tip.b2b.utility.B2BCommandLineUtility.resubmitMessage(B2BCommandLineUtility.java:1249)
[java] at oracle.tip.b2b.utility.B2BCommandLineUtility.main(B2BCommandLineUtility.java:786)
[java] Java Result: 1
BUILD SUCCESSFUL
Total time: 6 seconds
C:\Oracle\Middleware\11g_home\user_projects\domains\single_server_domain>

Answer 1

Thanks, Anuj.
Indeed I did not read 18.1. Now I have.
18.1 uses Unix syntax, the Windows syntax (where I am working) would look like that shown below, where JDK location will naturally vary and the middleware home may be different:
set ORACLE_HOME=C:\Oracle\Middleware\11g_home\Oracle_SOA1
set ANT_HOME=%ORACLE_HOME%\..\modules\org.apache.ant_1.7.1
set JAVA_HOME=C:\jdk1.6.0_20
The one-off jndi properties generation will be as shown in teh manual however it would see that teh port number of the weblogic server may need to be changed as well as the weblogic password - for me it was generated as 8001 whwere my weblogic server actually runs on 7001
@REM create once off jndi proprties
cd %ORACLE_HOME%\bin
ant -f ant-b2b-util.xml b2bcreate-prop
@rem Edit the jndi.properties file to include the weblogic password and fix weblogic port number
To submit a "repaired" applicaiton message one would do:
@rem run the utility - must have absolute path to message file!
set ORACLE_HOME=C:\Oracle\Middleware\11g_home\Oracle_SOA1
set ANT_HOME=%ORACLE_HOME%\..\modules\org.apache.ant_1.7.1
set JAVA_HOME=C:\jdk1.6.0_20
%ANT_HOME%\bin\ant -f %ORACLE_HOME%\bin\ant-b2b-util.xml b2bresubmit ^
-Dmsgid=2d373838303530333432393931303931 ^
-Dmsgsource=APPMSG ^
-Ddirection=OUTBOUND ^
-Dpayloadpath=C:\hl7\repair\AppMsg_Payload_2d373838303530333432393931303931.txt
It is critical to make sure the absolute path to the repaired message file is provided otherwise null pointer exceptions will be had even if the command is executed from the directory in which the messge file is located.
Another thing that will trip the beginner is the Message ID. The Message ID that is needed is that shown all over the place as MSG_ID or as b2b.messageId, which are the same. In the B2B Web Console this message ID will be shown in "application Message" tab of teh "reporting" facility, when one clicks the "details" "button" and looks at b2b.messageId property value. It is also shown as "Message Id" in teh details of teh business message. It would be nice if one could see this applicaitn message id in teh applicaiton messages report but I guess one can't have everything.
One also gets to know what the applicatin message Id is when one "downloads" the payload of the application message. The file name, which will be provided as default, will have the message id embedded - nice and easy :-) AppMsg_Payload_2d373838303530333432393931303931.txt
Thanks again
Michael