...
| Note |
|---|
- If these jars are added to resources of the System library JMSAdapters, the jars are available for all JMS components. Refer to the Add Resources to a Microservice section.
- In case of BEA Weblogic, InitialContext can be created by specifying empty values for JNDI Username and JNDI password as well.
- When configuring JMSIn 4.0 for BEA Weblogic in scheduling mode,the colour of the component does not change to green on startup. In order to avoid this, it is necessary to add following security permission in java.policy file under {JRE_HOME}/lib/security >.The permission to be added is "grant { permission javax.management.MBeanTrustPermission "register";} "
- After adding BEA Weblogic jars as resources, if we try to configure the component for Topic destination type in Fiorano MQ provider, test in Interactions configuration page of CPS will fail with java.lang.NoSuchMethodError. This is due to javax.jms package conflict present in both weblogic jars and jms-2.0.jar used by Fiorano. To avoid this, wljmsclient.jar and wlthint3client.jar has to be updated with the classes in javax.jms package of jms-2.0 jar by following these steps:
- Copy jms-2.0.jar present in %FIORANO_HOME%/extlib/jms to any location and extract the contents of jar using the command "jar xf jms-2.0.jar" from command prompt.
- Update javax.jms package classes in wljmsclient.jar with the above extracted classes using the command " jar uf wljmsclient.jar -C %EXTRACTED_PATH% javax/jms/* " from command prompt where %EXTRACTED_PATH% is the location where jms-2.0.jar is extracted. Similarly wlthint3client.jar has to be updated.
|
...
Configure the JMSIn as described in Configuration and Testing section and use feeder and display component to send sample input and check the response respectively.
...