You have to enable only INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory. It seems your PROVIDER_URL has issue. Please remove existing folder given for provider url and create folder like C:/JNDI-Directory. After that change as PROVIDER_URL=file:/C:/JNDI-Directory.
On Sat, Jan 16, 2016 at 3:08 PM, Indrajith Udayakumara <aiukum...@gmail.com> wrote: > Here I followed the same way as in your description > Should I un-comment all the INITIAL_CONTEXT FACTORIES ? > Here I did only the highlighted line. > > > > After I save this and run *IVTSetup.bat* in administrator mode > the following message comes, and the problem exists. > > > > Thank you > Indrajith > > On Sat, Jan 16, 2016 at 10:46 AM, Indika Sampath <indi...@wso2.com> wrote: > >> Hi Indrajith, >> >> Sometime ago I've configured WSMQ 7.x. Below steps followed up to >> configure. Please cross check with you setup. >> >> 1. Start ‘IBM WebSphere MQ Explorer, create a new queue manager. Make >> that queue manager as default by clicking the check-box "make this the >> default queue manager". Leave default values for the other fields. >> Queue Manager -> New -> Queue Manager >> Queue manager name: MyQueueMgr >> >> 2. Select the created Queue manager and expand the list. Create a new >> local queue. Leave default values for the other fields. >> Queue -> New -> Local Queue… >> Name: Queue1 >> >> 3. Expand Advanced sub tree and add a server-connection channel. Leave >> default values for the other fields. >> Channel -> New -> Server-connection Channel… >> Name: MyChannel >> >> LISTENER.TCP will added to the Listeners directory by default. >> >> 4. Navigate to [WebSphere MQ Home]\java\bin directory, open >> 'JMSAdmin.config' file and edit the file as follows: >> Uncomment the configuration for INITIAL_CONTEXT_FACTORY >> Ex: INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory >> Point to an empty folder for PROVIDER_URL >> Ex: PROVIDER_URL=file:/C:/JNDI-Directory >> >> 5. Navigate to [WebSphere MQ Home]\java\bin directory, create the default >> set of JNDI bindings by running the following command in the command prompt. >> IVTSetup.bat >> >> NOTE: Please execute above command in command prompt open by Run as >> Administrator >> >> 6. We have now enabled and verified JNDI support. Let's use the JMSAdmin >> tool to make some modifications in the JNDI bindings. Navigate to >> [WebSphere MQ Home]\java\bin from the console and start jmsadmin by running >> the following command: >> JMSAdmin.bat >> >> Run the following commands: >> ALTER QCF(ivtQCF) TRANSPORT(CLIENT) >> ALTER QCF(ivtQCF) QMGR(MyQueueMgr) >> DEFINE Q(MyQueue) QMGR(MyQueueMgr) QUEUE(Queue1) >> >> Run following command to verify configuration. >> DISPLAY CTX >> >> Run following command to quit JMSAdmin.bat >> END >> >> IBM MQ configuration complete. >> >> With regard to question you raised about IVTRun.bat (IVT stands for >> Initial Verification Test as I remember), you cannot just run IVTRun.bat. >> There are set of flags you have to pass depending on the configuration. >> WSMQ offer this utility to verify your configuration works fine. >> >> You can run IVTRun.bat as below once you done with step 3. >> >> IVTRun.bat -nojndi -client -m MyQueueMgr -host localhost -channel >> MyChannel >> >> Cheers! >> >> On Sat, Jan 16, 2016 at 10:17 AM, Indrajith Udayakumara < >> aiukum...@gmail.com> wrote: >> >>> After configuring ESB 4.9 with WebSphere MQ according to the steps here >>> >>> https://docs.wso2.com/display/ESB490/Configure+with+IBM+WebSphere+MQ >>> >>> the IVRun.bat shows nothing on the command prompt. >>> (both WSMQ and CMD were run as Administrator) >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Indika Sampath >> Senior Software Engineer >> WSO2 Inc. >> http://wso2.com >> >> Phone: +94 716 424 744 >> Blog: http://indikasampath.blogspot.com/ >> >> > -- Indika Sampath Senior Software Engineer WSO2 Inc. http://wso2.com Phone: +94 716 424 744 Blog: http://indikasampath.blogspot.com/
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
