Create Distributed Destination

I want to automate creation of distributed destinations as at times I need to create around 40 of them. Currently I do it "by hand" which is not very effecient !
          I tried using ant but it has too many limitations (does not allow space in the name etc). I tried WLST and can create JMSQueues but simply cannot create Distributed Destinations. I have searched and searched the web for all possible scripts, and tried all of them, but none of them work.
          My environment uses WebLogic 8.1 SP3 and above. I will be creating the Distributed Destinations on an existing (running) domain.
          If someone has already got this to work, please pass on the information to me.
          Thanks,
          Kevin.

An example is given here: http://middlewaremagic.com/weblogic/?p=7188
excerpt from the complete script
print 'CREATE UNIFORM DISTRIBUTED QUEUE';
resource.createUniformDistributedQueue('DistributedQueue');
distributedqueue = resource.lookupUniformDistributedQueue('DistributedQueue');
distributedqueue.setJNDIName('jms/CompanyQueue');
distributedqueue.setLoadBalancingPolicy('Round-Robin');
distributedqueue.setSubDeploymentName('SubDeployment');
distributedqueue.setUnitOfOrderRouting('PathService');When you want to create scripts you can also first use the admin console. In the middle top there is a record button.
To create a script, hit the record button, do some configuring, and hit the record button again. To script is
saved in the ${DOMAIN_HOME} directory.

