Compare creation of Datasources and JMS Queues : SAP vs (Weblogic/Websphere

I am used to creating JDBC Datasources and JMS Queues on Weblogic/Websphere thru their Admin applications.
Can someone compare/contrast that process to that on SAP's netweaver ( either using NWA or Visual Administrator).
Thanks

Hi Parag,
For the process of creating JDBC datasources and JMS resources @ SAP NetWeaver you can refer to the documents here on SDN and help.sap.com, and compare that process for yourself, thus not being influenced by others' biased or unbiased opinions.
For NetWeaver 04 and 04s these would be:
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/b0/6e62f30cbe9e44977c78dbdc7a6b27/frameset.htm">JDBC Connector Service</a>
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/22/cf4e71c46cdb4da31153be96c5389f/frameset.htm">JMS Connector Service</a>
For the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/javaee5">Java EE 5 Edition</a>:
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7bb9751d-0e01-0010-febd-c3adce2c408c">Working with Database Tables, DataSources and JMS Resources</a>
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/806e75a0-0e01-0010-2587-fc518de8ac1a">Administration Guide</a> -> section "Application Resources Management" (pages 89-104)
Hope that helps!
Your feedback/findings are very welcome!
-Vladimir

Similar Messages

Authentication problem w MDB on WL8.1 and JMS Queue on WL6.1

          Hi,
          I'm having problems with a MessageDrivenBean that is deployed on a Weblogic 8.1
          server. It listens to a JMS Queue on a Weblogic 6.1 server.
          I'm getting the following error message upon deployment:
          [java.lang.SecurityException: Authentication for user system denied in realm wl_realm
          I've made sure that both servers are installed with the user "system" and a password
          of "password".
          This worked fine for two WL6.1 servers.
          Here's my ejb-jar.xml:
          <!DOCTYPE ejb-jar PUBLIC
          '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN'
          'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
          <ejb-jar>
              <enterprise-beans>
                  <message-driven>
                      <ejb-name>WebResponseJMSBean</ejb-name>
                      <ejb-class>com.ditech.webresponse.jms.WebResponseJMSBean</ejb-class>
                      <transaction-type>Container</transaction-type>
                      <message-driven-destination>
                          <destination-type>javax.jms.Queue</destination-type>
                      </message-driven-destination>
                  </message-driven>
              </enterprise-beans>
              <assembly-descriptor>
                  <container-transaction>
                      <description>Transaction attributes for 'WebResponseJMSBean' methods</description>
                      <method>
                          <ejb-name>WebResponseJMSBean</ejb-name>
                          <method-name>*</method-name>
                      </method>
                      <trans-attribute>NotSupported</trans-attribute>
                  </container-transaction>
              </assembly-descriptor>
          </ejb-jar>
          Here's my weblogic-ejb-jar.xml:
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC
          '-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
          'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
          <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
                  <ejb-name>WebResponseJMSBean</ejb-name>
                  <message-driven-descriptor>
                      <destination-jndi-name>com.ditech.jms.CowResponseQueue</destination-jndi-name>
                      <provider-url>t3://localhost:7003</provider-url>
                      <connection-factory-jndi-name>com.ptp.jms.AppOnlineConnectionFactory</connection-factory-jndi-name>
                  </message-driven-descriptor>
                  <jndi-name>ejb/WebResponseJMSBean</jndi-name>
              </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          Can anyone give me any suggestions?
          Thanks in advance,
          -Ben


          We are facing a similar issue, between MDB's and JMS Queues on 2 separated WebLogic
          8.1 domains. What I will test next week are:
          1. In the domain where my MDB's are deployed, configure Foreign JMS Servers/Connection
          Factories/Queues, for which passwords can be specified (not possible in weblogic-ejb-jar.xml)
          2. If No.1 does not work, I will add CredentialGenerated="false" in <SecurityConfiguration>
          in config.xml in both domains
          3. If No. 2 still does not work, I will specify run-as principal and security-role
          in my MDB DD files, and specify CredentialMapping via the WebLogic admin console.
          Maybe you can try the same?
          Eric Ma
          "B Liu" <[email protected]> wrote:
          >
          >Hi,
          >
          >I'm having problems with a MessageDrivenBean that is deployed on a Weblogic
          >8.1
          >server. It listens to a JMS Queue on a Weblogic 6.1 server.
          >
          >I'm getting the following error message upon deployment:
          >
          >[java.lang.SecurityException: Authentication for user system denied in
          >realm wl_realm
          >
          >I've made sure that both servers are installed with the user "system"
          >and a password
          >of "password".
          >
          >This worked fine for two WL6.1 servers.
          >
          >Here's my ejb-jar.xml:
          >
          ><!DOCTYPE ejb-jar PUBLIC
          >
          >'-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN'
          >
          >'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
          >
          >
          ><ejb-jar>
          >
          >    <enterprise-beans>
          >
          >        <message-driven>
          >
          >            <ejb-name>WebResponseJMSBean</ejb-name>
          >            <ejb-class>com.ditech.webresponse.jms.WebResponseJMSBean</ejb-class>
          >            <transaction-type>Container</transaction-type>
          >            <message-driven-destination>
          >                <destination-type>javax.jms.Queue</destination-type>
          >            </message-driven-destination>
          >
          >        </message-driven>
          >
          >    </enterprise-beans>
          >
          >    <assembly-descriptor>
          >
          >        <container-transaction>
          >
          >            <description>Transaction attributes for 'WebResponseJMSBean'
          >methods</description>
          >            <method>
          >                <ejb-name>WebResponseJMSBean</ejb-name>
          >                <method-name>*</method-name>
          >            </method>
          >            <trans-attribute>NotSupported</trans-attribute>
          >
          >        </container-transaction>
          >
          >    </assembly-descriptor>
          >
          ></ejb-jar>
          >
          >Here's my weblogic-ejb-jar.xml:
          >
          ><?xml version="1.0"?>
          >
          >
          >
          ><!DOCTYPE weblogic-ejb-jar PUBLIC
          >
          >'-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
          >
          >'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
          >
          >
          ><weblogic-ejb-jar>
          >
          >    <weblogic-enterprise-bean>
          >
          >        <ejb-name>WebResponseJMSBean</ejb-name>
          >
          >        <message-driven-descriptor>
          >
          >            <destination-jndi-name>com.ditech.jms.CowResponseQueue</destination-jndi-name>
          >            <provider-url>t3://localhost:7003</provider-url>
          >            <connection-factory-jndi-name>com.ptp.jms.AppOnlineConnectionFactory</connection-factory-jndi-name>
          >        </message-driven-descriptor>
          >
          >        <jndi-name>ejb/WebResponseJMSBean</jndi-name>
          >
          >    </weblogic-enterprise-bean>
          >
          ></weblogic-ejb-jar>
          >
          >
          >Can anyone give me any suggestions?
          >
          >Thanks in advance,
          >-Ben
          >

Are Connection Factory and JMS Queue supposed to be in JNDI tree

I have created Connection Factory and JMS Queue. I am expecting to find both in JNDI tree. Where, in the http://localhost:7001/console/consolejndi.portal, could I find them? I mean, in which branch of the JNDI tree?

Hi,
You should find them following exactly the way you define their JNDI Names... Make sure you are looking into the JNDI tree for the right managed server... Pay attention into the targets of your connection factory and queue...
For example, a JNDI name jms.myConnectionFactory (or jms/myConnectionFactory) targeted to soa_server1 will appear under soa_server1 / jms / myConnectionFactory ...
Hope this helps...
Cheers,
Vlad

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.

Creation of cube and dso in sap bi 7.0

This topic has ben discussed here often. Kindly search the forums before posting a new thread. Unfortunately I would have to lock this thread.
Hi
Can any body tell me the how to create the cube as well an dso in bi 7.0 version thougt i how to create cube and ods in sap bi 3.5 version but i want to update my knowledge more what are main diif b/w 3.5 and 7.0 i had ask this question further also but i will be very greate full if any give me own hand made Answer rather than the for diff b/w 3.5 and biw 7.0
regards
gurkiran
Edited by: Dinesh Lalchand on Feb 12, 2009 12:53 PM
Edited by: Dinesh Lalchand on Feb 12, 2009 12:55 PM

Hi ,
I am trying to migrate the Transaction data sources before moving into the DEV from Sandbox.
So i have to delete the existing TR/UR's and trying to create the transformation, but while creating transformation fields mapping is not happend automatically. (For manul field mapping the transaction data is the time taking process)
We are using the spk 8 . Please let me know any one has faced the above problem .
Regards
Jose

BAM EMS to read payload from JMS queue in remote weblogic domain

Hi ,
I am trying to connect to JMS queue located in different web logic domain using oracle BAM EMS configuration. But my EMS configuration is not able to start .
Please find below details,
Name:
OSBBAM_EMSProcessor
Owner:
XXXXX
Created:
9/23/2014 12:05:21 AM
Last modified:
9/24/2014 10:58:58 PM
Status:
Test failed - BAM-00553: Resources start operation for destination jms/OSBBAM_EMSQ failed.
Initial Context Factory:
weblogic.jndi.WLInitialContextFactory.
JNDI Service Provider URL:
t3://xx.xxx.xx.xx.:xxxx.
Topic/Queue Connection Factory Name:
jms/osbConnectionFactory.
Topic/Queue Name:
jms/OSBBAM_EMSQ.
JNDI Username:
XXXX
JNDI Password:
XXXXXXX
JMS Message Type:
TextMessage.
Durable Subscriber Name (Optional):
Message Selector (Optional):
Data Object Name:
/BAMPOC/BAM_AuditTable.
Operation:
Insert.
Batching:
No.
Transaction:
No.
Start when BAM Server starts:
Yes.
JMS Username (Optional):
JMS Password (Optional):
Can any one guide me how to proceed with that?I have already tried with trusted setup in WLS and foreign server but It did not work.

You can refer to the following link for the detailed steps :-
Link :[http://www.informit.com/articles/article.aspx?p=170722&seqNum=3]

ODS Delta Process, DataSource and Delta Queue

Hi to all,
loading data from a SAP source system into SAP BW 7.0 via generic 3.x datasource causes problems.
Here is a short description:
The data flow is from a source table using a generic extractor into a target ODS in full update mode.
Update rules should move data from table structure into ODS structure in this way:
Source table structure
CustKey1     Key2
13386          C23
13386          B14
13387          A13
13387          E25
ODS structure
CustKey1     col1     col2
13387          A13     E25
This works pretty well - as long as all records with the same CustKey1 are transfered in the same data package. Data Browser (SE16) shows the situation in ODS-"New data" view (data is not activated):
Request    Data_packet_number     Data_record_number      CustKey1
112           000003                  1.061              0000013386
112           000004                      1              0000013386
112           000004                      2              0000013387
There are two records for CustKey1 0000013386 with
data record 1.061 in data packet 000003   and
data record       1 in data packet 000004.
The obove constellation is the cause for errors in the ODS Delta Queue and subsequent data processing.
I think there may be one solution to solve the problem by changing the Delta Process of the Data Source.
The properties are:
- Record type: Full, delta, before, after images
- Delta type: Delta from delta queue or from extractor
- Serialization: No serialization, serialization of request, serialization of data packages
But how can I change these settings? Transactions RSA2 RSO2 RSO6 RSO8 don't do this.
What is the right delta process to use?
I have tried changing the delta process generating several 3.x datasources with the following delta processes (see table RODELTAM)
- " " (Full-upload)
- AIE
- ADD
Unfortunately with no effect.
Who can help?
Regards
Josef
Edited by: Josef L. on Mar 20, 2009 7:44 PM

hi venkat,
whenever you load a delta from ods to cube , whatever the data changed in ods since last delta will be updated, hence from you case, both req1 and req2 will be loaded to cube.
Assign Points if useful
Ramesh

Gerneric Datasources and Outbound Queue

Dear Experts,
I've got some generic Datasources (Delta and Full Update) that work properly with productive BW-System.
Now I'm starting to build up an developement system (wrong order I know) and want to load data using the mentioned Datasources from time to time to get relevant data for testing.
Problem now is, that the generic delta Datasources fail accourding to doublicate keys (loading to dev-system) although in the basic tables for these datasources no doublicate keys are existing (or even are possible due to the table key).
I realized in smq1, that every time when data is transfered to productive BW-System, the counter to the queue for dev-System is incremented. When I delete all the entries in smq1 all the updates for dev-System work fine.
In one of the threads here I read, that generic Datasources do not have outbound queues. (Re: Generic Data Source issue).
So is there any way to turn of the outbound queues for specific (generic) Datasources? I do not want to turn them of in general as we use standard delta Datasources for Controlling.
Or how is the "normal" way to transfer data to a dev-System?
(One more information: productive system is 3.5; dev-system is 7.1.)
Thank you in advance
Kind regards
Philip
Edited by: Philip Munz on Nov 17, 2009 8:50 AM

ok,
after some days of searching and reading I now understand my problem.
For all, who face the same problems in understanding delta-updates, qrfc, rsa7 and so on, please have a look at
http://www.sdn.sap.com/irj/scn/index;jsessionid=(J2EE3417800)ID0216771750DB11245246034303112354End?rid=/library/uuid/40427814-376a-2c10-5589-bc1aaa6692c3&overridelayout=true
again thanks for the help
kind regards
Philip

Creating Datasource and Extracting from SAP R/3 ECC 6.0

Hello Gurus,
I am very new in BI field, I am learning through notes provided in this Blog.
Curretnly I need to know how we create Datasource at SAP R/3 ECC 6.0 (is there any difference b/t these?)
and how we may extract data from R/3 ECC 6.0 Source System.
Looking for your kind reply
Thanks in Advance
KK

You can use any specific Extractors to Create Data Source in R/3 side.
Let me explain with Generic Extraction
Goto SBIW--> you can see all the extractions here
Generic extractors are of 3 types:
1. Based on table/view
2. Based on Info set Query
3. Based on Function module
If you would like to create a custom table, then goto SE11>Select Table>Click on Create (Now create you own table here & use this table while creating Transaction data)
Goto RS02-->Select Transaction data.
Click on Create
Choose an application component to which the data source is to be assigned
Click on Generic Delta
Specify the Delta-Specific and the type for the field.
Specify a safety interval
Select Data type>Save> Now Data source was generated successfully
After generating the data source , you will find Delta Flag checked.
Please go through the following link for Generic Delta
[https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
Once you've done with Data Source in R/3 side--> u need to Replicate it to BI
Goto RSA1>source system>Select the Source system in which u've created Data source>R.C select Data Source Overview>Select the Application Component to which Data source is assigned>R.C Select Replicate dataSorce>here you can see your NEW Data source
Hope it helps!

Oracle BPM and JMS Queue: How to associate data from Map Messages to Process Data Objects?

Good Day!
I'm currently working on a project wherein it tries to get data from a JMSqueue Map Message being populated by CEP.
After CEP pushes some data in the JMSqueue. I have BPM configured with a JMS adapter to look up whether there are any messages to be processed upon.
Inside BPM, I want to know how can I correlate the data from the Map Message to my Process Data Object.
For example, If I have a Map Object wherein it has 3 attributes:
FirstName:String
LastName:String
Age:int
What is the expression I need to use inside Oracle BPM Data Association screen in order to map the data from the Map Messages into my process data objects?
Thanks!
Regards,
Jeff

Any ideas? Thanks!

Create jms queue xml data server

Hi,
What's the difference between jms queue and jms queue xml data servers and how to create jms queue xml data server.
Thanks.

Hello,
JMS messages can principally be processed by Oracle Data Integrator in two formats:
- JMS Messages: containers for rows of data, handled through JMS Queue/JMS Topic Technologies. With JMS Queue/JMS Topic technologies, each JMS destination is defined similarly to a flat file datastore. Each message in the destination is a record in the datastore.
- XML Messages: containers for XML files, handled through JMS XML Queue/JMS XML Topic Technologies. With JMS XML Queue/JMS XML Topic technologies, each messages payload contains a complete XML data structure. This structure is mapped into a relational schema (XML Schema) which appears as a model. This use the Oracle DI Driver for XML (see the driver documentation in Oracle DI documentation).
Find below a step by step creation process for such a destination:
1. Data Server
To create a JMS XML Queue data server, you declare a simple JNDI connection. The only JMS XML specific information is added to the URL. This information defines the XML file format.
The JNDI URL should be : <JMS_RESOURCE>?d=<DTD_FILE>&f=<XML_FILE>&s=<SCHEMA>&JMS_DESTINATION=<JMS_DESTINATION_NAME>
- JMS_RESOURCE: JNDI resource corresponding to your JMS queue that will contain the XML payload. You would specify this URL if you were managing normal JMS messages.
- DTD_FILE: path to a DTD file that describes the XML structure. Mandatory if the parameter XML_FILE is omitted.
- XML_FILE: path to the XML file with a structure similar to the expected XML messages. Mandatory if the DTD_FILE parameter is omitted.
- SCHEMA: schema name that will contain the XML structure. This value must match the one set for the physical schema attached to this data server. This parameter is mandatory.
- JMS_DESTINATION_NAME: name of the JMS queue or topic. This parameter is mandatory.
2. Schema
Creation is straightforward: In the Schema (Schema) and Schema (Work Schema), enter the name of the <SCHEMA> defined in the data server JNDI URL.
3. Model
Use standard reverse-engineering. As the Oracle DI Driver for XML is used the XML structure will be reversed as a relational structure.
Regards,
- FX

Using socket and JMS protocol in the same logic for OSB

Hi frnds,
In my organization...the only communication protocol used is "socket" protocol. However, I want to use JMS protocol to process incoming messages. Can somebody help me figuring out how to go about it.
Using some nice OSB blogs, I am able to create the JMS connection factory and JMS queues in weblogic. And that works fine when I select the communication protocol as JMS while creating the BS and PS.
What should be my message flow when the communication protocol used is "socket" for both BS and PS.
salil

Hi,
Make the BS as JMS and the PS as socket, in the PS's flow do a route for the BS... Then if an external call is made to the PS via socket, it will send a messages to a JMS queue...
Hope this helps...
Cheers,
Vlad

MDB and JMS on different servers

Hi,
My MDB is deployed on a different domain from the JMS server. Both are on weblogic.
While deploying weblogic, I m getting an error: Unable to create a connection.
Can anyone give pointers?
I have ensured the following:
1. The JMS server starts before the MDB server
2. The following data is mentioned in weblogic-ejb-jar.xml:
jndi name of the remote queue
provider url--- t3://hostName:port
jndi name of the remote connection factory
is there anyting else that i m missing ?
thanx and regards
Shivraman Giri

Hi,
Thanx for responding.
I will keep in mind these points when I use a foreign JMS provider. T
Right now I m getting problem when the JMS provider is remote but native ie. MDB and JMS are both on Weblogic. This obviates the need to mention Initial Context. Only the provider URL is to be specified.
Can you suggest a reason as to why i my EJB container (first weblogic ) is unable to connect to JMS provider (another weblogic)
regards
S.G

IS XI Support BEA Weblogic JMS Queue

Hi
I have a scenario where i have to send and recive message from the Weblogic JMS Queue ..
Is XI support Weblogic JMS Queue ..if it is which tranport protocol i have to use to connect to Weblogic queue
SV

Hi
Thanks Ravi..
U mean to say i have to use the Transport Protocol
Access JMS Provider with JNDI
I have few more questions like ..
what needs to filled in Connection parameters:
JNDI Look up name of Queue Connection Factory:
JNDI Look up name of JMS Queue:
Name of JNDI Initial Context Factory:
JNDI Sever Address:
JNDI Logon User:
JNDI Logon Password:
When i selected the Protocol some default Values came in do i have have to change any thing
JNDI Look up name:
JNDI Look up name of JMS Queue:
Name of JNDI Initial Context:
as u mentioned in Server address i will put : t3://server:XXX
and i have given the user id and Password ..
the user id and password is same for both JNDI logon and JMS Queue User..
SV

Talking to WL JMS Queue via HTTP

Hi,
We have a web application running on weblogic server 6.1. We were able to talk (in our case, this involved sending it xml input) to this application through the weblogic JMS by hitting the JMS queue via a java program on the same box. What we need to do now is to talk to that same JMS queue using HTTP. In other words, be able to post an HTTP message from a different box to the JMS queue on this weblogic server.
How do we do that? Please assume I know as little as possible.
Thanks so much.
Avraham

One way to do this is to create a servlet that forwards the incoming HTTP message to the queue. In order to access a remote box you probably just need to package the JMS client library with the servlet's WAR file. In this setup, the servlet is basically a router between the HTTP side and the JMS side. You can also create a JAX-RPC web service if you want the HTTP input to follow a specific XML structure.
- Bjarne.

Compare creation of Datasources and JMS Queues : SAP vs (Weblogic/Websphere

Similar Messages

Maybe you are looking for