Running weblogic examples and Jms configuration
I am new to JMS. I configured the JMS server using the weblogic console page and i created JMS server under Services. I am having only one server. I am starting the console using http://localhost:7001/
Now i want to run the examples of weblogic (QueueSend.java and QueueReceive.java).
What are the changes i have to do in the given java files and how to run the examples.
Please give the steps to configure JMS server and run the example and what are the parameters i have to pass to these file?
Thank you
Hello,
I am having problem with WL. I use version 8.1 with multiple server.
The Admin server works fine, but when I try to start other servers, I am getting the following errors.
Aug 23, 2005 2:48:16 PM EDT> <Error> <NodeManager@*.*:5555> <SocketInputHandler: Command read failed 'Read channel closed.' on socket /127.0.0.1>
<Aug 23, 2005 2:48:16 PM EDT> <Error> <NodeManager@*.*:5555> <Failed to write to socket Read channel closed., to /127.0.0.1>
<Aug 23, 2005 2:48:16 PM EDT> <Error> <NodeManager@*.*:5555> <Failed to write to socket Write Channel Closed, possible SSL handshaking or trust failure, to /127.0.0.1>
<Aug 23, 2005 2:48:20 PM EDT> <Info> <NodeManager@*.*:5555> <Starting Server devDomain::buyerserver1 ...>
<Aug 23, 2005 2:48:21 PM EDT> <Info> <NodeManager@*.*:5555> <Server devDomain::buyerserver1 started, process id = 4,068>
<Aug 23, 2005 2:49:33 PM EDT> <Info> <NodeManager@*.*:5555> <__COMMAND_DONE__>
Can someone please help?
Thank you.
Similar Messages
-
Running weblogic server and workshop on 2 different machines
hi all,
My computer cannot handle both the server and workshop running on it, at the same time.
1) installed weblgic server, created domain on computer A.
2) mapped the domain\source code(working in dev mode) on computer A to computer B.
3) I open up the .work file in the mapped drive from workshop on computer B.
Problem:
Computer B never completes "Scanning .. source...", very processor intensive.
Any help, very much appreciated.
Novice!Workshop is a pig and the scanning thing spikes my CPU everytime (1.8Ghz P4 and 1G memory). Please make it better.
-
What is the association between JMS Server and JMS Module in weblogic 10?
Hi,
I have a created a ConnectionFactory, Queue, Topic under JMS Modules in Weblogic Server 10 using admin console.
And I have created a JMS Server and Targetted to the current running server (Admin Server).
But when I run the Queue Sender program it is unable to LookUP the jndi which I gave for Queue.
queue = (Queue) initialContext.lookup("jndi_queue");
Exception:
javax.naming.NameNotFoundException: Unable to resolve 'jndi_queue'.
But I configured this jndi name when I create the Queue in JMS Module in Weblogic Server 10.
How JMS Module and JMS server are associated.
My Doubt is if i have several JMS Modules and only one JMS Server created then how does the JMS Server identifies which Queue/Topic belongs to which JMS Module????
Please advice.
Thanks....Hi,
Once you have JMS servers configured:
Step 1: Target the JMS configuration module to the cluster that will host the destination, or, if not using clustering, target the module to the individual WL server that will host the JMS server.
Step 2: Configure a "subdeployment" for the module and set it to reference the exact JMS server(s) that will host the destination. If you're using a distributed desitnation, you can specify multiple JMS servers, if you're using a regular destination, only specify a single destination.
Step 3: Create a destination resource in the module, and set its subdeployment to the subdeployment you specified in step 1 (the console calls this "advanced targeting"). As a best practice avoid the "default targeting" option for the resource - always choose subdeployment (advanced) targeting.
For more information, reference the "best practices" chapter of the JMS configuration guide:
http://download.oracle.com/docs/cd/E14571_01/web.1111/e13738/best_practice.htm#CACJCGHG
I also I highly recommend the JMS chapter of the book "Professional Oracle WebLogic".
Hope this helps,
Tom -
Weblogic.xml.security.SecurityConfigurationException running encrypt example
Hi,
I am trying to run the tutorial examples that are detailed at http://webservice.bea.com.
I am having problems running the encrypt SOAP messages example.
The command line client version works fine (the full transaction goes smoothly,
returning me the string I sent using the encryption). The browser version, though
, gives me an error.
(See attached).
I am using WLS 8.1. sp2.
I configured the server keystore and client keystore using the command line utilities
included
in the zipped example.
I configured the servers default identity asserter as well as the ssl & keystore
according to the
instructions of the zipped file.
Thanks in advance.i meet the same problem as Juan Campos'.
the error information as follow:
Request sent to the server
<!--REQUEST.................-->
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
</env:Header>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Exception during processing: weblogic.xml.security.SecurityConfigurationException: Service requires signed requests, but no Token was provided (see Fault Detail for stacktrace)</faultstring>
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">weblogic.xml.security.SecurityConfigurationException: Service requires signed requests, but no Token was provided
at weblogic.webservice.core.handler.WSSEClientHandler.processSpecs(WSSEClientHandler.java:325)
at weblogic.webservice.core.handler.WSSEClientHandler.handleRequest(WSSEClientHandler.java:101)
at weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.java:143)
at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:231)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:423)
at weblogic.webservice.server.servlet.ServletBase.invokeMultiOutput(ServletBase.java:349)
at weblogic.webservice.server.servlet.WebServiceServlet.invokeMultiOutput(WebServiceServlet.java:354)
at weblogic.webservice.server.servlet.ServletBase.invokeOperation(ServletBase.java:300)
at weblogic.webservice.server.servlet.WebServiceServlet.invokeOperation(WebServiceServlet.java:344)
at weblogic.webservice.server.servlet.ServletBase.handleGet(ServletBase.java:266)
at weblogic.webservice.server.servlet.ServletBase.doGet(ServletBase.java:158)
at weblogic.webservice.server.servlet.WebServiceServlet.doGet(WebServiceServlet.java:255)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
</bea_fault:stacktrace>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
Response from the server
<!--RESPONSE.................-->
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<env:Header>
</env:Header>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Exception during processing: weblogic.xml.security.SecurityConfigurationException: Service requires signed requests, but no Token was provided (see Fault Detail for stacktrace)</faultstring>
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">weblogic.xml.security.SecurityConfigurationException: Service requires signed requests, but no Token was provided
at weblogic.webservice.core.handler.WSSEClientHandler.processSpecs(WSSEClientHandler.java:325)
at weblogic.webservice.core.handler.WSSEClientHandler.handleRequest(WSSEClientHandler.java:101)
at weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.java:143)
at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:231)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:457)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:423)
at weblogic.webservice.server.servlet.ServletBase.invokeMultiOutput(ServletBase.java:349)
at weblogic.webservice.server.servlet.WebServiceServlet.invokeMultiOutput(WebServiceServlet.java:354)
at weblogic.webservice.server.servlet.ServletBase.invokeOperation(ServletBase.java:300)
at weblogic.webservice.server.servlet.WebServiceServlet.invokeOperation(WebServiceServlet.java:344)
at weblogic.webservice.server.servlet.ServletBase.handleGet(ServletBase.java:266)
at weblogic.webservice.server.servlet.ServletBase.doGet(ServletBase.java:158)
at weblogic.webservice.server.servlet.WebServiceServlet.doGet(WebServiceServlet.java:255)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
</bea_fault:stacktrace>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
i try Bruce Stephens' advise,but don't know exactly how to do,(which certificate should be imported?)will someone please tell the details? -
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).
ThanksHi 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 -
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. -
Running Weblogic 8.1 SP3 and IPlanet 6.0 on same machine
I have requirement to run Weblogic Platform SP3 and IPlanet 6.0 servers on same Solaris machine
for a client of ours.
Please let me if we can do this. What kind of issues we may run into.
Thanks,
SanjayHi
Of course, you can install both at the same machine.
Only remember the memory required ... and the real memory available ... this for don't have swap problems.
Remember too if you are planning to create WLS clusters ... BEA recommends 1 cluster per CPU ... and reserve 1 CPU for the iPlanet web Server. Even, you can install all clusters and web server as your machine support ( under load, try to mantain the CPU usage under 70-80%).
Jin -
What privileges user should have to install and run weblogic on linux box
What privileges user should have to install and run weblogic on linux box ?
Hello.
Normal user if you don't want to listen to ip port < 1024 or write in protected directories (like /var).
Regards. -
Trying to run the example "rf record and playback reference application"
http://zone.ni.com/devzone/cda/epd/p/id/5894 trying to run this example but a lot of files are not being found. I'm using Labview 8.5 with version 4 of the sound and vibration toolkit. I suspect the problem is the old toolkit version. Can someone confirm? Can't find any info on upgrading to toolkit so I suppose it would mean a new purchase? thanks
Hello Mike,
This example is designed for our RF Hardware platform. You need the RFSG driver, RFSA driver, Spectral Measurements Toolkit, Modulation Toolkit, and the advanced signal processing toolkit for the example to run. You should be able to see this under the software requirements at the bottom of the page. The two drivers should be available for download on our website, but the toolkits must be purchased and they aren't generally available with the dev suite.
I hope this helps,
Paul C
Message Edited by Paul C. on 03-11-2010 12:28 PM -
MQ/WebLogic Topology and Architecture
I am new to MQ and am trying to get my head around a couple of basic "big
picture" things; I'll explain what I think is going on and hopefully someone
will jump in when I'm off in the weeds. I need to do is integrate a J2EE
application with a legacy MQ system and as you might expect, I cannot alter
that system, I must accommodate it (which J2EE is designed to do).
MQ is designed to be distributed; the idea that you'll install an MQ Server
on every Application Server machines seems like a special case. In my case,
it's academic.
First MQ itself:
There appears to be some internal and proprietary things MQ needs to do for
efficiency and possibly historical reasons. To achieve that, you must install
an MQ Client on each machine so that access appears to be local for Applications
that talk to MQ. I have written some code that talks directly to the server
using some of the Client libraries and I was able to send but could not get
messages off the queue; I found some documentation that said that this would
be the case in some circumstances. I suspect that the reason for this is
that I may have not used the "correct" client libraries since I found some
example code that doesn't yet run (we can ignore that for now).
The Client install does give you Java classes that provide connectivity and
it implies JMS support but in what form, since the classes appear to use
proprietary code?
Does the Client have the ability to run as a JMS Server that appears to be
a local JMS nexus that I can talk to with standard JNDI lookups?
WebLogic J2EE Integration:
The ultimate goal here is to integrate an existing MQ installation so I can
send and recieve from a J2EE Application I am working on.
I have been reading that there's at least three different ways to make this
connection.
1) Roll your own using the proprietary lib clients in a startup class
2) Using WebLogic's Bridge technology
3) Use WebLogic's Foreign Destination configuration.
Detailed questions below by item number:
1) -> I understand that directly using IBM's client libraries is supposed
to function the same as running the Client locally, that doesn't sound like
it would give the scalability of pooling and that solution won't route to
drive MDBs.
2) -> A lot of posts state that for WL/MQ integration this is not necessary.
I don't know a lot about the specifics of what I will need to do to talk
to this other system yet, I am just trying to get my head around the general
cases.
3) -> This is the most appealing to me since it sounds like it is a matter
of using the WL console to set up the JMS destination once I have the correct
libraries in the server's classpath. It would seem that the JMS queues look
like they are local, I can drive MDBs from this with all the manageability
built in. However, does the server use the same provider factory class as
I would in my own code or are there special considerations?
Comments and pointing to specific reading encouraged (don't just say, to
read the 677 page Java MQ docs).
ThanksWow! All I can say is "Thanks", it's gonna take we a while to get through
all this but I do appreciate the help. I tried to get the Client stuff installed
on my Linux dev box but it's not clear which rpms are needed and some complained
because I am still running RH7.3. I am in the process of moving to a supported
platform RHEL3.x or above... stay tuned.
Hello Tom,
> Hi!
>
> If you haven't already done it, the best place to start is to read
> through the entire "Integrating Remote JMS Providers" FAQ:
>
> http://e-docs.bea.com/wls/docs81/faq/interop.html
>
> I'm also appending my own integration notes which mention MQ (and
> which you may have already run across). I update these notes from
> time to time. Enjoy!
>
> Tom, BEA
>
> JMS Integration of Foreign Vendors with BEA WebLogic Server
> -----------------------------------------------------------
>
> The following notes are derived mostly from
> "http://dev2dev.bea.com/technologies/jms/index.jsp".
>
> For additional questions, a good forum for WebLogic questions in
> general is "newsgroups.bea.com". These can be mined for information by
> using Google's newsgroup search function.
>
> JMS Integration Overview
> ------------------------
> - For integration with "non-Java" and/or "non-JMS" platforms, see
> "Non-Java Integration Options" below.
>
> - For a foreign JMS vendor to participate in a WL transaction it must
> support XA. Specifically, it must support the javax.jms.XA*
> interfaces.
>
> - In WL versions 6.0 and up it is possible to make synchronous calls
> to foreign JMS vendors participate in a WL transaction as long as the
> foreign vendor supports XA.
>
> - WL 6.0 and 6.1 MDBs can be driven by foreign vendors
> non-transactionally. They can be driven transactionally by a select
> few foreign vendors (MQ is not part of the select few)
>
> - WL 7.0 and later, MDBs can be driven by foreign vendors
> transactionally and non-transationally.
>
> - WL 6.1 and later WL provides a messaging bridge feature. Messaging
> bridges forward messages between any two JMS destinations, including
> foreign destinations, and can transfer messages transactionally or
> non-transactionally.
>
> - WL 8.1 JMS provides additional features that simplify transactional
> and JNDI integration of foreign vendors. See
> http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features and
> http://e-docs.bea.com/wls/docs81/faq/interop.html
>
> Integration with 8.1 Details
> ----------------------------
> To start, first read the "Integrating Remote JMS Providers FAQ"
> (released in Dec 2004) at:
> http://e-docs.bea.com/wls/docs81/faq/interop.html
>
> A good overview of 8.1 JMS interop capability is the presentation
> "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
>
> http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/App
> lication_Servers/1097-Foreign_JMS_Providers_WLS.pdf
>
> This document refers to helpful new 8.1 features, which simplify
> integration. These include:
> http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_
> foreign_providers
> http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
> And are also summarized here (under interoperability):
> http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
> Also read the MDB documentation, which extensively covers integrating
> foreign vendors:
>
> http://edocs.bea.com/wls/docs81/ejb/message_beans.html
>
> The 8.1 features are likely sufficient for most 8.1 integration needs,
> but you may want to refer to the "Using Foreign JMS Providers With
> WLS" white-paper mentioned below, which is 7.0 specific but contains
> specific examples of configuring non-WebLogic JMS vendors. See also
> notes on "MQ" below.
>
> Integration with 6.1 and 7.0 Details
> ------------------------------------
> Read the "Using Foreign JMS Providers With WLS" white-paper:
>
> http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
>
> Note that this white-paper does not take into account 8.1 features.
>
> For 7.0 read the extensive 8.1 MDB documentation, which largely also
> applies to 7.0:
>
> http://edocs.bea.com/wls/docs81/ejb/message_beans.html
>
> Non-Java Integration Options
> ----------------------------
> - WL JMS has a JNI based C client which is available for Windows and
> some UNIX platforms. This C client supports 7.0 and up, and will be
> officially packaged with WLS in 9.0 (virtually unchanged). The C API
> is currently only supported through the jms newsgroup. See "JMS C
> API", here:
>
> http://dev2dev.bea.com/technologies/jms/index.jsp
>
> - WL supports direct Windows COM access through its "JCOM" feature.
> This doesn't include the JMS API, but one can invoke EJBs which in
> turn invoke JMS. See
>
> http://e-docs.bea.com/wls/docs61/jcom.html
>
> http://e-docs.bea.com/wls/docs70/jcom/
>
> http://e-docs.bea.com/wls/docs81/jcom/
>
> - Similar to JCOM, but more advanced and supported on more platforms,
> WL supports access via the standard IIOP protocol. You can use the
> BEA Tuxedo C client for this purpose (no license fee). This doesn't
> include the JMS API, but one can invoke EJBs which in turn invoke JMS.
> See
> http://e-docs.bea.com/wls/docs81/rmi_iiop/
> http://e-docs.bea.com/wls/docs70/rmi_iiop/
> http://e-docs.bea.com/wls/docs61/rmi_iiop/
> Unlike most other approaches, the IIOP client approach also allows the
> client to begin and commit user (JTA) transactions (not configured).
> - If you already have a BEA Tuxedo license, one option is communicate
> through BEA Tuxedo (which has various APIs on Windows) and configure a
> WebLogic Server to respond to these requests via the WTC bridge.
> Search for "WTC" in the BEA docs. Unlike most other approaches, the
> Tuxedo API approach also allows the client to begin and commit user
> (JTA) transactions.
>
> - Another approach is to interop via web-service standards. Or even to
> simply to invoke a servlet on the WL server using a basic HTTP call
> from the client. These operation in turn can invoke the JMS API.
> There is a white-paper on "Interoperability Study of BEA WebLogic
> Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates
> web-services here:
> http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
>
> - Yet another approach is to use a third party product that is
> designed to wrap any JMS vendor. There are even open source
> versions. In no particular order, here are some examples: Open3
> WinJMS, CodeMesh, Active JMS, SpiritSoft
>
> - Finally, there are .NET/C/C++ integration libraries that are not
> specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
>
> Notes on MQ Remote Capable XA Clients
> -------------------------------------
> Until recently, IBM MQ JMS clients could not work transactionally
> unless they were running on the same host as their MQ server. This is
> a limitation unique to MQ that was relaxed with the introduction of
> IBM's new "WebSphere MQ Extended Transactional Client". See:
>
> http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
>
> The product is new, and for some reason, configuration of this client
> seems to be tricky, even when WebLogic is not involved at all. Oddly,
> the main sticking point seems to be simply making sure that class
> paths refer to the required IBM jars:
>
> - Required on WLS where MQ objects are bound into JNDI:
> com.ibm.mq.jar, com.ibm.mqjms.jar
>
> - Required only if MQ objects are bound into JNDI on a different
> server: com.ibm.mq.jar
>
> If there are problems when using this client, first get it to work
> using a pure IBM client without any BEA classes involved. Once that
> is working, search the WL JMS newsgroup for answers and/or contact BEA
> customer support.
>
> Notes on Oracle AQ Integration
> ------------------------------
> If problems are encountered integrating Oracle's built-in queuing
> (Oracle AQ) JMS client, there is publicly available wrapper code that
> can aid integrating AQ directly into MDBs, JMS, or the messaging
> bridge. The solution is titled "Startup class to bind
> AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is
> posted to:
>
> http://dev2dev.bea.com/codelibrary/code/startupclass.jsp (older
> version) http://xa-compliant-oracleaq.projects.dev2dev.bea.com (newer
> version)
>
> Caveats:
>
> It may be that the solution doesn't directly support concurrent
> consumers. Perhaps Oracle requires that concurrent consumers each
> have a unique JMS connection? As a work-around, parallel message
> processing can be achieved indirectly by forwarding AQ messages into a
> WL JMS destination - which do support concurrent processing.
>
> Up-to-date versions of Oracle may be required. For more information,
> google search the weblogic.developer.interest.jms newsgroup for
> "Oracle" and "AQ".
>
> MDB Thread Pool Notes
> ---------------------
> WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to
> specify which thread pool an MDB uses to run its instances. In most
> cases this field should be configured to help address potential
> performance issues and/or dead-locks:
>
> http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-
> policy
>
> (Note that "dispatch-policy" is ignored for non-transactional foreign
> vendors; in this case, the MDB "onMessage" callback runs in the
> foreign vendor's thread.)
>
> MDB Concurrency Notes
> ---------------------
> Queue MDBs driven by foreign providers can run multiple instances
> concurrently. Topic MDBs driven by foreign providers are limited to
> one instance (not sure, but transactional foreign driven topic MDBs
> may not have this limitation). The size of the thread pool that the
> MDB runs in and the "max-beans-in-free-pool" descriptor limit how many
> instances run concurrently.
>
> Design Guide-Lines and Performance Tuning Notes
> -----------------------------------------------
> The "WebLogic JMS Performance Guide" white-paper contains detailed
> design, performance, and tuning information for Clustering, Messaging
> Bridge, JMS, and MDBs.
>
> http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD
> .jsp
> -
Startup Classes and JMS - Suggestions Please!
I'm in serious need of having several resources initialized before beans
start handling requests.
I tried implementing a Weblogic Startup Class, and it works fine - as long
as it's the first thing
to run! -- the problem is, when my Message Driven Beans deploy, if there are
messages waiting
for them in their durable subscriptions, they immediately start
processing... then about 30 seconds
later Weblogic (6.0sp1) gets around to starting my startup class. If I put
code in each MDB that
kicks off the initialization when they are invoked I still run into
problems, because my initialization
takes a LONG time (more than 2 minutes) - so I end up with lots of
transaction rollbacks... which
are very annoying and clutter up the log files, and scare customers of the
product.
Is there anyway to make a startup class/servlet/something that runs and
completes before any
other processing occurs?
Thanks,
JamesYes, Startup servlet has the same problem - it doesn't 'startup' until after
jms messages are already being delivered. :( aside from this, there are
class loader issues -servlet space and ejb space are not the same...
Thanks though,
James
"minjiang" <[email protected]> wrote in message
news:[email protected]...
Hi, did you ever try startup servlet? not startup class?
mj
James House wrote:
The only problem with creating a base class to extend is the fact that
Java only supports single inheritance, -- and I'm already inheriting...
>>
I've been involved with many projects that use WLServer, and in
almost every one of them, there has been a need for a startup class
that fires before the server starts handling requests.... strange that
I'd be the only one to need this, when the need has recurred so often.
James
"Raja Mukherjee" <[email protected]> wrote in message
news:[email protected]...
James,
If you have common initialization tasks to be shared by multiple MDBs,
I
would create an abstract class (a.k.a BeanAdapter class) where you canhave
all your initialization logics and have your MDB extend from it.
I am not convinced that the Startup class needs to run first. In fact,
I
have the same view that Startup class should run last. My only wishlist
for
startup class was that I should be able to specify order, which isaddressed
in 6.1.
I am also getting the feeling from different posts that MDB deploymentwould
have a re-try logic in 6.1, which I am beginning to look into. Check
(or
post) in JMS news group.
.raja
"James House" <[email protected]> wrote in message
news:[email protected]...
Thanks for the help... I like the pattern you pointed me to better
than
anything else... ... but in all cases (your method, Gene's, and whatI'm
currently doing) I still have to put some code in every MDB that
I deploy... : (
Put in a good word for me there at BEA and convince the appropriate
developer that startup classes should run first!
James
"Raja Mukherjee" <[email protected]> wrote in message
news:[email protected]...
James,
There are several ways to solve your problem. I normally use
setMessageDrivenContext to do all my initialization. There are two
types
of
initialization that I have performed here, first, reading theconfiguration
file and then load some utility classes in specific order. The
problem
with
the second was that you will have to use synchronized block
w/HotSpot
2.0
to
keep the order, which is ok. I don't use static block to do the
initialization, instead use an init() metod. Hopefully you got the
idea.
Recently, Gene Chuang created a pattern which esentially does the
same
and
I
liked the pattern because it was a nicer way of doing what I
needed to
do.
I
have changed all my examples to customer to use the new pattern.
You
can
find it in
http://theserverside.com/patterns/thread.jsp?thread_id=7270.
The
only think I do not use of this pattern is
initializeEveryContextSwap()
method. I am not convinced yet that I would need it (of course
that
might
change over the time).
Hope this helps, and thanks Gene.
.raja
"James House" <[email protected]> wrote in message
news:[email protected]...
Ok... here's some more detail:
The application is largely JMS based, and most of my Session
EJBs
are
invoked only my Message Driven Beans.
I have a large set of properties that need to be read from a
config
file,
and stored somewhere "globally". I also have a number of
utilities
that
need to get "warmed up" before I start doing any real processing(before
I start receiving messages from the JMS Topics). These
utilities
take
a
long time to warm up (a long time being about 45-60 seconds) -
because
they are loading hundereds of classes, and creating variousconnections
to external resources.
Currently I'm creating a Singleton object that reads the
configuration
file
name from an environment property, and it then parses the file,
and
starts
configuring all of these utilities. Since the "Startup Class"
didn't
work
(weblogic invokes it after I'm already receiving messages), I
put
code
at
the beginning of all of my MDB's onMessage() methods that calls
the
singleton's "getInstance()" method - which synchronizes on alock
object,
and does all of it's work.
I don't like this solution because:
1- I have to put code in EVERY message-driven bean that I
create -
if
I
forget one, everything is broken.
2- I have to increase the transaction time out of the entire
server
to
be over 60 seconds since the beans hang that long while theconfiguration
is
happening.
It seems very obvious that a "Startup Class" should be invoked
after
the
server has come completely up, but before it starts listening
for
requests -- isn't the whole point of a "startup class" to getthings
ready
that need to be done as soon as the server comes up? but alas,
the
person
who designed this at BEA apparently didn't agree with me on this
point!
Any suggestion on better solutions would be greatly appreciated.
James
"Raja Mukherjee" <[email protected]> wrote in message
news:[email protected]...
You can do it this way, but I would not recommend it, unless
that's
the
only
way to attack the problem at hand. But that's just me.
I have seen this problem with multiple clients and in most
cases
there
is
a
better way to handle it. If James give us a little more
information
on
what
type of configuration is he talking about and some background
of
his
application, we as a group can think and may be able to come
up
with
some
idea.
.raja
"Joel Nylund" <[email protected]> wrote in message
news:[email protected]...
you could wrap the starting of weblogic in your own class
and do
initialization
there. You have to be careful because of the way weblogic
classloaders
work, but
you may be able to do what you want. Weblogic is just a java
class,
so
you
can
start your class, then once your done initializing, just
call
weblogic.Server.main
-Joel
James House wrote:
I'm in serious need of having several resources
initialized
before
beans
start handling requests.
I tried implementing a Weblogic Startup Class, and it
works
fine -
as
long
as it's the first thing
to run! -- the problem is, when my Message Driven Beans
deploy,
if
there
are
messages waiting
for them in their durable subscriptions, they immediately
start
processing... then about 30 seconds
later Weblogic (6.0sp1) gets around to starting my startupclass.
If
I
put
code in each MDB that
kicks off the initialization when they are invoked I still
run
into
problems, because my initialization
takes a LONG time (more than 2 minutes) - so I end up with
lots
of
transaction rollbacks... which
are very annoying and clutter up the log files, and scarecustomers
of
the
product.
Is there anyway to make a startup class/servlet/something
that
runs
and
completes before any
other processing occurs?
Thanks,
James -
Integrating SOA and Peoplesoft: Configuring JMSTARGET Connector in IB.
Hi All,
I have created JMS queue/topic in oracle application server. Can anybody idea how can we configure JMS connector of peoplesoft integration broker.
Let me first explain my requirement, I am working in peoplesoft outbound interface design with SOA integration.
So my approach will be creating JMS queue in oracle application Server and then configuring this JMS to any node of peoplesoft IB.
Then extracted information from peoplesoft need to send to the above node so that once the node receive the message it should
populate the JMS queue inturn SOA BPEL will be triggered to write into third party file/database.
Please give your inputs on this approach if you any other suggetion for peoples soft outbound integration with SOA.
Thanks inadvance.Its published, but somehow you are unable to see it..issues with Meatlink for sure..
Here is its content :
Applies to:
PeopleSoft Enterprise PT PeopleTools - Version: 8.4 - Release: 8.4
Information in this document applies to any platform.
This document was previously published as Customer Connection Solution 201077819
Symptoms
Please see below.
Cause
Not Applicable
Solution
<<Document:664816.1>> E-IB: Configuring Integration Broker with IBM MQ on AIX
SPECIFIC TO: Enterprise, PeopleTools, Integration Broker Release 8.49
ISSUE:
How to setup Integration Broker to PUT messages to an IBM MQ Server on a remote machine?
SOLUTION:
<See attachment for documentation with screenshot examples.>
Configuring Integration Broker with IBM MQ on AIX
The following guide is intended to outline the setup between Peoplesoft Integration Broker and IBMs Websphere MQ version 6 client on AIX. Note: This is not a certification, but a working example, specifically using the MQ client to connect to a remote machine running the MQ server.
Platform Information:
PeopleSoft PeopleTools 8.49
IBM Websphere MQ Release 6
AIX
Steps
1) Install and IBM Websphere MQ (WMQ) client
2) Configure WMQ connection
3) Configure Peoplesoft
4) TEST using PING and a Peoplesoft message to PUT data onto the WMQ server
Steps
1) Install and configure Websphere MQ client on AIX where Peoplesoft is located
NOTE: This is one optional architecture. It is also possible to install Peoplesoft and MQ on the same server, which avoids the client software altogether.
a. IBM deliveres an MQ client that is installed on the same box as the Peoplesoft with the following options.
i. Installed to /usr/mqm, all objects owned by local user mqm
ii. Ensure that the MQ Extended Transactional Client is installed
1. This includes com.ibm.mqetclient.jar file
iii. Mq specific environment variables
1. $MQ_JAVA_DATA_PATH=/usr/mqm
2. $MQ_JAVA_INSTALL_PATH=/usr/mqm/java
3. $MQ_JAVA_LIB_PATH=/usr/mqm/java/lib
4. jms.jar, fscontext.jar, jndi.jar, providerutil.jar, stcjms.jar
iv. CLASSPATH
1. Includes the following MQ jar files
i. com.ibm.mqetclient.jar
ii. providerutil.jar
iii. com.ibm.mqjms.jar
iv. ldap.jar
v. jta.jar
vi. jndi.jar
vii. jms.jar
viii. connector.jar
ix. com.ibm.mq.jar
2. Example
a. > echo $CLASSPATH
i. echo $CLASSPATH /usr/mqm/java/lib/com.ibm.mqetclient.jar:/usr/mqm/java/lib/providerutil.jar:/usr/mqm/java/lib/com.ibm.mqjms.jar:/usr/mqm/java/lib/ldap.jar:/usr/mqm/java/lib/jta.jar:/usr/mqm/java/lib/jndi.jar:/usr/mqm/java/lib/jms.jar:/usr/mqm/java/lib/connector.jar:/usr/mqm/java/lib/fscontext.jar:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib:/usr/mqm/java/bin
3. When setting up Peoplesoft, add these jar files to the classpath setting in the setenv.sh file and reboot PIA
2) Configure WMQ
a. Edit JMSAdmin.config (located in /usr/mqm/java/bin)
ii. Set Initial Context Factory = com.sun.jndi.fscontext.RefFSContextFactory
# The following line specifies which JNDI service provider is in use.
# It currently indicates an LDAP service provider. If a different
# service provider is used, this line should be commented out and the
# appropriate one should be uncommented.
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
iii. Set PROVIDER_URL=file:/usr/mqm/java
# The following line specifies the URL of the service provider's initial context. It currently refers to an LDAP root context. Examples of a file system URL and WebSphere's JNDI namespace are also shown, commented out.
#PROVIDER_URL=ldap://polaris/o=ibm,c=us
PROVIDER_URL=file:/usr/mqm/java
#PROVIDER_URL=iiop://localhost/
b. Run JMSAdmin to setup queue and qcf to the MQ server
i. def qcf(PLAS160_QCF) HOSTNAME(GSPLVP006-VM2) PORT(1414) CHANNEL(SYSTEM.DEF.SVRCONN) QMANAGER(QM_gsplvp006_vm2) TRANSPORT(CLIENT)
ii. NOTE: When connecting from a client to a remote server, it is important to specify the hostname, port and transport along with the other values.
iii. def q(PLAS160_Q) queue(PLAS160_Q)
1. Note: The q is a local naming alias, whereas the queue is the physical queue name on the MQ server
iv. Screenshot:
v. This creates a .bindings file
vi. NOTE: It is also possible to use IVTSetup for this, but JMSAdmin is recommended.
vii. NOTE: It is possible to gain a .bindings file from your MQ server administrator. Be sure that this format is correct, and the location on the client is referenced correctly.
viii. JMSAdmin can also be used to determin what connections are available from this machine using command dis ctx as shown
b. Optional: Test the connection to the MQ server using IBM software.
NOTE: Testing the ivtQ and ivt QCF can be accomplished using the IVTRun program, provided that the ivtQ and ivtQCF have been setup in the .bindings file with the same available on the MQ server (some mq administrators do not enable this by default)
i. Example IVTRun, see Appendix 1
ii. Example .bindings file see Appendix 2
3) Configure PeopleSoft
a. Create an external NODE representing the target JMS queue
i. Example node, see appendix 3
b. Setup the connectors properties for the new node
i. Use the connector ID= JMSTARGET
ii. Example properties screenshot, see Appendix 4
1. Notes
a. JMSProvider is MQSeries
b. JMSFactory, JMSQueue are those specified in the .bindings file representing that on the JMS server. In this case, PLAS160_QCF and PLAS160_Q are used for this example.
c. JMSUrl is the location of the working .bindings file on the web server (in this case file:/D:/apps/IBM/WebSphereMQ/Java )
c. Setup Gateway Properties
i. Access the Gateway Properties using PIA and add the JMS information for MQSeries to the integrationgateway.properties file as shown:
## JMS configuration Section
# <the following line is required>
ig.jms.JMSProvider.JNDIFactory.MQSeries=com.sun.jndi.fscontext.RefFSContextFactory
ii. Queue information here is only needed if going to GET message using the JMSListeningConnector. Not needed for the target PUT (or ping)
iii. Example integrationgateway.properties, See appendix 5
4) Test PUT connection from Peoplesoft to WMQ
1. Ping the JMS node from the node definition
b. Setup routings to PUT messages to the MQ node
i. Example using USER_PROFILE
ii. Submit the message and check the Operations Monitor
iii. Verify that the message made it to MQ (this is viewed by browsing the queue on the Websphere MQ Explorer, message browser. A better utility is rfhutil which is included in the MQ windows client development kit)
NOTE: This document is intended for 1 way communication TO Mq from Peoplesoft. Setup for GET using the JMSListeningConnector is a separate topic for documentation.
Appendix 1 IVTRun
Appendix 2 .bindings file.
NOTE: The PLAS160_QCF and PLAS160_Q references are applicable to this example.
#This file is used by the JNDI FSContext.
#Wed Sep 17 11:43:13 PDT 2008
PLAS160_QCF/RefAddr/9/Type=SRC
PLAS160_Q/RefAddr/5/Encoding=String
PLAS160_QCF/RefAddr/13/Content=5000
PLAS160_QCF/RefAddr/3/Content=GSPLVP006-VM2
PLAS160_Q/RefAddr/8/Content=PLAS160_Q
PLAS160_QCF/RefAddr/13/Type=PINT
PLAS160_QCF/RefAddr/1/Type=TRAN
MYPUT/RefAddr/2/Content=-2
PLAS160_QCF/RefAddr/6/Encoding=String
PLAS160_QCF/RefAddr/17/Type=RINT
PLAS160_QCF/RefAddr/5/Type=CHAN
PLAS160_QCF/RefAddr/18/Encoding=String
PLAS160_Q/RefAddr/2/Content=-2
PLAS160_PUT/RefAddr/1/Encoding=String
PLAS160_QCF/RefAddr/20/Content=SYSTEM.DEFAULT.MODEL.QUEUE
PLAS160_PUT/RefAddr/3/Type=PER
MYPUT/RefAddr/6/Encoding=String
PLAS160_Q/RefAddr/5/Content=0
PLAS160_PUT/RefAddr/8/Content=PLAS160_PUT
PLAS160_Q/RefAddr/6/Encoding=String
MYPUT/RefAddr/0/Type=VER
PLAS160_PUT/RefAddr/7/Type=FIQ
PLAS160_QCF/RefAddr/7/Encoding=String
MYPUT/RefAddr/4/Type=CCS
PLAS160_PUT/RefAddr/2/Content=-2
PLAS160_QCF/RefAddr/19/Encoding=String
PLAS160_PUT/RefAddr/5/Content=0
PLAS160_PUT/RefAddr/2/Encoding=String
PLAS160_Q/RefAddr/3/Type=PER
MYPUT/RefAddr/8/Type=QU
MYPUT/RefAddr/7/Encoding=String
PLAS160_Q/RefAddr/7/Encoding=String
MYPUT/ClassName=com.ibm.mq.jms.MQQueue
PLAS160_Q/RefAddr/7/Type=FIQ
PLAS160_QCF/RefAddr/8/Encoding=String
PLAS160_QCF/RefAddr/6/Type=CCS
MYPUT/RefAddr/9/Content=
PLAS160_QCF/RefAddr/10/Type=SFIPS
PLAS160_QCF/RefAddr/10/Encoding=String
PLAS160_PUT/RefAddr/3/Encoding=String
PLAS160_QCF/RefAddr/20/Type=TM
MYPUT/RefAddr/8/Encoding=String
PLAS160_Q/RefAddr/8/Encoding=String
PLAS160_QCF/RefAddr/14/Type=MBS
PLAS160_QCF/RefAddr/17/Content=5000
PLAS160_QCF/RefAddr/2/Type=QMGR
PLAS160_PUT/FactoryName=com.ibm.mq.jms.MQQueueFactory
PLAS160_QCF/RefAddr/7/Content=\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000
MYPUT/FactoryName=com.ibm.mq.jms.MQQueueFactory
MYPUT/RefAddr/3/Content=-2
PLAS160_PUT/RefAddr/0/Type=VER
MYPUT/RefAddr/6/Content=273
PLAS160_QCF/RefAddr/18/Type=TCM
PLAS160_QCF/RefAddr/9/Encoding=String
PLAS160_QCF/RefAddr/11/Content=false
PLAS160_QCF/RefAddr/1/Content=1
PLAS160_Q/RefAddr/6/Content=273
PLAS160_QCF/RefAddr/11/Encoding=String
PLAS160_QCF/RefAddr/20/Encoding=String
PLAS160_PUT/RefAddr/4/Type=CCS
PLAS160_PUT/RefAddr/4/Encoding=String
PLAS160_QCF/RefAddr/14/Content=10
PLAS160_QCF/RefAddr/4/Content=1414
PLAS160_Q/RefAddr/9/Content=
MYPUT/RefAddr/9/Encoding=String
MYPUT/RefAddr/0/Content=6
MYPUT/RefAddr/1/Type=EXP
PLAS160_Q/RefAddr/9/Encoding=String
PLAS160_PUT/RefAddr/8/Type=QU
PLAS160_Q/RefAddr/0/Content=6
PLAS160_Q/RefAddr/0/Type=VER
MYPUT/RefAddr/5/Type=TC
PLAS160_Q/RefAddr/3/Content=-2
PLAS160_QCF/RefAddr/0/Encoding=String
PLAS160_PUT/RefAddr/6/Content=273
PLAS160_QCF/RefAddr/21/Content=
PLAS160_Q/RefAddr/4/Type=CCS
MYPUT/RefAddr/9/Type=QMGR
PLAS160_QCF/RefAddr/21/Encoding=String
PLAS160_PUT/RefAddr/9/Content=
PLAS160_QCF/RefAddr/12/Encoding=String
PLAS160_PUT/RefAddr/5/Encoding=String
MYPUT/RefAddr/0/Encoding=String
PLAS160_Q/RefAddr/8/Type=QU
PLAS160_Q/RefAddr/0/Encoding=String
PLAS160_PUT/RefAddr/0/Content=6
PLAS160_Q/FactoryName=com.ibm.mq.jms.MQQueueFactory
PLAS160_PUT/RefAddr/3/Content=-2
PLAS160_QCF/RefAddr/7/Type=CT
PLAS160_QCF/RefAddr/1/Encoding=String
PLAS160_QCF/RefAddr/11/Type=SPAG
PLAS160_QCF/RefAddr/21/Type=TQPFX
PLAS160_QCF/RefAddr/13/Encoding=String
PLAS160_QCF/RefAddr/22/Encoding=String
PLAS160_PUT/RefAddr/6/Encoding=String
PLAS160_QCF/RefAddr/15/Type=FIQ
PLAS160_QCF/RefAddr/3/Type=HOST
MYPUT/RefAddr/1/Encoding=String
PLAS160_PUT/RefAddr/1/Type=EXP
PLAS160_QCF/RefAddr/19/Type=MNST
PLAS160_QCF/RefAddr/2/Encoding=String
PLAS160_PUT/RefAddr/5/Type=TC
PLAS160_QCF/FactoryName=com.ibm.mq.jms.MQQueueConnectionFactoryFactory
PLAS160_QCF/RefAddr/14/Encoding=String
PLAS160_QCF/RefAddr/18/Content=true
MYPUT/RefAddr/2/Type=PRI
PLAS160_QCF/RefAddr/8/Content=0
MYPUT/RefAddr/4/Content=1208
MYPUT/RefAddr/2/Encoding=String
PLAS160_PUT/RefAddr/9/Type=QMGR
PLAS160_Q/ClassName=com.ibm.mq.jms.MQQueue
PLAS160_Q/RefAddr/1/Encoding=String
MYPUT/RefAddr/7/Content=1
PLAS160_Q/RefAddr/1/Type=EXP
MYPUT/RefAddr/6/Type=ENC
PLAS160_QCF/RefAddr/12/Content=true
PLAS160_QCF/RefAddr/2/Content=QM_gsplvp006_vm2
PLAS160_Q/RefAddr/7/Content=1
PLAS160_QCF/RefAddr/3/Encoding=String
PLAS160_Q/RefAddr/5/Type=TC
PLAS160_QCF/RefAddr/15/Content=1
PLAS160_QCF/RefAddr/5/Content=SYSTEM.DEF.SVRCONN
MYPUT/RefAddr/1/Content=-2
PLAS160_PUT/RefAddr/7/Encoding=String
PLAS160_QCF/RefAddr/15/Encoding=String
PLAS160_Q/RefAddr/9/Type=QMGR
MYPUT/RefAddr/3/Encoding=String
PLAS160_Q/RefAddr/1/Content=-2
PLAS160_Q/RefAddr/2/Encoding=String
PLAS160_Q/RefAddr/4/Content=1208
PLAS160_QCF/RefAddr/8/Type=CTO
PLAS160_PUT/RefAddr/7/Content=1
PLAS160_QCF/RefAddr/22/Content=1
PLAS160_QCF/RefAddr/12/Type=UCP
PLAS160_QCF/RefAddr/0/Type=VER
PLAS160_QCF/RefAddr/4/Encoding=String
PLAS160_QCF/RefAddr/22/Type=MRET
PLAS160_QCF/RefAddr/16/Type=LA
PLAS160_PUT/ClassName=com.ibm.mq.jms.MQQueue
PLAS160_QCF/RefAddr/4/Type=PORT
PLAS160_PUT/RefAddr/8/Encoding=String
PLAS160_QCF/RefAddr/16/Encoding=String
PLAS160_PUT/RefAddr/1/Content=-2
PLAS160_PUT/RefAddr/4/Content=1208
PLAS160_Q/RefAddr/3/Encoding=String
PLAS160_PUT/RefAddr/2/Type=PRI
PLAS160_PUT/RefAddr/6/Type=ENC
PLAS160_QCF/RefAddr/5/Encoding=String
MYPUT/RefAddr/3/Type=PER
PLAS160_PUT/RefAddr/9/Encoding=String
PLAS160_QCF/RefAddr/17/Encoding=String
MYPUT/RefAddr/4/Encoding=String
PLAS160_Q/RefAddr/2/Type=PRI
MYPUT/RefAddr/7/Type=FIQ
PLAS160_Q/RefAddr/4/Encoding=String
PLAS160_QCF/ClassName=com.ibm.mq.jms.MQQueueConnectionFactory
PLAS160_QCF/RefAddr/16/Content=
PLAS160_Q/RefAddr/6/Type=ENC
PLAS160_QCF/RefAddr/6/Content=819
PLAS160_QCF/RefAddr/19/Content=true
PLAS160_QCF/RefAddr/9/Content=0
MYPUT/RefAddr/5/Content=0
PLAS160_PUT/RefAddr/0/Encoding=String
MYPUT/RefAddr/8/Content=PLAS160_PUT
PLAS160_QCF/RefAddr/10/Content=false
MYPUT/RefAddr/5/Encoding=String
PLAS160_QCF/RefAddr/0/Content=6
Appendix 3 Node definition
Appendix 4 - Node JMSTarget Connectors Properties
Appendix 5 integrationgateway.properties JMS configuration section
## JMS configuration Section
#The JNDIFactory Classnames for Weblogic, IPlanet, MQSeries.
#ig.jms.JMSProvider.JNDIFactory.Weblogic=weblogic.jndi.WLInitialContextFactory
#ig.jms.JMSProvider.JNDIFactory.IPlanet=com.sun.jndi.fscontext.RefFSContextFactory
ig.jms.JMSProvider.JNDIFactory.MQSeries=com.sun.jndi.fscontext.RefFSContextFactory
#ig.jms.JMSProvider.JNDIFactory.OracleApplicationServer=com.evermind.server.rmi.RMIInitialContextFactory
# Enter the number of Queue listners to instantiate
#ig.jms.Queues=1
# For each queue specify the following properties
# Name
# Provider
# JMSFactory name (which is binded to the JNDI)
# MessageSelector (optional Message Filter)
# JNDI System File URL
# JMS User
# JMS Password
# Example :
#ig.jms.Queue1=QUEUE_VAS
#ig.jms.Queue1.Provider=MQSeries
#ig.jms.Queue1.JMSFactory=QCF
# ig.jms.Queue1.MessageSelector=
#ig.jms.Queue1.Url=file:/D:/apps/IBM/WebSphereMQ/Java
# ig.jms.Queue1.User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.Password=EncryptedPassword
# ig.jms.Queue1.SecurityPrincipal=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.SecurityCredentials=EncryptedPassword
#IBInfoHeaders
#ig.jms.Queue1.MessageName=QE_F18_ASYNC
#ig.jms.Queue1.MessageVersion=VERSION_1
#ig.jms.Queue1.RequestingNode=FromNode
#ig.jms.Queue1.DestinationNode=ToNode
# Use the supplied encryption utility to provide an encrypted password for the entry below
#ig.jms.Queue1.NodePassword=EncryptedRequestingNodePassword
#ig.jms.Queue1.SubChannel=SubChannel
# Enter the number of Topic Subscribers to instantiate
# ig.jms.Topics=1
# For each Topic specify the following properties
# Name
# Provider
# JMSFactory name (which is binded to the JNDI)
# MessageSelector (optional Message Filter)
# JNDI System File Url
# JMS User
# JMS Password
# Example :
# ig.jms.Topic1=ExampleTopic
# ig.jms.Topic1.Provider=MQSeries
# ig.jms.Topic1.JMSFactory=TopicConnectionFactory
# ig.jms.Topic1.MessageSelector=
# ig.jms.Topic1.Url=file:c:/
# ig.jms.Topic1.User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Topic1.Password=EncryptedPassword
# ig.jms.Queue1.SecurityPrincipal=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.SecurityCredentials=EncryptedPassword
#IBInfo Headers
#ig.jms.Topic1.MessageName=QE_F18_ASYNC
#ig.jms.Topic1.MessageVersion=VERSION_1
#ig.jms.Topic1.RequestingNode=FromNode
#ig.jms.Topic1.DestinationNode=ToNode
# Use the supplied encryption utility to provide an encrypted password for the entry below
#ig.jms.Topic1.NodePassword=EncryptedRequestingNodePassword
#ig.jms.Topic1.SubChannel=SubChannel
#For sending error either ErrorQueue or ErrorTopic must be configured
#If both exists, errors are only sent to ErrorQueues.
#Configure the Error-Queue configuration
# ig.jms.ErrorQueue=ErrorQ
# ig.jms.ErrorQueue-Provider=Weblogic
# ig.jms.ErrorQueue-User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.ErrorQueue-Password=sam
# ig.jms.Queue1.SecurityPrincipal=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.SecurityCredentials=EncryptedPassword
# ig.jms.ErrorQueue-JMSFactory=TopicConnectionFactory
# ig.jms.ErrorQueue-Url=file:c:/
#Configure the Error-Topic configuration
# ig.jms.ErrorTopic=Error
# ig.jms.ErrorTopic-Provider=IPlanet
# ig.jms.ErrorTopic-User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.ErrorTopic-Password=sam
# ig.jms.ErrorTopic-JMSFactory=TopicConnectionFactory
# ig.jms.ErrorTopic-Url=file:c:/
## End of JMS configuration Section
# Profile Information
# Set it to either TRUE or FALSE
ig.ProfileInformation=FALSE
#End-Of Profile Information
##EIPTestTool Properties
#Class name of the Gateway Manager to use during processing
#ig.gatewayManagerClass=com.peoplesoft.pt.integrationgateway.eiptesttool.EIPTestToolGatewayManager
#Contains a true or false value.
#True for LoopBack
#ig.EIPLoopBack=TRUE
#Contains the directory path that will be used
#to store request/response files during recording.
#ig.EIPOutputDirectory=c:/temp/output
# Number of ig.EIPMsgProp.N.propFile's
#ig.EIPMsgProp.count=0
#Certification root directory
#ig.EIPInputDirectory=c:/temp/input
#MessageProperty file names with locations.
#ig.EIPMsgProp.1.propFile=c:/temp/input/properties/pro1.xml
#ig.EIPMsgProp.2.propFile=c:/temp/input/properties/pro2.xml
#Overrides input directory for an EIP
#ig.EIPMsgProp.1.inputDirectory=c:/temp/input/properties1/
#EIPNodemapFileName
#ig.EIPNodeMap=c:/temp/nodemap.xml
##End of EIPTestToolProperties
#File connector password.
# Use the supplied encryption utility to provide an encrypted password for the entry below
ig.fileconnector.password=EncryptedPassword
#End of file connector properties.
## Query Access Services (QAS) Configuration Section.
# QAS Repository Home Directory. This is the directory where Query result blocks will be
# temporarily persisted.
# Example:
#ig.qas.repositoryHomeDir=C:/QASRepository
# Uncomment the following line and replace the value with the actual QAS Repository Home Directory.
#ig.qas.repositoryHomeDir=<Full-Path-For-Directory>
## END of QAS Configuration.
## AS2 Connector Properties.
# These Properties need to be set to use either the AS2TargetConnector or the AS2ListeningConnector
# REQUIRED:
# AS2 KeyStore Properties
# Uncomment the following two lines to specify your key keystore path and password.
# Use the PSCipher.bat utility to encrypt the keystore password.
# example:
# ig.AS2.KeyStorePath=C://pt846//webserv//peoplesoft//keystore//pskey
# ig.AS2.KeyStorePassword=GD9klUFw8760HVaqeT4pkg==
# OPTIONAL:
# AS2 Log Directory, logs all incoming and outgoing AS2 requests and responses.
# Uncomment and specify the correct directory name to enable logging.
# example:
# ig.AS2.LogDirectory = c://temp//as2//logs
## End of AS2 Connector Properties
## AS2ListeningConnector Only Properties.
# OPTIONAL:
# AS2From and AS2To http header parameters are required on all incoming AS2 messages. These parameters must
# map to PeopleSoft node definitions either directly or indirectly via AS2 From & To map specifications.
# AS2 From & To Map
# This map translates incoming AS2From and AS2To http header parameters into PeopleSoft node names.
# This property is not required if your incoming messages use AS2From and AS2To parameters that match
# existing PeopleSoft node definitions.
# ig.AS2.AS2ListenerMap.From.<AS2From>= Specify the PSFT Source Node Name.
# ig.AS2.AS2ListenerMap.To.<AS2To>= Specify the PSFT Target Node Name.
# This example translate AS2From from AS2SENDER to PSFT_SRC_NODE, and AS2To from AS2RECEIVER to PSFT_TGT_NODE.
# example:
# ig.AS2.AS2ListenerMap.From.AS2SENDER=PSFT_SRC_NODE
# ig.AS2.AS2ListenerMap.To.AS2RECEIVER=PSFT_TGT_NODE
# AS2 Message name
# Message name used to publish AS2 transactions.
# Use this property if the incoming AS2 Message Name is not in the HTTP Header or the URL.
# Replace <source> and <target> with either the incoming AS2From and AS2To http header parameters .
# when those match existing PeopleSoft node definitions, or with the PeopleSoft nodes names specified in the
# AS2 From & To map above.
# ig.AS2.<source>.<target>.MessageName= Specify the Message Name
# example:
# ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.MessageName=AS2_ORDER_REQUEST
# These Properties need to be set to use either the AS2TargetConnector or the AS2ListeningConnector
# REQUIRED:
# AS2 Certificates
# CertificateAlias is the certificate of the AS2 Listening Node used to decrypt incoming messages.
# SignerCertificateAlias is the certificate of the AS2From trading partner of Listening Node used to verify
# the incoming signature.
# Replace <source> and <target> with either the incoming AS2From and AS2To http header parameters
# when those match existing PeopleSoft node definitions, or with the PeopleSoft nodes names specified in the
# AS2 From & To map above.
# ig.AS2.<source>.<target>.CertificateAlias = Specify the target AS2 Listening Node certificate alias.
# ig.AS2.<source>.<target>.SignerCertificateAlias = Specify the source AS2From trading partner certificate alias.
# example:
# ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.CertificateAlias=<GeneratedAS2certificatealias>
# ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.SignerCertificateAlias=<GeneratedAS2certificatealias>
## End of AS2ListeningConnector Only Properties
## AS2 Target Connector Properties
# These Properties need to be set to use the AS2TargetConnector
# AS2 Original Request Information Log Directory
# This is required for Async MDN only. The Async MDN receiver uses this directory
# to find original request information.
# example:
# ig.AS2.AS2Directory=c://temp//as2
## END of AS2 Target Connector Properties.
#XML dtd lookup flag
# true - enable dtd reference lookup dtd on gateway. this is also the default value.
# false - disable dtd reference lookup on gateway.
ig.dtdLookup=true
# Maximum active connections to be cached on gateway
# These are connections from gateway to peoplesoft application server
# Caching connections will improve integration broker throughput
ig.connection=10
##################### -
Content Conversion - JDBC and JMS
Can we use File Content Conversion with JDBC and JMS ?
Hi,
How To Use the Content Conversion Module in JMS Adapter - https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000582377&
check this for JMS content conversion:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Check the how to guide provided by prabhu and also this link on the XMl To TeXtCoversion Module,
http://help.sap.com/saphelp_nw04/helpdata/en/44/748d595dab6fb5e10000000a155369/content.htm
Ref How To Use the Content Conversion Module in JMS Adapter -
https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000582377&
See this weblogs which was shown with examples:
How to use SAP's WebAS J2EE's JMS Queue in Exchange Infrastructure
Sync/Async communication in JMS adapter without BPM (SP19)
Async/Sync Communication using JMS adapter without BPM (SP 19)
Exploring JMS and SAP-XI JMS Adaper
Configuring the sender JMS adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
Configuring the receiver JMS adapter
http://help.sap.com/saphelp_nw2004s/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
Check JMS Adapter section of this blog by Sravya:
Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part III
Also information related to Provider-specific settings are available
http://help.sap.com/saphelp_nw2004s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
Plz do refer the following threads:
JMS Content Conversion - no CR/LF
Message (Data) getting lost after JMS Content Conversion(Sender)
Message (Data) getting lost after JMS Content Conversion(Sender)
Message (Data) getting lost after JMS Content Conversion(Sender)
Regards,
Vinod. -
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
>
-
Weblogic Admin server port configuration
Hi All,
I want to configure the Admin server port from 7001 to 80. Since I cant access Admin console, can we change this using the config files.If so, which file I need to
modify.
Environment: Oracle Enterprise Linux
Pl. provide me some inputs.
THanks
RajHi Raj
1. By default when you create a Weblogic Domain and choose all the defaults, it uses default port as 7001. There will NOT be any entry for this in config.xml file. Look for the file named config.xml file under yourDomain/config/ folder. You will not find any word like "7001" most of the times.
The entries related to this section are something like this in addition to extra tags between <server>...</server> for example:
<server>
<name>yourAdminServerName</name>
<listen-address/>
</server>
2. Take a back up of config.xml file. Make sure Server is not running. If someting goes wrong, use this backup config.xml file to restart the server.
3. Carefully edit config.xml file, the contents inside the above tag <server>...</server> by adding a new attribute as shown below by name <listen-port>
<server>
<name>DefaultServer</name>
<listen-port>80</listen-port>
<listen-address></listen-address>
<tunneling-enabled>true</tunneling-enabled>
</server>
All you do is add this one line: <listen-port>80</listen-port> within the <server>...</server> tags.
Restart the server. Access the weblogic console like this now http://localhost:80/console or http://localhost/console (port 80 is default and we do not need to type it manually).
Thanks
Ravi Jegga
NOTE: You can change the port from Admin Console also, siince you mentioned you do not have access to console, you can manually edit config.xml file.
Maybe you are looking for
-
New DVD-RW not recognized by iTunes
I replaced the original DVD-R in my 1 GHz TiBook with a Pioneer DVD drive model DVR-K05. Do I need to update drivers with this new optical drive? iTunes doesn't recognize the new writer and still lists the old Matshita UJ-815 DVD-R as the CD burner.
-
I am using ECC 5 version. In the ALV grid display, if we assign a box as a first field, we get selection boxes for each row and also in the Fields' header, we will have one more button to select All fields and columns in the list. I do not require 'S
-
Free Transform/Rotate Causes Flash CS3 to Crash
This problem is driving me nuts. I'm importing a 2000 x 3000 jpeg image and converting it to a symbol. everything seems fine until I try to do a free transform and rotate the image. Then when I proceed to cut the image, CS3 crashes. I can reproduce t
-
Hi, I need your help. After crashing Premiere CS3 I tried to re launch it and this appears [..\..Src\DirectoryRegistry.cpp-283] Can you please help me?
-
Officejet Pro 8600 print cartridge error
one or more cartridges appear to be damaged K. Message appeared after replacing the exhausted original black setup cartridge. I replaced the replacement cartridge with a new cartridge to no avail. I cleaned the contacts and even replaced all the o