Similar Messages

  • [WLST offline]: Cannot create distributed destination

    We have a small problem with WLST and distributed destinations. I have made the following code:
    readDomain ('< our domain path >/Demo8')
    # Check that the queue exists
    ls ('/JMSServer/cgJMSServer1/JMSQueue')
    create ('myQueue1','JMSDistributedQueue')
    cd ('JMSDistributedQueue')
    cd ('myQueue1')
    set ('JNDIName','myjndi')
    create ('member1','JMSDistributedQueueMember')
    cd ('JMSDistributedQueueMember')
    cd ('member1')
    set ('JMSQueue','queue1')
    cd ('..')
    cd ('..')
    UpdateDomain()
    The problems is, that the command "set ('JMSQueue','queue1')" fails.
    Does anyone have an example of a successful WLST configuration of Distributed Destinations?
    The error message from my script is:
    Error: setJMSQueue() failed.
    Error: set() failed.
    Traceback (innermost last):
    File "scr.py", line 19, in ?
    File "initWls.py", line 46, in set
    com.bea.plateng.domain.script.jython.WLSTException: java.lang.reflect.Invocation
    TargetException
    at com.bea.plateng.domain.script.jython.CommandExceptionHandler.handleEx
    ception(CommandExceptionHandler.java:33)
    Your help will really be appreciated....
    Kind regards,
    Henrik

    The best way to create distributed destinations is to create physical destinations in single server mode and then create more servers and a cluster. wlst offline will automatically create distribued destinations and members. Considering that the recommended JMS architecture is homogeneous, there is little need to do it manually. An example:
    readTemplate('c:/bea813/weblogic81/common/templates/domains/medrec.jar')
    cd('JMSServer/MedRecJMSServer')
    q=create('newQueue', 'JMSQueue')
    q.setJNDIName('newQueue')
    cd('/')
    create('newServer1', 'Server')
    create('newServer2', 'Server')
    create('newCluster', 'Cluster')
    assign('Server', 'newServer1,newServer2', 'Cluster', 'newCluster')
    writeDomain('d:/temp/domains/813/medrec/medrec_0720')
    closeTemplate();

  • Error occurred while forwarding a message for distributed destination

    Is there a change in the way that Uniform Distributed Destinations are handled in the cluster after weblogic9.2?
    I am using oracle weblogic 10.3.0.1 in production mode. I have two managed servers, each managed server has a JMS Server.
    I create a Uniform distributed Topic on the System module, and publish a message to it.
    I can see the message in the topic on the first JMSServer but the following error happens and the message never makes it to the second JMSServer
    <Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
    <Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on IP:PORT for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    <Sep 24, 2009 2:00:45 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "ManSvr1" for domain "Domain" running in Production Mode>
    <Sep 24, 2009 2:00:46 PM GMT+00:00> <Notice> <Cluster> <BEA-000102> <Joining cluster Clus on mip:mport>
    <Sep 24, 2009 2:00:47 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Sep 24, 2009 2:00:47 PM GMT+00:00> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Sep 24, 2009 2:09:52 PM GMT+00:00> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destination member JMSSystemResource!JMSServer2@example: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with 8935413426058515615S:fqhn:[-1,-1,sslport,sslport,-1,-1,-1]:Domain:ManSvr2, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:
         java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:
         java.rmi.ConnectException: Could not establish a connection with 8935413426058515615S:fqhn:[-1,-1,sslport,sslport,-1,-1,-1]:Domain:ManSvr2, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):fqhn:nonsslport:null:-1'; No available router to destination; nested exception is:

    I specified the cluster address, but still get the following errors after a message is published to the topic. Are there other configuration items that can be checked?
    <Sep 29, 2009 9:51:49 AM GMT+00:00> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Sep 29, 2009 9:52:01 AM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultAdministration" is now listening on 10.241.134.92:7018
    for protocols admin, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    <Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 10.241.134.92:7019 for
    protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    <Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "ClusManSv
    r2" for domain "domain" running in Production Mode>
    <Sep 29, 2009 9:53:26 AM GMT+00:00> <Notice> <Cluster> <BEA-000102> <Joining cluster Clus on 224.0.0.10:7390>
    <Sep 29, 2009 9:53:27 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Sep 29, 2009 9:53:27 AM GMT+00:00> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Sep 29, 2009 9:56:14 AM GMT+00:00> <Warning> <JMS> <BEA-040498> <An error occurred while forwarding a message for distributed destinati
    on member SOAFJMSSystemResource!SOAFJMSServer1@EventingAdminTopic: weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteExc
    eption: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,7017,7017,-1,-1,-1]:testnn
    2092.net:domain:ClusManSvr1, java.rmi.ConnectException: No known valid port for: 'Def
    ault[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested exception is:
    java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
    ilable router to destination; nested exception is:
    java.rmi.ConnectException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,1
    1217,7017,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No
    known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested
    exception is:
    java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
    ilable router to destination
    weblogic.messaging.dispatcher.DispatcherException: java.rmi.RemoteException: Could not establish a connection with 5660061832836428941S:
    managedServer.net:[-1,-1,7017,7017,-1,-1,-1]:managedServer.net:domain:
    ClusManSvr1, java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; N
    o available router to destination; nested exception is:
    java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
    ilable router to destination; nested exception is:
    java.rmi.ConnectException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,1
    1217,7017,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No
    known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No available router to destination; nested
    exception is:
    java.rmi.ConnectException: No known valid port for: 'Default[t3]:t3(t3):managedServer.net:7018:null:-1'; No ava
    ilable router to destination
    at weblogic.messaging.dispatcher.DispatcherWrapperState.dispatchAsync(DispatcherWrapperState.java:158)
    at weblogic.jms.dispatcher.DispatcherAdapter.dispatchAsync(DispatcherAdapter.java:84)
    at weblogic.jms.backend.BEForwardingConsumer$1.run(BEForwardingConsumer.java:503)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.jms.backend.BEForwardingConsumer.processMessages(BEForwardingConsumer.java:499)
    Truncated. see log file for complete stacktrace
    java.rmi.RemoteException: Could not establish a connection with 5660061832836428941S:managedServer.net:[-1,-1,7017,701
    7,-1,-1,-1]:managedServer.net:domain:ClusManSvr1, java.rmi.ConnectException: No known v

  • Problem creating Physical Destination for Message Driven Bean example

    I am trying to create a MDB application. in which i want to distribute the workload using messages.
    I am using SUN j2ee application server8.2 and netbeans 6.5 on windows xp professional.
    I referred the j2ee 1.4 tutorial to create the mdb's.
    I am able to create queue's and connection factories.
    the tutorial says
    To create the physical destination, perform the following steps:
    •.In the tree component, expand the Resources node, then expand the JMS Resources node.
    •.Select the Physical Destinations node.
    •.On the Physical Destinations page, click New. The Create Physical Destination page appears.
    •.In the Physical Destination Name field, type PhysicalQueue.
    •.Choose queue from the Type combo box.
    •.Click OK.
    but i am not able to find out this Physical Destination node in admin console. So when i execute my MDB project the messages are created but the onMessage() method is not invoked.
    Please help!!!

    Hi,
    but this example was in guide to this version.
    Ok, in case it is not possible to use MDB, how should i handle long time consumpting functions in EP enviroment?
    (customer has only EP6SP2 and he need to send a lot of mails after user request and i dont want to leave user waiting till that function ends. - should i start new thread in portal?)
    JJ

  • Distributed destination issue on Web Logic server 8.1

    Hi,
    I'm using distributed JMS destination (Cluster) of Web Logic server 8.1.
    I'm using Oracle B2B to talk to the cluster. Oracle B2B is only creating a consumer on one of the managed servers in this cluster. This is resulting in loss of messages when messages are placed by the WLI on the other managed server.
    Further the consumers are created randomly by Oracle B2B.
    My question here is whether Web Logic Server 8.1 supports multiple consumers for its clusters?
    Please Help!
    Thanks in advance.
    Warm Regards,
    Suhas.

    Are your consumers co-located with each managed server or remote?
    Let me preface this by this is the way I believe it works...
    The reason I ask is that distributed destinations route to one managed server at connect time. So for producers, when 1 message is placed on a distributed destination, it is really routed to only 1 managed server queue. From a remote consumer standpoint, when connecting to a distributed destination to read messages, you are only routed to one of the managed server queues to read from, not the logical superset of all queues in the distributed destination. So you would need to connect to each distributed destination member queue directly to ensure each had consumers. Whereas if your consumers are co-located on the cluster, then they can each connect to the local member queue for that distributed destination and ensure that each member of the distributed destination has consumers.
    I'd recommend you note the follow docs:
    QueueReceivers
    http://edocs.bea.com/wls/docs103/jms/dds.html
    When creating a queue receiver, if the supplied queue is a distributed queue, then a single physical queue member is chosen for the receiver at creation time. The created QueueReceiver is pinned to that queue member until the queue receiver loses its access to the queue member. At that point, the consumer will receive a JMSException, as follows:
    If the queue receiver is synchronous, then the exception is returned to the user directly.
    If the queue receiver is asynchronous, then the exception is delivered inside of a ConsumerClosedException that is delivered to the ExceptionListener defined for the consumer session, if any.
    Upon receiving such an exception, an application can close its queue receiver and recreate it. If any other queue members are available within the distributed queue, then the creation will succeed and the new queue receiver will be pinned to one of those queue members. If no other queue member is available, then the application won’t be able to recreate the queue receiver and will have to try again later.
    Note:      For information on the load-balancing heuristics for distributed queues with zero consumers, see “Configuring Distributed Destination Resources”.
    http://edocs.bea.com/wls/docs103/jms_admin/advance_config.html#jms_distributed_destination_config
    The producer makes such a decision each time it sends a message. However, there is no compromise of ordering guarantees between a consumer and producer, because consumers are load balanced once, and are then pinned to a single destination member.

  • Unable to get distributed destination in cluster

    [Cross post with interest.jms]
              Hi,
              I'm working with Weblogic 8.1.2 on Windows. Up until now I've always worked with a single server on which I have configured a JMS server and a number of queues. My clients get references to the queues using the createQueue() method. I now need to test in a clustered environment and my clients are no longer able to create queues; my clients gets a "Invalid destination name" each time.
              I've created a simple cluster with 2 servers and one distributed connection. Each server in the cluster has a uniquely named JMS server. I created a distributed connection called C1_DIST_SECURITY_PERSISTENCE and then created the members automatically for the cluster. My understanding from what I've read is that is the client should no longer need to name the JMS server when calling createQueue, instead the distributed destination name should be sufficient. So, my client calls
              session.createQueue("C1_DIST_SECURITY_PERSISTENCE")
              Everytime it does this it gets the exception: weblogic.jms.common.JMSException: Invalid destination name: C1_DIST_SECURITY_PERSISTENCE
              As an aside I modified my code to try explicitly looking up one of the destination members. In this case a totally different exception occurs:
              eblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Environment not found on thread ] at weblogic.jndi.internal.NamingNodeReplicaHandler.<init>(NamingNodeReplicaHandler.java:150) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
              Any help here greatly appreciated.
              Thanks,
              Aoife

    Hi Gsrc,
    This is my code in the PR.
    public void processRequest(OAPageContext pageContext, OAWebBean webBean)
    super.processRequest(pageContext, webBean);
    String itemNum=pageContext.getParameter("itemNum");
    System.out.println("item nnum "+itemNum);
    i am getting a null value in the print stmt.
    Thanks.
    Message was edited by:
    SRK84

  • How WLS makes one JMSServer leave or join a distributed destination?

    HI,
              According to the WLS documents for Distributed Destination:
              When one member becomes unavalibale due a server failure, traffic is then redirected toward other avaliable destination members in the set.
              Currently, I created two queues and defined two JMS Servers (JMSServer1, JMSServer2). These two JMS Servers are in same distributed destination (JMSDes1).
              My question is
              1) when the JMSServer1 is shutdown, How WLS marked it unavaliable? And How WLS makes it leave the JMSDes1? (If you can know where I can find the documents, it will be greate).
              2) After the JMSServer1 is recycled and is active, how WLS markes it avaliable and makes it join the JMSDes1 again?
              Thanks for any help.

    HI,
              According to the WLS documents for Distributed Destination:
              When one member becomes unavalibale due a server failure, traffic is then redirected toward other avaliable destination members in the set.
              Currently, I created two queues and defined two JMS Servers (JMSServer1, JMSServer2). These two JMS Servers are in same distributed destination (JMSDes1).
              My question is
              1) when the JMSServer1 is shutdown, How WLS marked it unavaliable? And How WLS makes it leave the JMSDes1? (If you can know where I can find the documents, it will be greate).
              2) After the JMSServer1 is recycled and is active, how WLS markes it avaliable and makes it join the JMSDes1 again?
              Thanks for any help.

  • WebLogic 10.3 jms Uniform Distributed Destination

    We are running WL Server 10.3 on Suse 11.0. I have created a Cluster, Servers, JMS Servers, Connection Factory and a Distributed Destination. On the Connection Factory, I have the "Server Affinity" checkbox unchecked. Server/Cluster all look good. I am using the jmsfullclient.jar for the test.
    When attempting to access the distributed destination, I get the following error on the second message. If I were to turn on "Session Affinity" in the Cluster, the problem does not arise but I lose the value of the distributed destination. Any suggestions and assistance would be appreciated.:
    weblogic.jms.common.JMSException: No failover destination.
         at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
         at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
         at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1275)
         at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:783)
         at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:541)
         at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:394)
         at weblogic.jms.client.JMSProducer.send(JMSProducer.java:384)
         at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:970)
         at com.overstock.util.Example.main(Example.java:44)
    Caused by: weblogic.jms.common.JMSException: No failover destination.
         at weblogic.jms.frontend.FEProducer.pickNextDestination(FEProducer.java:750)
         at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:1092)
         at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1399)
         at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1460)
         at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
         at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
         at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
         at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
         at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: weblogic.messaging.dispatcher.DispatcherException: could not find Server null
         at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:176)
         at weblogic.messaging.dispatcher.DispatcherManager.dispatcherFindOrCreate(DispatcherManager.java:58)
         at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreate(JMSDispatcherManager.java:219)
         at weblogic.jms.dispatcher.JMSDispatcherManager.dispatcherFindOrCreateChecked(JMSDispatcherManager.java:230)
         at weblogic.jms.frontend.FEProducer.findDispatcher(FEProducer.java:825)
         at weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:995)
         ... 9 more
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.messaging.dispatcher.S:null'. Resolved 'weblogic.messaging.dispatcher'; remaining name 'S:null'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.messaging.dispatcher.DispatcherManager.dispatcherCreate(DispatcherManager.java:172)
         ... 14 more
    My client code is extremely basic and is the following:
    public class Example {
    public static void main(String args[]) {
    String providerUrl = "t3://localhost:7003,localhost:7005";
    Hashtable<String, String> ht = new Hashtable<String, String>();
    ht.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
    ht.put(Context.PROVIDER_URL, providerUrl);
    InitialContext ctx = null;
    try {
    ctx = new InitialContext(ht);
    ConnectionFactory connFactory = (ConnectionFactory) ctx
    .lookup("connectionfactory");
    Destination dest = (Destination) ctx.lookup("distributedqueue");
    Connection conn = null;
    Session session = null;
    MessageProducer p = null;
    try {
    conn = connFactory.createConnection();
    conn.start();
    System.out.println("Thread:" + Thread.currentThread().getId() + " got a connection "
    + conn.hashCode());
    session = conn.createSession(false, Session.AUTO_ACKNOWLEDGE);
    p = session.createProducer(dest);
    System.out.println("Thread:" + Thread.currentThread().getId() + " started a connection");
    for (int i = 0; i < 1000; i++) {
    p.send(session.createTextMessage());
    System.out.println("FinishedRunning:" + Thread.currentThread().getId());
    catch (JMSException e) {
    e.printStackTrace();
    finally {
    if (p != null) {
    try {
    p.close();
    catch (JMSException e) {
    e.printStackTrace();
    if (session != null) {
    try {
    session.close();
    catch (JMSException e) {
    e.printStackTrace();
    if (conn != null) {
    try {
    conn.close();
    catch (JMSException e) {
    e.printStackTrace();
    catch (Exception e) {
    e.printStackTrace();
    Edited by: svachary on Jan 8, 2009 1:01 PM

    Hi,
    I would suggest you to go through these 2 links which you give all the details about UDD
    Topic:Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
    http://middlewaremagic.com/weblogic/?p=3747
    Topic:JMS Demo using WebLogic Uniform Distributed Queue (UDQ)
    http://middlewaremagic.com/weblogic/?page_id=1976
    Tips to solve UDQ issues
    - Make sure the Server Affinity Enabled parameter should be un-checked (disable) which under the [ Connection factory –> Configuration (tab) –> Load Balance (sub-tab)]
    - Disable the Server Affinity Enabled parameter for the connection factory whish is been used by your UDQ.
    - All the managed servers are in the same cluster.
    - If the managed serves are in different boxes make sure the listing address is given correctly which is under [ Machine –> Configuration (tab) –> Node Manager (sub-tab) ]
    - Test if you are able to PING the servers on different boxes and make sure that there is no network issues and you are able to communicate with the servers.
    Hope this helps you.
    Regards,
    Ravish Mody
    http://middlewaremagic.com/weblogic/
    Come, Join Us and Experience The Magic…

  • Distributed Destination and multiple clusters

    We have two clusters; each consisting of two managed servers. Can I create a single distributed JMS destination for BOTH clusters? If yes, how? If no, what is the best alternative so that I do not have to change the application for JMSqueue name?
              Thank you for your help.
              Vipul

    Distributed destinations do not span between clusters.
              You can configure two distributed destinations, each with the same JNDI name. The JNDI names will not conflict as they will be in two different clusters. Clients that refer to the JNDI name will end up communicating with the distributed destination that's in the same cluster as their JNDI context...
              Tom

  • How do you get distributed destinations to work ?

              Hi all,
              I'm trying to getting to work Distributed JMS Destinations. But
              still without success. This is the sitation:
              Node1---->JMS Server1------>Queue1 [Distributed destination1]
              Node2---->JMS Server2------>Queue2 [Distributed destination1]
              I have a cluster with 2 Nodes.
              I have created 2 JMS Servers each one targetted on one Node.
              Then I have created 2 Queues and added them to a Distributed Destination as member.
              Now I start the QueueSender (pointing to the Distributed Destination's JNDI)
              I start 2 QueueReceivers (pointing to the JNDI of the 2 Queues).
              The problem is that when one of the two nodes, let's say Node1, fails
              messages aren't dispatched to the JMS Server2.
              So I wonder: Is it possible that if one of the 2 JMS Server fails
              the message is redirected to the other JMS Server ?
              Thanks a lot
              Francesco
              

    Receivers only load-balance once - when
              they are first created. The JMS Performance
              Guide explores the implications of this.
              Keep in mind that the distributed destination
              feature was optimized for the case where
              receivers (generally MDBs) run on the same
              servers as the distributed destination
              instances, which simply load balances each
              receiver to its local destination instance.
              Otherwise, if the receivers
              are not co-located with distributed destination
              instances, load-balancing
              configuration requires special care to prevent
              physical destinations from not getting served
              by receivers.
              One solution for the latter problem, as you
              already wrote below, is to receive directly from the
              physical destinations - which removes the
              load balancing decision all-together.
              Francesco wrote:
              > Hi,
              > thanks a lot for your clean answers.
              > Ps has anybody got an answer about my last question (That is, should I lookup
              > the JNDI
              > of the single Queue or of the Distributed Destination in order to get distributed
              > destination to work ?)
              > Thanks a lot
              > Francesco
              >
              > Tom Barnes <[email protected].bea.com>
              > wrote:
              >
              >>It is normal for a sender to get an exception
              >>when its connection's host server goes down.
              >>The client connection's host server does
              >>not change for the life of the connection,
              >>and does not automatically fail-over.
              >>Even when the client's connection host stays up
              >>but the JMSServer hosting the current
              >>distributed destination instance goes down, the sender
              >>may still get an exception. Such an exception
              >>can indicate that there is ambiguity as to
              >>whether or not the JMS server received the
              >>message from the send().
              >>
              >>The standard way to handle
              >>such exceptions is to re-establish the connection,
              >>session, and producer on the client (usually
              >>using the exact same code that initialized
              >>these resources to start with.)
              >>
              >>In addition, it is highly recommended
              >>for the client to register exception listeners
              >>on both the connection and on the WLSession.
              >>
              >>Tom
              >>
              >>Francesco wrote:
              >>
              >>
              >>>"Barry Myles" <[email protected]> wrote:
              >>>
              >>>
              >>>>Hi Francesco
              >>>>
              >>>>Try creating a connection factory that has Load balanced ticked and
              >>
              >>server
              >>
              >>>>affinity
              >>>>unticked
              >>>>
              >>>>now make sure that the distributed destinations load balancing property
              >>>>is set
              >>>>to Round Robin
              >>>>
              >>>>
              >>>>
              >>>>>I start 2 QueueReceivers (pointing to the JNDI of the 2 Queues).
              >>>>
              >>>>Also when the QueueRecievers are running do you see one consumer attached
              >>>>to each
              >>>>physical queue?
              >>>>
              >>>>HTH
              >>>>
              >>>>
              >>>>"Francesco" <[email protected]> wrote:
              >>>>
              >>>>
              >>>>>Hi all,
              >>>>>I'm trying to getting to work Distributed JMS Destinations. But
              >>>>>still without success. This is the sitation:
              >>>>>
              >>>>>Node1---->JMS Server1------>Queue1 [Distributed destination1]
              >>>>>Node2---->JMS Server2------>Queue2 [Distributed destination1]
              >>>>>
              >>>>>I have a cluster with 2 Nodes.
              >>>>>I have created 2 JMS Servers each one targetted on one Node.
              >>>>>Then I have created 2 Queues and added them to a Distributed Destination
              >>>>>as member.
              >>>>>
              >>>>>Now I start the QueueSender (pointing to the Distributed Destination's
              >>>>>JNDI)
              >>>>>I start 2 QueueReceivers (pointing to the JNDI of the 2 Queues).
              >>>>>
              >>>>>The problem is that when one of the two nodes, let's say Node1, fails
              >>>>>messages aren't dispatched to the JMS Server2.
              >>>>>
              >>>>>So I wonder: Is it possible that if one of the 2 JMS Server fails
              >>>>>the message is redirected to the other JMS Server ?
              >>>>>Thanks a lot
              >>>>>Francesco
              >>>>
              >>>Hi Barry,
              >>>I have tried to modify the connection factory as you said but
              >>>I'm still stuck. Basically when I shut down one of the two Nodes, the
              >>
              >>Sender
              >>
              >>>receives an exception "IllegalStateException: Producer is closed".
              >>>
              >>>Could you tell me if it's basically correct that :
              >>>
              >>>Sender----->looks up the Distributed Queue
              >>>Receivers---->look up the single Queues (which belong to the Distr.
              >>
              >>Queue)
              >>
              >>>Thanks again
              >>>Francesco
              >>
              >
              

  • In portal where we will create JCO destinations?

    HI Gurus,
    In portal where we will get the option or screen for creating JCO destinations....
    I guess its somemwhere in System Admin---->
    If anybody knows the path please share with me.......
    Thanks in Advance,
    Dharani

    Hi,
    Please check the below document for help
    configure ESS:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eb036a-0a01-0010-25a3-b2224432640a
    ESS/MSS Installation to R/3 4.7 Enterprise
    http://help.sap.com/saphelp_erp2004/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
    Configuring The Business Package For Employee Self Service (ESS)-mySAP ERP 2004
    MSS - http://help.sap.com/saphelp_erp2004/helpdata/en/0a/8b3b40b1607a56e10000000a1550b0/frameset.htm
    help.sap.com - Configuration of Employee Self-Service (ESS)
    http://help.sap.com/saphelp_erp2005/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
    help.sap.com - Technical Description and Configuration Information
    http://help.sap.com/saphelp_erp2005/helpdata/en/76/77594d165144a1a9bff9aae1e26b26/frameset.htm
    BP for ESS Document
    https://www2.iviewstudio.com/support_content/_17295/BP_ESS_05_P1.pdf
    General Settings for Self-Service Applications
    Configuring MSS on Portal 6.0
    Implementation and Configuration guide for ESS into Portal,Backend R/3 4.7C
    Thanks & regards
    Santosh
    Reward if helpful !!!

  • Pdfmark code in MS Word 2008 doc doesn't seem to work properly to create Named Destination

    Hi all,
    I've been having trouble with creating Preview-compatible Named Destinations in Acrobat 9.x (see http://forums.adobe.com/thread/770470?tstart=0).  Distiller, on the other hand, appears to create compatible Destinations, so as a last-ditch effort, I tried to go back to my original source file (Microsoft Word 2008 document) to use Distiller's pdfmark functionality, to see if maybe I could finally get a PDF with Preview-compatible Destinations.
    Following instructions found elsewhere on this forum, I went into Word and inserted the following field into a test location in my document:
    PRINT "[ /Dest /testdest /View [ /XYZ null null null ] /DEST pdfmark"
    This field code is supposed to then cause a pdfmark to be inserted into the resulting PostScript and/or PDF files.  Distiller is supposed to understand this and turn it into a Named Destination called "testdest."  However, it doesn't seem to work - I don't see the pdfmark code in the PS file, and the PDF file doesn't have any Named Destinations in it.
    I'm using Acrobat 9.x on Mac OS X 10.6.5, so I tried this two different ways:
    1) Using the "Print to Adobe PDF" workflow (which replaced the "Adobe PDF Printer" from previous OS/Acrobat versions) - this automatically generates a PDF via (presumably) an API call to Distiller... and
    2) Using the "Print to Postscript" workflow to generate a PS file, which I then ran through Adobe Distiller.
    In neither case did I end up with a named destination in the PDF file, as I was supposed to.  In case #2, even the Postscript file didn't have a pdfmark embedded in it.  Thus, I'm assuming that perhaps this is particular issue may be a problem with MS Word 2008 rather than with Acrobat... but I'm hoping someone might have a clue as to how to fix it.
    I welcome ideas on how to get Word 2008 to properly output pdfmark code, so that Distiller will pick it up and properly embed a Named Destination into the PDF...
    Thanks in advance.
    (If anyone has ideas about the Preview-compatible problem, linked above, that would also be great!)

    You're suggesting that it was never fixed from Word 2004 to 2008?  Possibly.  I wonder if it's fixed in Word 2011?  Anyone know?  But is it really a Word problem, rather than a Distiller issue?
    I appreciate your offer, though I do have access to Word on Windows (2003, I think), so I could try Distilling there... I only worry about formatting, since there are minor differences (e.g. font kerning, etc.) between Mac and Windows that are subtle, but sufficient to create formatting issues for very long documents (e.g. pushing figures onto the wrong pages, etc.).  That would be a rather big problem.
    The question remains whether this is an issue with Word or Distiller, though... and whether it's fixed in Distiller X and/or Word 2011.
    Adobe, care to comment?
    I'd really love to find a proper Mac solution, if one exists... it would be rather a slap to Mac users if a solution doesn't exist.

  • Getting error in creating JCo destination for WebDynpro

    Hi Guys,
    I am getting an error in creating JCo Destination under Web Dynpro Content Admin.I am deploying MSS on Netweaver portal SR1 and ecc 5.0.I am getting a message"An error has occurred: "Failed to process the request."Contact your System Admin.
    When I am seeing the details:
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
    Web Dynpro code generators of DC sap.com/tcwdtools:
    No information available
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    6.40 patchlevel 87289.311
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_07-b05, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2003, version: 5.2, architecture: x86
    Error stacktrace:
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:871)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:223)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:274)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:620)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:263)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:737)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:635)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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)
    Please help me guys.
    Paritosh

    You should post your question to the Webdynpro forum:
    Web Dynpro Java

  • Best practice for creating RFC destination entries for 3rd parties(Biztalk)

    Hi,
    We are on SAP ECC 6 and we have been creating multiple RFC destination entries for the external 3rd party applications such as Biz-talk and others using TCP/IP connection type and sharing the programid.
    The RFC connections with IDOC as data flow have been made using Synchronous mode for time critical ones(few) and majority through asynchronous mode for others. The RFC destination entries have been created for many interfaces which have unique RFC destinations with its corresponding ports defined in SAP. 
    We have both inbound and outbound connectivity.with the large number of RFC destinations being added we wanted to review the same. We wanted to check with others who had encountered similar situation and were keen to learn their experiences.
    We also wanted to know if there are any best practices to optimise on number of RFC destinations.
    Here were a few suggestions we had in mind to tackle the same.
    1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
    2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
    3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
    I have done checks on SAP best practices website, sap oss notes and help pages but could not get specific information I was after.
    I do understand we can have as unlimited number of RFC destinations and maximum connections using appropriate profile parameters for gateway, RFC, client connections, additional app servers.
    I would appreciate if you can suggest the best architecture or practice to achieve  RFC destinations in an optimized manner.
    Thanks in advance
    Sam

    Not easy to give a perfect answer
    1. Create unique RFC destinations for every port defined in SAP for external applications as Biztalk for as many connections. ( This would mean one for inbound, one for outbound)
    -> be careful if you have multi cllients ( for example in acceptance) RFC's are client independ but ports are not! you could run in to trouble
    2. Create one single RFC destination entry for the external host/application and the external application receiving the idoc control record to interpret what action to perform at its end.
    -> could be the best solution... its easier to create partner profiles and the control record will contain the correct partner.
    3. Create RFC destinations based on the modules it links with such as materials management, sales and distribution, warehouse management. This would ensure we can limit the number of RFC to be created and make it simple to understand the flow of data.
    -> consider this option 2.
    We send to you messagebroker with 1 RFC destination , sending multiple idoctypes, different partners , different ports.

  • Using Messaging  Bridge with Distributed Destinations

    I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
              * WLS Server1:
              * JMS Server1:
              * inbound queue
              * outbound queue
              * JMS Server2:
              * inbound queue
              * outbound queue
              * WLS Server 2:
              * JMS Server3:
              * inbound queue
              * outbound queue
              A distributed destination is configured for the inbound and outbound queues.
              Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
              Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
              Any suggestions?
              

    Hi Rob,
              Consumers on distributed destinations are always pinned
              to a single physical destination on creation. Only
              producers can round-robin each message. When a
              distributed destination is used as a source destination,
              you will need to configure a bridge per distributed
              destination. Alternatively, you can enable
              forwarding between the physical queues, which automatically
              forwards messages from physical queues with
              no consumers to physical queues that have consumers
              (but the extra hop impacts performance). For more information,
              consult the JMS documentation.
              Tom
              Rob McArthur wrote:
              > I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
              > * WLS Server1:
              > * JMS Server1:
              > * inbound queue
              > * outbound queue
              > * JMS Server2:
              > * inbound queue
              > * outbound queue
              > * WLS Server 2:
              > * JMS Server3:
              > * inbound queue
              > * outbound queue
              >
              > A distributed destination is configured for the inbound and outbound queues.
              >
              > Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
              >
              > Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
              >
              > Any suggestions?
              >
              >
              

Maybe you are looking for