SOABook

in this post I will explain use of preferences and how to use preferences in BPEL. for changing value of preferences from em console please check in previous post  Click here Preferences are variables, we can  change these variable values while deploying to another environment with out changing code and we can modify value of these variable run time from em console. step1:    how to create prefernce variable.    open composite.xml file in source mode.     add  <property name="bpel.preference. JMSHeader ">CustomJMSHeader</property> in side component element . Here  JMSHeader is variable name. you can change as per requirement. Step 2:     how to access preference variable.       use   ora:getPreference() function from BPEL Xpath Extension Functions.

To stop consumption of messages from queue. we can set below  settings in weblogic console. method1: Step 1:    Navigate to the queue from where consumption needs to stop.    JMS module --->JMS queue   Step 2:    select the queue and expand advanced option in configuration -->general tab Step 3:      Check the check box   Pause Message Consumption at Startup . Step 4:     Restart the server to effect the changes. Method2: follow below path: JMs server--> your queue target server --->  monitoring ---> active destinations select your particular queue/topic, set Production Paused property to true.

Issue: Error while connecting to JMS Queue/Topic Exception occurred when binding was invoked. Exception occurred during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. DOMAIN: JMSQueuetest:JMSProduce [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141 ERRJMS_CONN_FAC_NOT_FOUND. ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory jms/TestConnectionFactory neither through JNDI nor instantiate it as a Java class. Please examine the log file to determine the problem. Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit ...