JMS configuration for clustring

          Hi,
          I have a JMS.ear, having jms.war, jms-ejb.jar.
          I need to deploy it for clustered environment.
          So how to set the targets? what changes needs to be made in the config.xml to incorporate
          this.
          I am using PUB/SUB type of JMS model.
          Any pointers ??
          - tia
          Regards
          Sam
          

As for the configuration by the Production Admins, our infrastructure guys use weblogic templates (and god know whatever custom scripts). Therefore they use the same weblogic template in Dev, QA and Production. Configure once and deploy multiple times.
          Don't know the exact nature of you applications..who is sending the msg to the topic and who is receiving (your own application or another application). But we have a simple JMS queue on a cluster of 4 servers and MDBs deployed on all 4. Therefore the MDBs listen to the Queue on their own server. It's pretty HA and never had an issue for it. Our prod monitoring group watch the logs and if there is a problem on a specific server, they just restart it and it picks off where it left off.
          Later...
          - Wayne

Similar Messages

  • Configuring JMS adapter for a BPEL process which puts a msg in a Q of MQ

    Hi,
    I am trying to develop a BPEL process which picks up a message from a Q in Websphere MQ and puts that message in another Q of MQ after processing that.
    I have updated the oc4j-ra.xml with the following inputs:
    <connector-factory location="eis/MQSeries/Queue" connector-name="Jms Adapter">
              <config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
              <config-property name="factoryProperties" value="QueueManager=TestManager;TransportType=1;Hostname=machine's ip address;Port=1414;Channel=channel name for connecting to client"/>
              <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
              <config-property name="isTopic" value="false"/>
              <config-property name="isTransacted" value="true"/>
              <config-property name="username" value="admin"/>
              <config-property name="password" value="welcome"/>
         </connector-factory>
    But while testing the BPEL process, I get the error:
    <remoteFault>
    <part name="code" >
    <code>null</code>
    </part>
    <part name="summary" >
    <summary>file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. ; nested exception is: ORABPEL-12511 Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console. </summary>
    </part>
    <part name="detail" >
    <detail>null</detail>
    </part>
    </remoteFault>
    Can anyone tell me what has gone wrong in setting the connection factory for the Q or what else I have to configure to sort out this problem?
    Thanks,
    Jayatu

    I am experiencing the exact same issue while configuring for Tibco EMS!!!
    I have also checked the oc4j-xa.xml file etc and I am also unable to find any guidance on the steps required from XML config files through to adapter wizard entries!

  • How to configure for remote JMS client?

    I have my own Java JMS test program for performance measurements.
              I am using the JNDI and JMS provider functionality of the WebLogic 9.1 app-server but my test program is just pure JMS 1.02 sender/receiver clients - ie it is NOT part of, or deployed as a J2EE application.
              SINGLE MACHINE TEST
              ===================
              In a single machine environment I was able to
              - configure a JMSServer
              - configure a JMSSystemModule
              - configure resources for ConnectionFactories and Queue and Topics
              I then made what I believe to be a 'standalone' application module copied from some mysystemmodule-jms.xml and with that I somehow worked out how to deploy it using the weblogic.Deployer tool.
              The deployment apparently set up the JNDI and my JMS client could gain access to the administered objects and do what it does.
              Everything works.
              TWO MACHINE TEST
              ================
              I now have a second machine.
              I want to put my JMS sender client on this new machine and I want the JMS server and JMS receiver client to be unchanged from the SINGLE MACHINE TEST.
              But I really don't know quite how to proceed from here...
              Do I need to install the WebLogic app-server on the sender machine or is the weblogic.jar all I need?
              What is necessary configuration for JNDI access on the sender machine?
              Can I in fact use my original SINGLE MACHINE server unchanged as I am hoping?
              I don't think I want a "thin" client because I read that performance is impacted (and these are performance tests)
              Remember this is NOT a J2EE application. There is no MDB; no client-container; no descriptors etc. Maybe that makes it more complicated - I don't know.
              Sorry for such basic questions but if somebody can just point me to an appropriate example or tutorial it could save me days...
              Thankyou.

    Hi,
              My problem is on similar lines. I have an applet based UI working on RMI/t3 protocol.
              I am using weblogic 9.2 as my app server.
              When my applet is executed on JRE 1.5x it works fine.
              But when I use JRE1.4x it gives the following exception
              java.lang.NoClassDefFoundError: javax/management/InvalidAttributeValueException
              at weblogic.rmi.internal.Stub.<clinit>(Stub.java:21)
              at java.lang.Class.forName0(Native Method)
              at java.lang.Class.forName(Class.java:141)
              at weblogic.rmi.internal.StubInfo.class$(StubInfo.java:34)
              at weblogic.rmi.internal.StubInfo.<clinit>(StubInfo.java:34)
              at java.lang.Class.forName0(Native Method)
              I have analyzed the reason for this.
              the class javax/management/InvalidAttributeValueException was included in java 1.5 and above. So JRE 1.4 does not have it.
              In previous versions of weblogic this class was a part of their 'weblogic.jar' file and in weblogic 9.2 it is not a part of weblogic.jar file so when I am using JRE1.4 and weblogic 9.2 then it obviously does not find this class hence the above exception.
              I tried to put this all together and made custom made client jar file incliding the necessary classes. I was able to get throght this exception only land up in following exception.
              java.lang.VerifyError: class weblogic.utils.classloaders.GenericClassLoader overrides final method .
                   at java.lang.ClassLoader.defineClass0(Native Method)
                   at java.lang.ClassLoader.defineClass(Unknown Source)
                   at java.security.SecureClassLoader.defineClass(Unknown Source)
                   at sun.applet.AppletClassLoader.findClass(Unknown Source)
                   at java.lang.ClassLoader.loadClass(Unknown Source)
                   at sun.applet.AppletClassLoader.loadClass(Unknown Source)
                   at java.lang.ClassLoader.loadClass(Unknown Source)
                   at java.lang.ClassLoader.loadClassInternal(Unknown Source)
                   at weblogic.jndi.WLInitialContextFactoryDelegate.<clinit>(WLInitialContextFactoryDelegate.java:204)
                   at weblogic.jndi.spi.EnvironmentManager$DefaultFactoryMaker.<clinit>(EnvironmentManager.java:26)
                   at weblogic.jndi.spi.EnvironmentManager.getInstance(EnvironmentManager.java:48)
                   at weblogic.jndi.Environment.getContext(Environment.java:307)
                   at weblogic.jndi.Environment.getContext(Environment.java:277)
                   at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
                   at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
                   at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
                   at javax.naming.InitialContext.init(Unknown Source)
                   at javax.naming.InitialContext.<init>(Unknown Source)
              I really need to support clients using Jre 1.4 and Jre 1.5
              I will really appreciate any help on this one.
              Please advise.
              Thank you all.

  • Sender JMS adapter configuration for IBM MQSeries

    Dear All,
    i am doing a IBM MQSeries 5.2.x Message ->sender JMS adapter -> XI server -> receiver RFC adapter -> R/3.
    i have deployed the JMS adapter with the required jar files of IBM MQSeries 5.2.x in XI server.
    in Sender JMS adapter configuration for IBM MQSeries 5.2.x, i have put following data:
    1. Transport Protocol: Websphere MQ - is it okay?
    in JMS provider settings:
    2. in channel name - what should be there?
    3. Transport Network protocol should be TCP/IP or WebsphereMQ - how to decide this thing.
    4. JMS Complaint - whether WebsphereMQ or JMS API.
    in JMS Settings:
    5. JMS Queue user - is this IBM MQSeries 5.2.x Queue User or someother user?
    6. JMS Message Selector - what data to take here.
    So if anybody has connected IBM MQSeries 5.2.x to XI via JMS adapter, please answer my above queries.
    Regards,
    Rajeev Gupta

    Hi Swaroop,
    you can send me those documents at my gmail-id : [email protected]
    Hi All,
    one more question - to connect XI server to IBM MQSeries via JMS adapter in ID, do we need to have a MQSeries Client installed on XI server - or - just by configuring JMS adapter, we can send messages from IBM MQSeries to XI server without any MQSeries client on XI server?
    Why Channel name is required in JMS configuration data?
    Thanks,
    Rajeev Gupta

  • Error: Invalid configuration for the JMS adapter

    Hi!
    I'm doing a test with CEP to get messages from a JMS WebLogic queue but I'm getting the following error:
    <BEA-2045010> <The application context "Teste" could not be initialized: org.springframework.beans.FatalBeanException: Error in initialization context lifecycle; nested exception is java.lang.IllegalArgumentException: Invalid configuration for the JMS adapter, you must Bean or specify a converter or a type of event.
    Teste.context.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:osgi="http://www.springframework.org/schema/osgi"
    xmlns:wlevs="http://www.bea.com/ns/wlevs/spring"
    xmlns:jdbc="http://www.oracle.com/ns/ocep/jdbc"
    xmlns:spatial="http://www.oracle.com/ns/ocep/spatial"
    xsi:schemaLocation="
    http://www.springframework.org/schema/beans
    http://www.springframework.org/schema/beans/spring-beans.xsd
    http://www.springframework.org/schema/osgi
    http://www.springframework.org/schema/osgi/spring-osgi.xsd
    http://www.bea.com/ns/wlevs/spring
    http://www.bea.com/ns/wlevs/spring/spring-wlevs-v11_1_1_3.xsd
    http://www.oracle.com/ns/ocep/jdbc
    http://www.oracle.com/ns/ocep/jdbc/ocep-jdbc.xsd
    http://www.oracle.com/ns/ocep/spatial
    http://www.oracle.com/ns/ocep/spatial/ocep-spatial.xsd">
         <wlevs:event-type-repository>
              <wlevs:event-type type-name="Pet">
                   <wlevs:class>testewithprotobuf.MyPet$Pet</wlevs:class>
              </wlevs:event-type>
         </wlevs:event-type-repository>
         <wlevs:adapter id="pet_messageAdapter" provider="jms-inbound">
              <wlevs:listener ref="pet_inputChannel" />
              <wlevs:instance-property name="converterBean"
                   ref="PetMessageConverter" />
         </wlevs:adapter>
         <wlevs:channel id="pet_inputChannel" event-type="Pet">
              <wlevs:listener ref="pet_messageProcessor" />
         </wlevs:channel>
         <bean id="PetMessageConverter" class="testewithprotobuf.PetMessageConverter" />
         <bean id="PetBean" class="testewithprotobuf.PetBean" />
         <wlevs:processor id="pet_messageProcessor">
              <wlevs:listener ref="pet_outputChannel" />          
         </wlevs:processor>
         <wlevs:channel id="pet_outputChannel" event-type="Pet">
              <wlevs:listener ref="PetBean" />
         </wlevs:channel>
    </beans>
    My converter class:
    import java.util.Collections;
    import java.util.List;
    import javax.jms.BytesMessage;
    import javax.jms.JMSException;
    import javax.jms.Message;
    import testewithprotobuf.MyPet.Pet;
    import com.bea.wlevs.adapters.jms.api.InboundMessageConverter;
    import com.bea.wlevs.adapters.jms.api.MessageConverterException;
    import com.google.protobuf.InvalidProtocolBufferException;
    public class PetMessageConverter implements InboundMessageConverter {
         @SuppressWarnings("rawtypes")
         @Override
         public List convert(Message message) throws MessageConverterException,
                                                                JMSException {
              BytesMessage bytesMessage = (BytesMessage) message;
              long bodyLen = bytesMessage.getBodyLength();
              byte[] buffer = new byte[(int) bodyLen];
              bytesMessage.readBytes(buffer);
              try {
                   Pet pet = Pet.parseFrom(buffer);               
                   return Collections.singletonList(pet);
              } catch (InvalidProtocolBufferException e) {
                   throw new MessageConverterException(e);
    Please, what's wrong?
    Thanks!

    This error usually indicates that you have both event type and converter bean specified or neither specified. In your case, that doesn't appear to the case from looking at the spring file. Could you also paste the contents of your configuration file from META-INF/wlevs directory?

  • Configuration for JMS Adapter Sensor action and JMS Queue sensor action..!!

    Hi,
    Id like my BPEL process to send an XML message to JMS on Websphere,I was able to do this through a JMS adapter.But I would more like to add sensors into my process which would really do the same thing - send an XML message to JMS Q.
    Now I understand that there are two ways to do this,JMS Queue and JMS Adapter - thorugh bpel sensor action.
    I am able to use JMS Queue and it works fine , but adds its own xml tags to the message,Is there any way I could send only my xml payload as a message to the queue??
    Also could any1 tell me what is the configuration for JMS Adapter sensor action?
    Any suggestions how do I go about it??

    Hey Anirudh,
    Thanx for the response :-)
    All these hold good when I have an AQ adaptor right,But the thing is I want to send a message to a 'JMS' queue with out actually using an adapter configuration wizard and everythng..So I resolved to JMS queue Sensor action..Heres the xml snippet from the sensorAction.xml files which is generated..
    <actions targetNamespace="http://xmlns.oracle.com/Test_JMS_Logging" xmlns="http://xmlns.oracle.com/bpel/sensor" xmlns:tns="http://xmlns.oracle.com/Test_JMS_Logging" xmlns:pc="http://xmlns.oracle.com/bpel/sensor">
    <action name="JMS_LogEntry" publishName="" publishType="JMSQueue" enabled="true" filter="" publishTarget="jms/L_Queue">
    <property name="JMSConnectionFactory">jms/L_QueueCF</property>
    <sensorName>ActivitySensor_JMS</sensorName>
    </action>
    </actions>
    This works grt and adds messages to the queue..But adds its own header info according to the sensor.xsd loacted at the Oracle_home\bpel\system\xmllib\ folder.
    Right now the XML message added to the Queue is:-
    <actionData xmlns="http://xmlns.oracle.com/bpel/sensor">
    <header>
    <sensor sensorName="ActivitySensor_JMS" classname="oracle.tip.pc.services.reports.dca.agents.BpelActivitySensorAgent" kind="activity" target="AddLEntr
    y" xmlns:pc="http://xmlns.oracle.com/bpel/sensor" xmlns:ns2="http://www.ulrhome.com/2008/10/L_Entry" xmlns:tns="http://xmlns.oracle.com/Test_JMS">
    <activityConfig evalTime="completion">
    <variable outputDataType="string" outputNamespace="http://www.w3.org/2001/XMLSchema" target="$WriteL_Produce_Message_InputVariable/L_Entry/ns2:L_Entry/ns2:LCName"/>
    </activityConfig>
    </sensor>
    <instanceId>950016</instanceId>
    <processName>Test_JMS</processName>
    <processRevision>v2009_04_15__40833</processRevision>
    <domain>default</domain>
    <timestamp>2009-04-15T11:21:23.596-04:00</timestamp>
    <midTierInstance>app01.ulrhome.com:9700</midTierInstance>
    </header>
    <payload>
    <activityData>
    <activityType>scope</activityType>
    <evalPoint>completion</evalPoint>
    <durationInSeconds>0.011</durationInSeconds>
    <duration>PT0.011S</duration>
    </activityData>
    <variableData>
    <dataType>12</dataType>
    <data>
    <ns0:LCName xmlns:ns0="LC_Test1http://www.ulrhome.com/2008/10/L_Entry">LC_Test1</ns0:LCName>
    </data>
    <queryName/>
    <target>$WriteL_Produce_Message_InputVariable/L_Entry/ns2:L_Entry/ns2:LCName</target>
    <updaterName>AddL_Entry</updaterName>
    <updaterType>scope</updaterType>
    </variableData>
    </payload>
    </actionData>
    My requirement is that I need to add a sensor to the BPEL process which posts 'Only my payload message to the JMS queue'..
    What I would want the message in the Queue to be is : -
    <data>
    <ns0:LCName xmlns:ns0="LC_Test1http://www.ulrhome.com/2008/10/L_Entry">LC_Test1</ns0:LCName>
    </data>
    Also while creating a Sensor action I get another option as JMS Adaptor,I am not sure of what value to type in this wizard..Heres what I keyed in..M sure this is not right..Cos it dosnt work :-)
    <action name="SensorAction_JMS" publishName="" publishType="JMSAdapter" enabled="true" filter="" publishTarget="jms/LoggingQueue">
    <property name="JMSConnectionName">Log</property>
    </action>
    </actions>
    Could any 1 tel me what values are the right values..And does JMS Adapter mean that I have to create a JMS Apator in the project and give that connection name as a Value..
    I am not finding sufficiant Documentation for 'JMS Adapter' so M clueless and right now any help will be appriciated :-)
    Regards,
    Akshatha.

  • JMS configuration problem log file

    Hello,
    My purpose is to send xml data from MQSeries to BW using XI. MQSereies is installed in XI server. For thah I am trying to configure JMS adpter for MQSeries in XI. I have successfully deployed the necessary external drivers using SDM. I have configured the sender channel with the following parameters.
    Adapter type: JMS
    Transport Protocol :WEBsphereMQ(non-JMS)
    Message protocol :JMS1.x
    Queue connection factory java class:com.ibm.mq.jms.MQQueueConnectionFactory
    Queue Java Class: com.ibm.mq.jms.MQQueue
    IP address: IP address of XI system.
    Port: 1414
    Queue manager name : MQ-manager-name_XI-system-name
    Channel Name : reciever-channel-name_XI-system-name
    JMS queue: postcard
    Charecter set ID:
    Transport/networkprotocol: TCP/IP
    JMS-Compliant : WebsphereMQ(non-JMS)
    But when I check it in adapter monitor JMS is shown as red.
    <b>In default trace file I am getting the following error</b>
    javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'SYSTEMNAME:QUEUEMANAGERNAME_SYSTEMNAME'
                at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
                at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1450)
                at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:960)
                at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:159)
                at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:215)
                at com.sap.aii.af.service.jms.WorkerJMSReceiver.init(WorkerJMSReceiver.java:283)
                at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:325)
                at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    <b>I also get the following warning</b>
    Warning   : Catching java.lang.NullPointerException
                at com.sap.aii.af.service.jms.WorkerJMSReceiver.start(WorkerJMSReceiver.java:584)
                at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:335)
                at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Can any one tell what could be the problem.
    Regards,
    Amith

    Try the following :
    1. Check if by any chance more than 1 Queue manager listeners have port number as 1414. Make sure all run on unique ports.
    2. Instead of IP addreess in the adapter config., try using hostname.
    3. Also check the website www.mqseries.net for this error

  • Anyone successfully deployed BPEL + JMS Adapter (for MQ) to WebSphere?

    Anyone successfully deployed BPEL Process Manager + JMS Adapter (for MQ) to WebSphere (i.e not OAS/OC4J)?
    If you have - I would love to see a valid example of the ra.xml and oc4j-ra.xml files in your jca/JmsAdapter.rar file - to see how you configured access for the JMS Adapter to your remote MQ queues.
    Thank you
    Dennis

    Hi Garima,
    Please check the following:
    1. Add dhbcore.jar also to aii_af_jmsproviderlib.sda and deploy it.
    2. Check the existence of your JMS drivers.
    3. Check the following link and Install the drivers as the way it is mentioned in the guide 'How To Install And Configure External Drivers For JDBC & JMS'
    https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
    There are 4 files which needs to be added. http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
    Any of the above solutions should help you solve the problem.
    Regards,
    Abhy

  • IDoc receiver AEE: Error "Configuration for Sender/Receiver Partner Number/Port is incorrect"

    Hi all,
    We are on PI 7.4 AEX SP 7. We are trying to get the following scenario working: Inhouse warehouse management system (JMS) --> PI --> ECC (IDoc)
    Sender is configured as 3rd party technical system system with business system maintained in SLD
    business system has logical system assigned in SLD
    adapter specific identifiers show logical system in ID / NWDS
    logical system is defined in receiver (ECC system)
    partner profile is created in ecc for this very logical system (inbound parameters)
    No mapping of EDI_DC40 node in ESB (complete node disabled)
    no header mapping in ID / NWDS
    receiver IDoc AEE adapter is configured to not enforce control record (Control Record in IDoc XML = Not Mandatory)
    no Identifiers specified in receiver IDoc AEE adapter
    My guts feeling is that this should work, however, it doesnt't. Failing with "The Configuration for Sender/Receiver Partner Number/Port is incorrect. Enter proper values in Sender/Receiver Component"
    Any thoughts are highly welcome.
    Cheers
    Jens

    Hi,
    The error mentioned by you is not related to the port..but its related to the Application ...
    IDoc 51 means idoc has been received in R/3 client and when it tries to process it ended in error..
    Check with the functional consultant for the error you have received..
    HTH
    Rajesh

  • JMS authorization for default user

    Hi All,
    I need to configure the JMS authorization for WLS 9.2. I succeed to do it for specific user that determined with access control to JMS Topic resource:
    TopicConnection _topicConnection = topicConnectionFactory.createTopicConnection(_user, _password);
    Along with it I succeed to create topic connection without sending the user/password:
    TopicConnection _topicConnection = topicConnectionFactory.createTopicConnection();
    I can't understand why I succeed if I configured the access to a JMS Topic Connection for specific user only. How I can close this access for default user?
    Thanks,
    Igor.
    Edited by igorkh at 10/07/2007 8:30 AM

    Hi,
              The user/pass arguments supplied for the createConnection call in WebLogic is only checked for the createConnection call itself, and there's no ACL check -- the call only checks that the user is a valid user. As far as I know there's no direct way to restrict the ability to create a JMS Connection to a particular JMS user (no way to specify an ACL directly). What you can do instead is configure an ACL on the JNDI name of the connection factory. You can also configure ACLs on your destinations (not just the JNDI name for the destination).
              For pretty much all API calls (not just JMS API calls), WebLogic generally obtains the implicit security credentials stored in the current thread. The current thread's credentials are initialized either by the user/pass that was passed in the most recent time a Context was created by the application using that same thread, or, if on the server and no context was created, the credential can be supplied as part of the EJB's or servlet's configuration.
              These implicit thread credentials are checked in various places when accessing a particular destination, as well as during JNDI lookups (applies if you've configured ACLs in your JNDI tree).
              Tom

  • JMS configure in  Two JVM - (Urgent)

    Hi,
    Application is running in resin server. For my requirement server should publish message and morethan one client(standalone application) should consume that message (non durable). How should i configure for topic connection.

    Sounds like you want basic JMS message consumer functionality.
    http://docs.oracle.com/javaee/1.4/tutorial/doc/JMS4.html#wp79145

  • Need separate duplicate JMS modules for each server?

    Using WebLogic 9.2.2 on AIX 5.3.
    I'm trying to set up a domain with 6 managed servers. I need to deploy several JMS queues and a foreign server to each JMSServer on each server. I looked at the JMSModule object, and I'm trying to determine whether it's possible to define a single JMSModule that I can deploy to all of my servers. So far, this doesn't appear to be possible. As a result, I have to do tons of painful cut/paste inside the console. Is this how it's supposed to work?

    David,
    Sorry, if I was not clear earlier.
    A Module can be targeted to a single Cluster, one or more comma separated list of WLS servers and the servers don't have to be part of a cluster (note that certain resources such as UDD or CF that can be targeted to an entire cluster, cannot be done so, if the module is not targeted to the cluster. And to achieve the same, the user has to manually add/remove the managed servers to the list of Module's/sub-deployment's targets whenever a server is added or removed to/from the cluster/domain).
    So, in your case, you can define all the JMS resources for that domain in a single Module descriptor and deploy it to a list of all the managed servers. Then you can use the sub-deployments to group and target them onto other related targets (for example, one or more queues can be grouped as a sub-deployment and targeted to a single JMSServer that is hosted by one of the WLS server instance, where the Module is currently targeted to, etc).
    I believe you are creating/using a "system resource" type module via Admin console, the JMSModules wizard shall walk you through the targeting page, where you can see all the available target servers/clusters.
    Here is an example of config.xml snippet for this kind of module targeting :
    <jms-system-resource>
    <name>SystemModule-0</name>
    <target>Server-0,Server-1</target>
    <sub-deployment>
    <name>ConnectionFactory-0</name>
    <target>Server-0,Server-1</target>
    </sub-deployment>
    <sub-deployment>
    <name>Queues</name>
    <target>JMSServer-0</target>
    </sub-deployment>
    <descriptor-file-name>jms/systemmodule-0-jms.xml</descriptor-file-name>
    </jms-system-resource>
    and the corresponding JMS module descriptor file snippet (can be found under DOMAIN_DIR/config/jms dir) as shown below:
    <?xml version='1.0' encoding='UTF-8'?>
    <weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls
    ="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http:/
    /www.bea.com/ns/weblogic/weblogic-jms http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd">
    <connection-factory name="ConnectionFactory-0">
    <sub-deployment-name>ConnectionFactory-0</sub-deployment-name>
    <jndi-name>ConnectionFactory-0</jndi-name>
    <security-params>
    <attach-jmsx-user-id>false</attach-jmsx-user-id>
    </security-params>
    </connection-factory>
    <queue name="Queue-0">
    <sub-deployment-name>Queues</sub-deployment-name>
    <jndi-name>Queue-0</jndi-name>
    </queue>
    </weblogic-jms>
    That being said, depending on, how many resources (factories, destinations etc) you are having and how you are going to group them, you may end of with too many sub-deployments within a single module, for which you need to carefully select targets/manage them.
    Both approaches (one module descriptor with many sub-deployments and many module descriptors with fewer sub deployments) have positives and negatives, when its comes to manageability. The recommended best practice is to have the JMS resource configuration split into more than one module with fewer number of sub-deployments within each, to have finer control over the resource configuration/management.
    Sounds like, you are trying to configure one queue on every managed server, that has duplicate(same) configuration properties. If that is the case, you can try using the UDD (Uniform Distributed Destination), that comes with automatic member (physical destination) management on all of its targets. That way, all you need is one UDD resource configuration/sub-deployment in the module and target the sub-deployment to the same targets as the module's targets (or accept the default targeting option, if available in the resource targeting page).
    More information on UDDs can be found here:
    http://edocs.bea.com/wls/docs100/jms/dds.html#wp1313025
    Hope this helps.
    Thanks
    Kats

  • Durable subscriber configured for the topic - reconnect policy

    Hi,
    we have Durable subscriber configured for the topic. When ever the managed server associated with the Topic is restarted, we have to restart subscriber to receive the messages again.
    we did tried using the reconnect policy to all , still we have same issue, could you please provide your suggestions.
    Susbcriber is not throwing the connect exception as well,when ever the managed server goes down also.
    thanks
    ARun

    I would suggest, if you have done so, that you set an Exception listener on the connection, or on the session using WLS extension interface, so that your client will get Exception on server failure and refresh the JMS objects (connection/session/subscriber).

  • JMS configuration in visual administrator

    HI All,
    I have deployed an ear file to J2EE stack of NW2004, that ear file consists of JMS topics, queues and destinations.
    Any extra configuration need to be done in Visual Admin related to JMS.
    I just deployed application without doing any JMS configuration in VA.
    Please let me know the detailed procedure for this.
    Regards,
    Anil.

    Follow the below procedure for creating a connection factory/queue/topic
    Visual Administrator->Services->JMS Provider
    Then  create a connection factory and queue .
    Get back in case of some issues.
    Regards.

  • SAP DMS - How to do an external DMS configuration for the existing system ?

    Hi All.
    Greetings.
    Request help and understanding.
    Am new to the world of SAP. And request SOME clarity for understanding of DMS.
    We are wanting to put an external DMS server and wish to configure for the same.
    So that the load on the production SAP R/3 database is reduced.
    We are now wanting to test the same on Dev environment.
    From SDN Link :
    I understand that :
    DMS basically has a content server. which stores documents.
    That can be accessed through Web, SAP R/3 Gui , SAP Portal.
    I have gone thro various links and the following links i have found to be informative and helpful :
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/c1/1c31a243c711d1893e0000e8323c4f/frameset.htm
    http://wiki.sdn.sap.com/wiki/display/PLM/DMS+Customizing
    http://help.sap.com/saphelp_nw70/helpdata/en/59/fba637fcf7dc39e10000009b38f8cf/frameset.htm
    However, would like to know the following because am not getting the clarity :
    1) Is there any supported platform / compatibility guide for DMS ?
    if yes, can someone send me the link?
    2) We have oracle 11g as our for SAP R/3 backend.
    Windows 2003 server 64 bit system.
    When i check the system status on the dev server of sap.
    It says. ECC 6.0 Rel 7.00 update 20 (hOpe am reading it correctly)
    After much search on the SMP site,
    we finally discovered and downloaded the DMS software for unicode and / 64 bit.
    Which we saw under the maintenance components separately seen for DMS 7.0
    Now for this DMS content server which we would like to make it external for storage of documents -
    do we need to have a separate database for this purpose as a repository.
    If i run a setup of DMS - will that automatically install any default repository for this or
    will it allow me to choose any other repository for the same ?
    Can anyone advise on this.
    Because this link says content server is based on Instance of MAXDB : http://help.sap.com/saphelp_nw70/helpdata/en/59/fba637fcf7dc39e10000009b38f8cf/frameset.htm
    3) I read some thing like this on some of the SDN links :
    P40 - Integration of DMS
    P62 - R&D Document Manage¬ment and Workflow
    P71 - Document management
    What are they referring to.
    4) We would be accessing these thro web, gui, customised portal.
    This content server configuration is a bit confusing.
    5) Is SNC configuration required to be done for the separate DMS server setup.
    If yes, how to do that ? any configuration link for that please ?
    Can anyone advise on the things to do.
    Steps to do.
    What all are the pre-requisites to check, before we start the set up of DMS.
    Can anyone help me understand this whole thing regarding the DMS installation and configuration.
    Step-wise.. from the start to end.
    Because it gives me a lot of uneasiness without having everything in place before we could say we could start the whole process of configuration / installation.
    Many thanks for your help in advance.
    Wishing you a happy and relaxed weekend.
    Kind regards
    Indu

    Thanks christoph & pradeep kumar.
    did a few more research and atleast have come to understand that.
    DMS server installation has content server which works only with MAXDB.
    So my understanding is correct.
    And what we see as Easy DMS is a client installation.
    which probably i would look at at a later stage.
    Found this link to be a little more informative :
    http://www.sapfans.com/forums/viewtopic.php?f=12&t=330558
    I really wish. That life were to be so easy. To call a consultant and finish it off
    Wishful thinking
    thanks and cheers
    indu

Maybe you are looking for

  • Table control scrolling issue

    hi,       I am having a issue with table control scrolling. When i was passing less number of records (say 19 records becuase table control is having 19 lines) to table control in BDC call transaction, everything is working fine. after filling the 19

  • Trouble viewing php in live view or split screen

    I have installed a testing server to render the php in my dreamweaver site. I have php5.3 on mac os x 10.6. The split view only shows a simple "php" logo or icon. Any idea what is going on? Or how to resolve the php rendering so that it provides a "l

  • Share upload status bug

    Hi, I found a ugly display bug in iMovie 10, while uploading a video to YouTube. So I can't see the exactly status of the upload. Apple, please fix this! Btw. I saw a similar bug in Safari while downloading something. Thx

  • UNABLE TO START JSPM - NEED HELP PLZ

    An error occured during the execution of JSPM_MAIN phase You can find more information in the log file /usr/sap/<SID>/DVEBMSGXX/j2ee/JSPM/log/ Can not initialize application data. Could not detect deployed components. No access to the table with syst

  • Bug on Calendar when going to march 2013

    When going to March 2013 on the Calendar app (view by month), it crashes...