JMS Properties in JNDI Directory

We are starting to use Message-Driven-Beans within our WLS 8 environment. My responsibility
is for WebSphere MQ and JMS. Currently our JMS usage has been such that that the
connection_factory information is stored in a central LDAP directory and administered
by the WebSphere MQ team. The queue objects are administered by the application
teams and kept locally. We would like to keep this concept also when using MDBs
in WLS. Looking at the configuration I cannot see how I could define two seperate
JNDI (initial_context) references - one for the queue object and a different one
for the connection_factory.
Any ideas?
Thanks in advance,
Martin
PS: Using MQ as transport for JMS is mandatory!

If your program is in an executeable jar file then add the following in the manifest
class-path: junk.jar
junk.jar has
pjb/props/myconfig.properties file
To access the properties in junk from your executable jar file in your class, do the following
Locale eng = Locale.ENGLISH;
String myvalue  = java.util.ResourceBundle.getBundle("pjb.props.myconfig",eng).getString("greeting");That should work
Or if you not using an executable jar file just set your CLASSPATH to the directory where that junk.jar is.
java -cp c:\myjavalib\stash\                 <-----Assmuing junk.jar is in thereJava dynamically reads jar files.

Similar Messages

  • PI 7.11 JMS adapter using JNDI weblogic server issue

    Hi SAP experts,
    I have a scenario to integrate to a application using JMS adapters. we use SAP PI 7.11 version.
    We have deployed JMS drivers successfully and We face issue here to connect to weblogic server
    We are using JMS adapter using JNDI to connect to weblogic server version 10.3.
    Can anyone help with the exact format to be used in JMS properties table and additional parameters table in JMS communication channel. Your quick help will be appreciated.
    A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up destination: AccrualDetailsQueue for profile:  ConnectionProfile of channel: CC_SND_JMS on node: 3010950 having object id: 673696a9fe8c39fdab32213f0930afb3: javax.naming.NameNotFoundException: Unable to resolve 'AccrualDetailsQueue'. Resolved ''<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination(JndiConnectorImpl.java:168)<br

    Hi Padmini,
    Refer to the following link:
    http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
    It was very helpful to me, for configuring the additional parameters in the communication Channel JMS.
    I leave you some screenshots of the settings that I did.
    I seize the opportunity to ask you, where do I can get the drivers (.Jar) for Weblogic?
    Regards.
    Rodrigo.

  • Message Queue 4.4 doesn't know "jms.properties" ?

    Sun JMS Tutorial illustrates using a properties file to supply context properties. You define a System property "jms.properties" to point to the location of the properties file:
    java -Djms.properties=%J2EE_HOME%\config\jms_client.propertiesInside of said file is the properties in question (these are a surmise; the contents are nowhere documented).
    java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
    java.naming.provider.url=file:///C:/TempThen a call to InitialContext() will succeed.
    But the Tutorial assumes you're running under J2EE, and I'm not. I'm using the stand-alone Message Queue 4.4. If I define the properties on the command line,
    java -Djava.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory -Djava.naming.provider.url=file:///C:/Tempthen InitialContext() succeeds.
    If I explicitly dump the contents of the file into System.properties,
           String
           prop = System.getProperty( "jms.properties" );
           Properties props = System.getProperties();
           try  {
               java.io.File pf = new java.io.File( prop );
               props.load( new java.io.FileInputStream(pf) );
           catch( Exception ex )  { ex.printStackTrace(); }Then they get defined and InitialContext() tries to use them. But if I don't then they never get defined. Obviously the Tutorial expects that someone will do that, but who? AFAIK, both environments use the same naming library.
    Has the behavior of MQ changed since version 1.3 of the tutorial? Or is J2EE doing something that the standalone product doesn't?

    This is all about JNDI configuration. Before you can look up an object in a JNDI repository you need to tell the JNDI runtime which JNDI provider to use. This means you need to set the system properties java.naming.factory.initial and java.naming.provider.url to specify which JNDI provider to use and where the data is located. There's a bit about this in the JNDI tutorial [http://java.sun.com/products/jndi/tutorial/basics/prepare/initial.html|http://java.sun.com/products/jndi/tutorial/basics/prepare/initial.html] .
    The tutorial you are running uses the simple file-based JNDI provider known as "fscontext" and included in fscontext.jar.
    That tutorial seems to be reading the jms.properties property and importing its contents, though I can't see where that is supposed to happen and so am not surprised it doesn't work. jms.properties is not, as far as I can see, a standard property name.
    The MQ 4.4 documentation describes how to configure an InitialContext to use fscontext by configuring those properties directly. This would definitely work!
    [http://docs.sun.com/app/docs/doc/821-0029/aeqbb?a=view|http://docs.sun.com/app/docs/doc/821-0029/aeqbb?a=view]
    Note that your JNDI datastore (which you've defined to be in C:\Temp) will start off empty, so any lookups will fail unless you've inserted connection factories or destinations in there yourself. I see that is covered elsewhere in the JMS tutorial you were following. There's also a simple MQ GUI tool that can do this. [http://docs.sun.com/app/docs/doc/821-0027/aeoaz?a=view|http://docs.sun.com/app/docs/doc/821-0027/aeoaz?a=view]
    Finally, if you're simply trying to learn about JMS and MQ you can skip the use of JNDI completely and simply instantiate the underlying connection factories explicitly. This wouldn't be appropriate in a production environment (where it is recommended to store such objects in a central store) but for developmeht purposes would work just fine.
    Nigel
    http://docs.sun.com/app/docs/doc/821-0029/aeqbb?a=view

  • XI to IBM Websphere Default JMS Provider with JNDI

    Hello everybody!
    We face a problem with connecting SAP XI to IBM WebSphere Default JMS Provider (need to send a message from XI to WebSphere JMS and receive the response).
    We have the following versions installed:
        SAP XI: 7.0 SP8 , Sun JDK 1.4.2
        IBM WebSphere: IBM WebSphere Application Server ND, 6.0.2.17, J2RE 1.4.2 IBM
    We cannot set the JMS adapter of SAP XI for conecting with IBM WebSphere Default JMS Provider. The Communication Channel has erroneous state (at runtime) and the Communication Channel Monitoring tool displays the error message as described below (under "Variant 1" and "Variant 2" sub-headings) depending on the settings performed. 
    For connecting, the following JMS-provider settings were used at IBM WebSphere side:
       JMS Providers: Default Messaging Provider
       Queue Connection Factories: name:QueueConnectionFactory, jndi:jms/QueueConnectionFactory, provider: Default Messaging Provider
       Queues: name Queue, jndi: jms/Queue, provider: Default Messaging Provider
    The XI communication channel (and associated JMS-adapter) was set as Variants 1 and 2 show. Settings for both cases and received error messages were the following:
    <b>Variant 1.</b>
        Adapter type: JMS
        Type: Receiver
        JMS Provider: Access JMS Provider with JNDI (Java Naming and Directory Interface)
        JNDI Lookup Name of QueueConnectionFactory:  jms/QueueConnectionFactory
        JNDI Lookup Name of JMS Queue: jms/Queue
        Name of JNDI Initial Context Factory: com.sap.engine.services.jndi.InitialContextFactoryImpl
        JNDI Server Address: iiop://WEBSPHERE.HOST:2809/ 
        As the result, the Communication Channel Monitoring displays that the channel has erroneous state and the following error message is written:
        "Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of jms/QueueConnectionFactory.
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)"
    <b>Variant 2</b>
        The same settings as in Variant 1 above, were used and additionally the following settings were done:
        - Name of JNDI Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
        - The archive aii_af_jmsproviderlib.sda containing libraries required by WsInitialContextFactory, was deployed to the SAP WebAS where the XI is running. Those libraries were taken from WebSphere Application Server Pluggable Application Client installation package (described in the article "WebSphere Application Server Pluggable Application Client" located at http://www-128.ibm.com/developerworks/websphere/library/techarticles/0409_bhogal/0409_bhogal.html)
        - Also, as it is recommended in the referred article, the files required by IBM's iiop protocol (ibmext.jar ibmorb.jar ibmorbapi.jar) were put to the folder jre/lib/endorsed of the server(Sun JVM 1.4.2 is used by SAP WebAS / XI).
        As the result, the Communication Channel Monitoring displays that the channel has erroneous state as well and the following error message is written:
       "No adapter registered for this channel"
    We have not found the recommended solution either in SDN forums or in Internet in general. Is it yet possible to connect SAP XI to IBM WebSphere Default JMS Provider having mentioned product versioning? If yes, what settings have to be performed?

    IBM Websphere Default JMS Provider which is installed alongwith the application server is nothing but a scaled down version of the IBM WebSphere MQSeries. you should be able to connect to it with the same settings that can be used for a separate MQSeries server connectivity from XI.

  • PasswordSync Configuration - JMS Properties Settings

    Hi,
    I am basically trying to install and configure the password Sync process on a Windows 2000 Domain controller to interact with Sun IdM 6.0.
    I had installed the .NET 1.1 framework required for a Windows 2000 Domain Controller and PasswdSync. Now when I am trying to configure the PasswordSync, I am not sure what values should be entered against the "java.naming.factory.initial" and "java.naming.provider.url" properties under the JMS Properties tab of the PasswordSync configuration wizard. Also, I would appreciate if any one of you could throw some light on JMS Settings as well. I have set-up the JMS server and created a connection factory required before trying to configure.
    Thanks,
    Indie.

    Hi,
    I put tcpmon proxy between windows pwsync and IDM to determine if the password update
    was being sent and got the following:
    ==============
    Listen Port: 8080
    Target Host: 170.1.1.5
    Target Port: 8080
    ==== Request ====
    POST /idm/servlet/rpcrouter2 HTTP/1.0
    Accept: text/*
    SOAPAction: "urn:lighthouse"
    Content-Type: text/xml; charset=utf-8
    User-Agent: VCSoapClient
    Host: 170.1.1.5:8080
    Content-Length: 1165
    Connection: Keep-Alive
    Pragma: no-cache
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http:
    //www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><soap:Body soap:encodingStyle="http://schemas.xmlsoap
    .org/soap/encoding/"><snp:queuePasswordUpdate xmlns:snp="urn:lighthouse"><userEmailAddress>[email protected]</userEmailAddress><resourc
    eAccountId>CN=Gabriela Castro,CN=Users,DC=domain,DC=net</resourceAccountId><resourceAccountGUID>889e54e67501944ab573934e4b2724d6</resourceA
    ccountGUID><password>fr6j+8qxoHOqarRvYS8Flg==</password><accounts xsi:nil="1"/><resourcename xsi:nil="1"/><resourcetype>Windows Active Direc
    tory</resourcetype><clientEndpoint>AFISERV23P</clientEndpoint><jmsUser>guest</jmsUser><jmsPassword>guest</jmsPassword><queueName>destQueue
    </queueName><connectionFactory>destFactory</connectionFactory><sessionType>LOCAL</sessionType><JNDIProperties>java.naming.factory.initial=
    com.sun.jndi.fscontext.RefFSContextFactory;java.naming.provider.url=file:///C:imq</JNDIProperties><singleResult>true</singleResult></snp:que
    uePasswordUpdate></soap:Body></soap:Envelope>==== Response ====
    HTTP/1.1 200 OK
    X-Powered-By: Servlet/2.4
    Content-Type: text/xml;charset=UTF-8
    Date: Tue, 20 Nov 2007 22:23:05 GMT
    Server: Sun-Java-System/Application-Server
    Connection: close
    <?xml version='1.0' encoding='UTF-8'?>
    <SOAP-ENV:Envelope
      xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/'
      xmlns:xsi='http://www.w3.org/1999/XMLSchema-instance'
      xmlns:xsd='http://www.w3.org/1999/XMLSchema'>
    <SOAP-ENV:Body>
      <ns1:queuePasswordUpdateResponse
        xmlns:ns1='urn:lighthouse'
        SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'>
          <return xsi:type='xsd:string'>noIDMSessionRequired|ok|</return>
      </ns1:queuePasswordUpdateResponse>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    ==============from which I saw that java.naming.provider.url specifies a windows path and not a unix path, and since
    IDM is installed in UNIX (the servlet which is invoked by pwsync) this is what was failing, I changed it to the actual unix path where the .bindings file
    is and it worked.
    I can�t recall what I read in the documentation but it is not clear the value that this parameter must have,
    it specifies what the parameter is but when using both unix and windows environments it gets confusing, at least for me,
    but anyway, it works now.

  • JMS Header: JMS Properties and Message Selector

    Hi all
    I´m using a JMS Adapter to consume messages from a JMS queue (a JMS adapter which create the BPEL instance when a message arrives).
    The process must select messages which meet certain criterias, so I´m using Message Selector to filter the messages and only pick up the ones who interest me (If click on the "help" button on JDeveloper Wizard in the page you define Message Selector, you can see an example on how doing this).
    So how can I select messages using values placed on JMS Properties, in the Message Selector?
    For example, I set in the JMS Header:
    JMSInboundHeadersAndProperties
    --------JMSInboundProperties
    ----------------Property
    -----------------------name = 'Country'
    -----------------------value = 'Brazil'
    The JMSAdapter must consume only messages that "Country" = "Brazil".
    Thanks in advance.
    Menezes

    Yes
    I am able to specify JMS Header and JMS Properties when producing a message. However I am not able to user "Message Selector" to filter messages based on JMS Properties information when consuming messages.
    In the link you provide, there is an example on how to use Message Selector:
    # (a copy from the link)
    Message Selector
    ...for example, you can enter logic, such as:
    * JMSType = 'car' AND color = 'blue' AND weight > 2500
    * Country in ('UK', 'US', 'France')
    I believe the example with "Country" is exactly what I need, but I can´t get it work.
    I create the same example above, setting a property named "Country" in the JMSHeader, sending the message to a JMS Queue (BPEL Process #1) and try to comsume it on the Message Selector (BPEL Process#2), but JMSAdapter never consumes the message.
    Thanks for your help.

  • JMS Receiver Adapter, using JMS Properties

    Hello,
    with XI SP14 i should be able to set JMS Properties using Adapter Specific Message Attributes DCJMSStringProperty1 and DCJMSStringProperty2. I set the Elements DCJMSStringProperty(1,2) during java mapping and everything works fine. i can see the "DynamicConfiguration" in the Message monitoring appearing with the correct values.
    In the configuration of the adapter specific attributes i give the message properties names and hope the adapter will pass the the values to the jms (IBM MQ implementation) but in jms no properties appear.
    has anybody a hint for me, has anybody faces similar issues.
    best regards,
    roland

    Hi Prasad
    You can use a simple user defined function. The question is, to which destination element should the function be connected to? I tried to connect to the root element of the destination structure (as dummy) and it worked.
    I prefer JAVA Mapping it's more transparent and reusable.
    Btw. My original problem remains still unsolved. Our IBM MQ still cannt see the JMS Properties.I contacted SAP for this matter, I will provide you with the solution when there is any.
    Greetings
    Roland
    Message was edited by: Roland Stellmach

  • JMS SAF client paging directory definition ignored

    The paging directory definition in our ClientSAF.xml file is ignored:
              <weblogic-client-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
              <persistent-store>
                   <directory-path>C:\Work\newaupload\jms</directory-path>
                   <synchronous-write-policy>Disabled</synchronous-write-policy>
              </persistent-store>
              <saf-agent>
              <paging-directory>C:\Work\newaupload\jms-paging</paging-directory>
              </saf-agent>
              </weblogic-client-jms>
              Instead of the directory given in the configuration, the JMS SAF client creates a directory called "paging" in the current directory. In our case, the current directory is where all the binaries are and which is not writable, i.e. the JMS client fails.
              Is something wrong with the configuration? Or is this a bug?
              Peter
              Edited by peter05 at 05/30/2008 3:30 AM

    Hi Peter,
              For a server-side SAF with a file store, a paging directory would normally only be used internally for non-persistent messages - and I think client-side SAF would have the same behavior if it actually supports non-persistent messages in the first place.
              I don't know if the SAF client supports non-persistent - as I hadn't really thought about it -- there doesn't seem to be much purpose in it given that the purpose of SAF is store-and-forward and the "store" part implies persist messages.
              As a work-around, perhaps you can create the directory manually as read-only, then check to see if your app places any files in this directory. If it is, then your app could be creating non-persistent messages for store-and-forward, which likely isn't your intent -- non-persistent messages are not recovered on a restart, even if they are in a paging directory.
              If there must be an active paging directory for some reason, I advise (A) contacting customer support to find a way to configure it uniquely and (B), as a work-around, using an operating level linked directory or some-such to redirect the "paging" directory name out of your read-only binary directory to a better place.
              Hope this helps,
              Tom
              PS. In addition, it's a little strange to me that this directory name is hard-coded - what would happen if two SAF clients running in the same JVM attempted to use the same paging directory? Would they conflict with or even corrupt each-other?

  • Proxy-2-JMS Scenario: more than 10 additional JMS properties possible

    Hi @all,
    we're implementing a Proxy-2-JMS-Scenario. The JMS reciever side needs unfortunalety more than 10 additional JMS properties. In XI/PI the maximum number of additional JMS properties is 10.
    Do somebody know a good workaround in PI how to deal with it?
    Thanks and best regards,
    Stefan

    Hi @all,
    there is no way to handle with more than 10 additional jms properties for jms header.
    Best Greetings,
    Stefan

  • JMS properties in ALSB

    Hello,
    I've used ALSB 3.0. I created a proxy ans a business service that send JMS to a MQ queue, then i have a java application that listen the MQ to get the JMS. When i set one of the JMS properties in the test, i don't find this one when i'm listening with my java application. I've tested that with another java application that set and send a JMS. It works. So the problem is coming from ALSB, i don't know how to set a JMS propertie.
    Thank for your help.

    SOA Suite 11g - how to set/get JMS headers ?

  • Administering AQ JMS objects in JNDI

    I had used several JMS providers before like MQ and Tibco but I'm new to Oracle AQ.
    I'm trying to write a JMS client program which lookups a connection factory and a destination from a JNDI context, and then create a session and publish JMS messages.
    However, I cannot find a way to register JMS objects in JNDI. The sample programs provided by Oracle use a JMS session to create destination objects, which means they're not portable to other messaging system.
    Questions:
    1. Is there a way to administrate JMS objects in JNDI context in version 8.1.7?
    2. I did search the forum and it seems like looking up JMS objects from JNDI is available on Oracle 9i. Is that true? And what administration tool am I supposed to use?
    Thanks,
    Andy

    Hi,
    I am not sure with OSB. I never seen the face of it. But when you say you are not able to see the subscriber in the table then you cannot consume the message.
    Can quickly create AQJMS adapter service in bpel and select your topic and deploy the service in SOA server. Once it deploy go to the aq$my_topic1_s check if you able to see or not. And also try de-queue a message from the same topic.
    I am using JMS Transport for Proxy Service and i have enabled the durable subscriber option as well. Please tell me how the entries in the subscribers table gets added.
    You no need to do any thing. Just deploy your service and after that you should able to see record in the table. If record is not created then connection is not established between Topic and your service.
    I have doubt with the endpoints only
    jms://localhost:8011/aqjms.XATopicConnectionFactory/AqTopic
    Your JNDI name for connection factories given as aqjms/XATopicConnectionFactory and here its aqjms.XATopicConnectionFactory. Can you check it.
    Apart of this everthing looks same. Try above and let us know it.
    Regards,
    Tarak.
    Edited by: Tarak on Nov 1, 2012 3:36 PM

  • EbXML Header Properties to JMS properties

    Hi,
    We are using the ebXML protocol(ebMS) and using JMS integration to set up the Internal Delivery Channel. We are not using Oracle AQ instead using BEA JMS.
    For inbound messages, we noticed that when the ebXML message gets enqueued on the JMS Queue but we dont get all the ebXML header properties in the JMS properties of the message. Looks like only those properties which are needed by Oracle B2B are coming into the JMS properties.
    In our current architecture, we will be needing some more of the ebxml headers (like Conversation Id, From Role, To Role, Receiver Routing Id,Sender Routing Id, Service etc).
    Similarly for the Outbound messages, some of the JMS properties that is being set by the mid tier layer which enqueues the message on the Queue is being overridden by Oracle B2B. Looks like the message id is being overwritten and also this mid tier layer explicitly sets the conversation id, To Role, Receiver Routing Id, Sender Routing Id and Ref To Msg Id etc.
    We are looking at these details as we will need to migrate to Oracle B2B without much impact on the other mid tier components.
    Please give your thoughts.
    Thanks
    Kavitha

    Hi Sinkar, Nandagopal,
    The following is the message we are trying to send:
    <mes:message transport="async" acknowledgeRequired="true"
    xsi:schemaLocation="http://www.bt.com/btgs/solutions/message ../../Schemas/messageV3.01.xsd"
    xmlns:mes="http://www.bt.com/btgs/solutions/message"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
         <mes:messageSequenceID>1166429678cRY</mes:messageSequenceID>
         <mes:messageType>incident</mes:messageType>
         <mes:messageAction>event</mes:messageAction>
         <mes:messageDateTime>2006-12-18T08:14:40.005Z</mes:messageDateTime>
         <mes:routingDataItem>
              <mes:param>source</mes:param>
              <mes:value>Expedio IM</mes:value>
              <mes:param>destination</mes:param>
              <mes:value>TP BT MOM Bridge</mes:value>
         </mes:routingDataItem>
         <mes:payload>
              <inc:incident xmlns:inc="http://www.bt.com/btgs/solutions/message/incident"
                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" majorVersion="1" minorVersion="1"
              xsi:schemaLocation="http://www.bt.com/btgs/solutions/message/incident ../../Schemas/IncidentV1.01.xsd">
                   <inc:sourceSystem type="Remedy" name="Expedio IM"/>
                   <inc:targetSystem type="TP" name="TP BT MOM Bridge"/>
                   <inc:incidentHeader supplierTicketRef="XF02958950" customerTicketRef="NA" masterTicketRef="unknown" supplierTicketCreateDate="2006-12-18T07:00:55.000Z">
                   <inc:customerDetails contactNumber="609-252-6596" customerContact="Jo Bloggs" customerContract="ABC123" customerID="23558" customerName="ENCO"/>
                   <inc:incidentContact>          
                        <inc:role>Prime Contact </inc:role>          
                        <inc:firstName>GCS Helpdesk </inc:firstName>          
                        <inc:lastName>GCS Helpdesk </inc:lastName>          
                        <inc:telephone>0800 282820 </inc:telephone>          
                   </inc:incidentContact>          
                        <inc:product xsi:type="inc:CPEproductType" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                             <inc:elementID>3212435</inc:elementID>
                             <inc:productID>67</inc:productID>
                             <inc:productType>Routers</inc:productType>
                             <inc:productName>Cisco 7204</inc:productName>
                             <inc:productDescription >Unknown</inc:productDescription>
                             <inc:aEndSite>
                                  <inc:siteName>RUSSIA:MOSCOW;17; BUILDING 1;KRYLATSKAYA STREET;121614</inc:siteName>
                                  <inc:siteReference>TMPRUS-01</inc:siteReference>
                                  <inc:siteID>390075</inc:siteID>
                                  <inc:city>MOSCOW</inc:city>
                                  <inc:country>RUSSIAN FEDERATION</inc:country>
                                  <inc:postcode>121614</inc:postcode>
                                  <inc:location>
                                       <inc:subPremise>BUILDING</inc:subPremise>
                                  </inc:location>
                             </inc:aEndSite>
                             <inc:hostname>INB_RU_MOS01_RTR_01</inc:hostname>
                             <inc:serialNumber>74223995</inc:serialNumber>
                        </inc:product>
                        <inc:incidentTitle>Network Unreachable</inc:incidentTitle>
                   </inc:incidentHeader>
                   <inc:incidentBody>
                        <inc:incidentAction incidentAction="attribute change" incidentType="fault"/>
                        <inc:incidentPriority>2</inc:incidentPriority>
                        <inc:incidentSeverity>2</inc:incidentSeverity>
                        <inc:incidentStatus>in-progress</inc:incidentStatus>
                        <inc:logNotes>
                             <inc:noteLine timestamp="2006-12-18T08:14:38.000Z" author="macenadf">INITIAL VALUES:Element reported is INB_RU_MOS01_RTR_01 at RUSSIA:MOSCOW;17; BUILDING 1;KRYLATSKAYA STREET;121614.Assigned to Douglas Macena.Status set to WORK IN PROGRESS.Severity set to 2.Ticket submitted at 18/12/2006 07:00:55.</inc:noteLine>
                        </inc:logNotes>
                   </inc:incidentBody>
              </inc:incident>
         </mes:payload>
    </mes:message>
    Do the header properties have to be modified here?
    Further no other details were obtained in the B2B opmn server logs besides Start and Stop OPMN
    Is there a stub we can run from WLI that can put a message on the JMS, that can be read by B2B?
    With Thanks & Regards,
    Suhas.

  • How to read JMS properties in BPEL

    I have a BPEL receiving from a JMS Adapter. I want to read JMS properties set in the message in BPEL which is to be used later in the process. Is it possible ?
    Any help is appreciated.

    SOA Suite 11g - how to set/get JMS headers ?

  • I couldn't locate policy.properties or sso directory in Oracle AS10.1.3.1.1

    I'm trying to do SSO, configured policy in Access Manager as per integration steps in b25347.pdf
    I couldn't locate policy.properties or sso directory in Oracle AS10.1.3.1.1
    I dont know what i'm missing ?

    Thank you,Madrid!
    I have resolved the problem by setting the
    ORACLE_HOME to the right value.
    And thank all of you.
    But I still can't unstand why I could connect tothe
    database through user "system" without setting
    ORACLE_HOME environment variable???Hi everyone,
    I too, have encountered this problem. The user i
    used to install Oracle 10g Express is a member of
    ORA_DBA group AND it also has Windows admin. rights.
    However, i am not able to connect / as SYSDBA.
    Where and how in Windows can I verify ORACLE_HOME
    environment variable? and where can i check if it is
    pointing to oracle_sid? i have search for this
    pattern but was unable to find it.
    Thanks all for your help!Thanks everyone for all your replies. I verified and sure enuf, oracle_sid was not set the the db name
    Thanks!

  • JMS properties supported in the JMS Service?

    Hello,
    We are trying to send some JMS properties using the JMS Service and are not having any luck. Specifically, we need to set a JMSType...it appeared that customHeaders in the JMSMessageType (jms.xsd) should facilitate this, however, the properties we send in the name/value pair part of the customHeader in the jmsMessage is not getting through to the recieving side (neither a bpel jms listener nor a pojo listener). This suggests that perhaps this is not supported in the current version??
    Or am I doing something wrong?
    Thanks for the help.
    Cheers,
    Dustin

    Nope, im using the inbuilt JMS queues that come coupled with the deveopler install of the process manager... I can see the header variables when i dont try to use correlation but when i correlate them the header variables on the receive are empty!
    I've also had a bash at trying to get native correlation to work with the JMS adapter but not having much (any!) luck... Any chance you have some resources for that?
    Cheers
    Ian

Maybe you are looking for

  • Changing the Hierarchy of File organisation in iTunes Media.

    Hi All, Am sure many are facing this issue that i have, from what posts I've seen so far. It's the issue of having sorted or organised your music with iTunes, and when you need to move songs to your phone or back up external HArd Disk, we need to mov

  • What is the wrong with my select query

    HI All, TYPES: BEGIN OF t_equi,          equnr          TYPE equi-equnr,          aedat          TYPE equi-aedat,          matnr          TYPE equi-matnr,          sernr          TYPE equi-sernr,          kunde          TYPE equi-kunde,          zzre

  • Why do I get the Application Error jqsnotify.exe-Application Error. The memory could not be read?

    Why do I get this error message every time i opened up Firefox saying: jqsnotify.exe-Application Error and then at the bottom line it says: The instruction at "0x5ff3d322"referenced memory at " 0xe41203c3". The memory could not be "read". Click on OK

  • Javascript code for setting output file name of emailed form in Livecycle

    I was given a task of creating a new form with livecycle. I have no knowledge of javascripting so I am struggling with one of the things I am trying to get this form to do. The overview of this form is people around my company fill out this form then

  • Computer not recognizing ipod, and getting music off it

    first, i want to put my music from ipod onto new computer....but i dont want to pay for that yami thing...anyway to do it free??? and my computer wont even recognize my ipod when i plug it in? i have already installed itunes, so im confused