Incaseof 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 thecolourofthecomponentdoes not change to green on startup. In order to avoid this, it is necessary to add the following security permission in java.policy file under {JRE_HOME}/lib/security.
Code Block
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 jmsThisisduetojavax.jmspackageconflictpresentinbothweblogicjarsandjms-2.0.jar used by Fiorano. To avoid this, wljmsclient.jar and wlthint3client.jar has to jarhasto be updated with the classes in javax.jms package of jmswiththeclassesinjavax.jmspackageofjms-2.0 jar by following these steps:
Copy jmsCopyjms-2.0.jar present in %FIORANO_HOME%/extlib/jms to any location and jmstoanylocationand extract the contents of jar using the following command:
Code Block
jar xf jms-2.0.jar
Update javaxUpdatejavax.jms package jmspackage classes in wljmsclient.jar with the above-extracted classes using the command " jar uf wljmsclientjarufwljmsclient.jar -C %EXTRACTED_PATH% javaxPATH% javax/jms/* " from command prompt where %EXTRACTED_PATH% is the location where jmsisthelocationwherejms-2.0.jar is extracted. Similarly, wlthint3client.jar has to be updated.