JMS, MQSeries 5.2 and Websphere 4.0.2

How to configuring the WebSphere to work with MQSeries, Does anybody know how to do it.

I am getting the following Exception when trying ti run JMSAdmin with
INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
PROVIDER_URL=IIOP://localhost:900/
I Have websphere Advanced Single Server Edition
01:39:01 [1019853541907] [P=533785:O=0:CT] com.ibm.mq.jms.admin.AdminService@690726 initJNDI() javax.naming.ServiceUnavailableException exception caught: NULL returned when resolving initial reference=NameService
javax.naming.ServiceUnavailableException: NULL returned when resolving initial reference=NameService
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getCosRootContext(WsnInitCtxFactory.java:476)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:361)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:227)
     at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:98)
     at com.ibm.ws.naming.util.WsnInitCtx.<init>(WsnInitCtx.java:79)
     at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnInitCtxFactory.java:135)
     at com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(WsnInitialContextFactory.java:80)
     at com.ibm.ejs.ns.jndi.CNInitialContextFactory.getInitialContext(CNInitialContextFactory.java:68)
     at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
     at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
     at javax.naming.InitialContext.init(Unknown Source)
     at javax.naming.InitialContext.<init>(Unknown Source)
     at com.ibm.mq.jms.admin.AdminService.initJNDI(AdminService.java:192)
     at com.ibm.mq.jms.admin.JMSAdmin.<init>(JMSAdmin.java:126)
     at com.ibm.mq.jms.admin.JMSAdmin.main(JMSAdmin.java:1176)

Similar Messages

JMS, MQSeries, R/3 Link, NT and AIX...

Hi all,
To put you in situation, I have a java application which can run from any type of OS as of now. It sends documents to a queue (IDOCS) and those documents are then sent to SAP by an R/3 Link adapter. Using native binding and running the java application on the same computer as the QueueManager (AIX) it was all working fine.
Now, I have translated my app to use JMS instead and tried to run it on my Windows 2000 PC. The message are sent allrigth to the queue, but R/3 Link is now giving me a handfull of errors, complaining about conversion, character sets and things like that.
Here is a sample of errors I get:
02/18/03 17:00:39 SMQ4165: Warning on MQGET from inbound queue. Reason code 2110.
EXPLANATION: The attempt to get a message from the inbound message queue returned a warning. The warning code was 2110. The message will be passed to the use
r exit if one has been specified. If no exit was specified, the message will be passed to the bad message queue. If no bad message queue was specified, the
message will be left on the inbound queue, and the server will terminate.
ACTION: None.
02/18/03 17:00:39 SMQ4192: A data conversion problem occurred on the MQGET. Attempting to process message.
EXPLANATION: A warning was issued because the message needs codepage conversion, but the message is either not in MQSTR format, or a user-defined data- conver
sion exit call failed.
ACTION: Ensure that incoming messages from machines with a different code page, are in MQSTR format or that there is a user exit defined to convert messages i
n other formats.
02/18/03 17:00:40 SMQ4167: IDoc has an invalid structure version. IDoc value="16777216". Expected value="1".
EXPLANATION: The value of the version field in the IDoc header structure contains an invalid value.
ACTION: Ensure that the IDoc message starts with a valid version of the Saplink header structure (MQSAPH).
02/18/03 17:00:40 SMQ4191: A message was put to the bad message queue. Bad message type 1, reason 4108.
EXPLANATION: The message was not in a valid IDoc format. The bad message type is 1 and the bad message reason is 4108.
ACTION: Check the bad message reason code in the bad message header of the message. Attempt to correct the error and send the message again.
I finally set the CCSID to 819 in the connection string, now I suspect that my problem is related to the encoding I use but I can't find what to set it to instead. I write everything in a ByteMessage by the way, just as I was doing it with the native bindings.
Does anyone know how I am supposed to set this up? What encoding type should I set it to? Is the CCSID correct? previously, I was setting the format this way: bytesMessage.format = "MQHSAP ";
But using JMS, there is no such property so I tried to just write it to the ByteMessage, not sure this works either...
Thanks in advance,
Daniel
If it can be of any help, here is a code fragment of what I am doing:
using native binding, which was working fine
//Add the mandatory R3/Link header to our message
bytesMessage.writeBytes("SAPH");
bytesMessage.writeInt(1);
bytesMessage.writeInt(108);
bytesMessage.writeInt(273);
bytesMessage.writeInt(819);
bytesMessage.writeBytes("MQSTR ");
for(int i = 28; i < 108; i++)
bytesMessage.writeByte(32);
bytesMessage.writeBytes(textMessage);
bytesMessage.encoding = MQC.MQENC_INTEGER_NORMAL;
bytesMessage.format = "MQHSAP ";
And using JMS:
//Test code
queue = session.createQueue("queue://" + manager + "/" + name + "?priority=5&persistence=2&targetClient=1&encoding=" +
MQC.MQENC_INTEGER_REVERSED + "&CCSID=819");
//Add the mandatory R3/Link header to our message
bytesMessage.writeBytes("SAPH".getBytes());
bytesMessage.writeInt(1);
bytesMessage.writeInt(108);
bytesMessage.writeInt(273);
bytesMessage.writeInt(819);
bytesMessage.writeBytes("MQSTR ".getBytes());
StringBuffer padding = new StringBuffer(80);
for(int i = 28; i < 108; i++)
padding.append(" ");
bytesMessage.writeBytes(padding.toString().getBytes());
bytesMessage.writeBytes("MQHSAP ".getBytes());
bytesMessage.writeBytes(textMessage.getBytes());
queueSender.send(bytesMessage);

Hi There,
I know you used JMS and Link for R/3.
Now I am doing the same but I am getting the same problem besides I am doing what you mention in the forum.
Can you give me a hand to fix this?
I have configured and MQSeries under win2003 and in the same machine a Link 4 R/3. I have a Java app using a .bindings file to connect to the Q and send a message the same way you did, but i am getting this error:
IDoc has an invalid structure header. IDoc value="RFH ". Expected value="SAPH".
IDoc has an invalid structure version. IDoc value="2". Expected value="1".
IDoc has an invalid system number. IDoc value=<T.
IDoc has an invalid client. IDoc value=�Y♦.
IDoc has an invalid language. IDoc value=.
A message was put to the bad message queue. Bad message type 1, reason 4110.
It seems as if the all the JMS headers are at the begining of the msg and it always throw the same error. it doesn't matter what data I put in the bytesMessage.
I would really appreciate your help.
Here a portion code of my SendMessage operation.
     public String EnviarMsg(String Msg) throws JMSException {
          String resp = null;
          try {
               if (getQueueSend() == null) {
                    // Create un objeto QueueSender como productor del mensaje.
                    setQueueSend(QSess.createSender(MQueue));
                    // Crear y enviar un mensaje a la cola.
               * Aqui viene codigo para enviar msgs a la cola en formato SAP
               txtMsg = QSess.createBytesMessage();
               txtMsg.writeBytes("SAPH".getBytes());
               txtMsg.writeInt(1);
               txtMsg.writeInt(108);
               txtMsg.writeInt(273);
               txtMsg.writeInt(819);
               txtMsg.writeBytes("MQSTR ".getBytes());
               byte b = 32;
               for(int i=28; i<108; i++)
                    txtMsg.writeByte(b);
               txtMsg.writeBytes(Msg.getBytes());
               //txtMsg.encoding = MQC.MQENC_INTEGER_NORMAL;
               txtMsg.setStringProperty("JMS_IBM_Format", "MQHSAP ");
               //txtMsg.setText(Msg);
               // QueueSend.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
               // QueueSend.setTimeToLive(30000);Funciona. Probado con el MQSeries
               // 6.0
               QueueSend.send(txtMsg);
               resp = "OK";

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

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

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

Help me for Configuration on Oracle AS 10g and WebSphere MQ

If there someone can share there experience on configuration on Oracle AS 10g and WebSphere MQ. Is there some quite easy ways or tools to do this?
Welcome any advise!

Hi,
The only thing I know of is the documentation to configure the resource provider and I think there is an example on Technet:
"Declaring an IBM WebSphere MQ Resource Provider Reference"
[http://download.oracle.com/docs/cd/B32110_01/web.1013/b28958/jms.htm#i1086751|http://download.oracle.com/docs/cd/B32110_01/web.1013/b28958/jms.htm#i1086751]
and
[http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/index.html|http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/index.html]
I think the important thing is to note step 3 of the documentation,
Add to J2EE_HOME/applib any JAR files required by a Websphere MQ JMS client
as described in the IBM documentation.
I assume this comes from an MQ library that should be installed in OC4J.
If you use applib you must restart OC4J before it will be seen also.
I hope this can guide you in the right path.
Sincerely,
Steff

SAP XI and WebSphere Application Server v6

Hello,
has anyone made integration projects between SAP XI and WebSphere App Server v6 using JMS?
Thanks for any feedback
Jens

WebSphere is not a Sun Microsystems product.
It does not make sense to ask questions here, about a third party product,
particularly when that third party is such a large organization.
Can you describe what guidance you have received from IBM ?
They would be the best source of all nuances on their own product.
They created it.
They've undoubedly installed it once or twice.
They are expected to be prepared to answer questions about it.

Connection Weblogic and Websphere MQ

Can anybody help me how to connect Weblogic and Websphere MQ?

If you are using the foreign JMS server then create the binding file for MQ. The binding file would contain host and port and other required details.
Weblogic could understand the configuration details in that.

Crystal Report 9.0 and Websphere

hi can any body give me some steps regarding
integration of crystal report and websphere
i have already search this forum and i got lot many topics
regarding this but all were using cyrstal report version 8 and 8.5
which requires mandatory using IIS server which i dont wont to use
i want a pure websphere and 9.0 version communication
i had read the docs whihc states that 9.0 supports but i dont know how?
can any bosy help regarding this

here's the report code
<%@ page contentType="text/html; charset=utf-8" %>
<%@ page session="true"%>
<%@ page import="javax.servlet.jsp.*"%>
<%@ page import="java.util.Locale"%>
<%@ page import="java.net.*" %>
<%@ page import="java.text.DateFormat" %>
<%@ page import="javax.servlet.jsp.JspWriter"%>
<%@ page import="javax.servlet.http.HttpServletRequest" %>
<%@ page import="javax.servlet.http.HttpSession" %>
<%@ page import="com.crystaldecisions.sdk.occa.report.data.*" %>
<%@ page import="com.crystaldecisions.sdk.occa.report.application.*" %>
<%@ page import="com.crystaldecisions.report.web.viewer.*" %>
<%@ page import="com.crystaldecisions.sdk.occa.report.exportoptions.*" %>
<%@ page import="com.crystaldecisions.sdk.occa.report.definition.*" %>

<%
System.out.println("$$$$$$$$$$$$$$$$$$$$$$$$");
String reportName=(String)request.getAttribute("ReportName");
String requestNumber=(String)request.getAttribute("RequestNumber");
String requestNumber="RPT_112";
System.out.println("********************");
ParameterField newParameter = new ParameterField();
ParameterField newField = null;
System.out.println("@@@@@@@@@@@@@@@@@@@@@@@@@");
ParameterFieldDiscreteValue newValue = null;
System.out.println("^^^^^^^^^^^^^^^^^^^^^^^^^^");
try{
ReportClientDocument rptClientDoc = new ReportClientDocument();
//System.out.println("11111111111111111111111111");
/* Change DCWKS0241AB to the name of Machine where RAS is installed for ex like DCWKS0237 */
rptClientDoc.setReportAppServer("DCWKS0241AB");
System.out.println("22222222222222222222222222");
/* Change this E:\\Crystal\\Reports\\ to the path where your reports are kept */
String reportPath="E:\\RAS\\Reports\\Percentages.rpt";
rptClientDoc.open (reportPath, 0);
rptClientDoc.getDatabaseController().logon("bbva","bbva");
System.out.println("After Creating the Client Document on the Report");
/* folowing Code remove any default value to the report and append the request number in the input parameter*/
newField = (ParameterField)rptClientDoc.getDataDefinition().getParameterFields().getField(0);
newField.copyTo(newParameter,true);
newParameter.getCurrentValues().removeAllElements();
newValue=new ParameterFieldDiscreteValue();
newValue.setValue(requestNumber);
newParameter.getCurrentValues().add(newValue);
/* Just for Testing Purpose
Values v=newParameter.getCurrentValues();
IValue iv=v.getValue(0);
System.out.println("---> "+iv.computeText());
rptClientDoc.getDataDefController().getParameterFieldController().modify(newField, newParameter);
/* Specifying the Format */
PDFExportFormatOptions PDFExpOpts = new PDFExportFormatOptions();
//Create the ExportOptions object, set the PDF export options, and set the format type to PDF.
ExportOptions exOpts = new ExportOptions();
exOpts.setFormatOptions(PDFExpOpts);
exOpts.setExportFormatType(ReportExportFormat.from_int(ReportExportFormat._PDF));
System.out.println("After Setting the format");
System.out.println("Before getting source");
//Create the ReportExportControl object and set the report source to the report that will be exported to PDF.
ReportExportControl expViewer = new ReportExportControl();
System.out.println("Before getting source");
expViewer.setReportSource (rptClientDoc.getReportSource());
System.out.println("3");
//Set the export options to the ReportExportControl object.
expViewer.setExportOptions(exOpts);
System.out.println("After Setting the Export Options to the ReportExportControl object.");
//Set the exported report to display in the browser.
//The setExportAsAttachment method is set to false by default. If it is set to true the user will be presented with the File Download dialog box to save the exported report to disk.
expViewer.setExportAsAttachment(false);
//Export and view the report.
expViewer.processHttpRequest(request, response, (getServletConfig()).getServletContext(),null);
System.out.println("After Exporting and viewing the report back in the Browser.");
//Destroy the control.
expViewer.dispose();
catch (Exception e)
out.write("Error: Open" + e.toString() + "\n");
%>

EJB communication between weblogic and websphere

Hello:
I have weblogic 7.1 instance running in machine A and websphere running in machine B. I want to make a call to the ejb deployed from weblogic to websphere. Any experience in this would be very helpful. Or pl. post the procedure.
Thx in advance.

I don't think that there is any magic here, although I've never tried it.
All you need is the compiled EJBHome and EJBObject interfaces in the
classpath of the calling EJB, get an InitialContext in the JNDI namespace of
the target EJB container using the name of the JNDI InitialContext Factory,
do a lookup on the bean making sure to do a PortableRemoteObject.narrow when
you are casting the Home stub with the vendor specific version of
PortableRemoteObject(and that may be the real trick), call the appropriate
create method, and you are rolling.
I guess the question becomes how to make sure that when you are calling
PortableRemoteObject.narrow on the Home stub, that you get the vendor
specific version for the EJB container and JNDI namespace from which you are
doing the lookup.
I guess the answer is, I'm guessing. Have you tried it?
bill
"nebs om" <[email protected]> wrote in message
news:30035468.1103738722864.JavaMail.root@jserv5...
Hello:
I have weblogic 7.1 instance running in machine A and websphere runningin machine B. I want to make a call to the ejb deployed from weblogic to
websphere. Any experience in this would be very helpful. Or pl. post the
procedure.
>
Thx in advance.

JMS based message service and Service account in OSB

Hi forum,
I have query regarding JMS base messaging service and Service account.
My OSB service:
I have created one OSB service which of type JMS
configuration :
General :Messaging
Messaging: Request type :XML response type :none
Transport:JMS
JMS Transport: Destination Type queue., JMS Service account :.........(browse)
My requirement is to provide security to JMS proxy.
I have seen one option available in JMS transport is JMS Service Account.
I dont have a idea about using service accounts in JMS.
can any one pls give idea about JMS service account in JmS.How to provide security to jms proxy...
If u have any documents pls share me
Thanks & regards,
Krishna.

In your weblogic console go to your JMS Modules > ***JMSModule >****Queue >Roles >Policies. Add a user to the queue.This user should be there in the security realm of the weblogic console.
Create a service account with the same user name password and use it in your OSB to read or write to the queue.

Nd help configuring JMS Bridges between COM and SOM

We skip the JMS Bridge between SOM and COM because we deploy the O2A cartridge using the:
- When Central Order Management and Service Order Management Exist in the Same
OSM Instance in a Non-Cluster Environment.
- Customer and Service Order Management in the Same OSM Instance
"Deploy the following cartridges through Design Studio for the simple fulfillment
topology"
Now what happening is: the flow of the order taking time before it was completed or need manually submit the task using oms-automation user.
But even with the above work around we cannot see the billing data in BRM.
UpdateSalesOrderSiebelCommsProvABCSImpl (v. 1.0) this is the last BPEL process we see in BPEL.
FulfillBillingFunction.BRM-ALL.BundleGranularity.FulfillBillingSignificantUpdates is the last Activity we can see in osmwebui if not manually update the task.
Then ProvisionOrderSIResponseTask is the current task in osm task web client where order state is In-Progress.
With that it seems the SOM is not processing.
Do you have any idea why we can't complete the order and see the billing data in BRM?
Is'it the COM and SOM not properly configured, or have some issue with other application(RODOD)?
Thanks,
Ace

Hi All,
This issue already resolve by configuring the routing in AIA.

Configuring JMS Bridges between COM and SOM

Hi,
We started working on OSM 7.0.2 and I have a question about the configuration of JMS Bridges between COM and SOM.
When COM and SOM Cartridges are installed in the same OSM instance on non-cluster env., it is mandatory to configure JMS Bridges between COM and SOM?
If it is case, could you please detail the procedure to follow?
In the document called "Application Integration Architecture Order-to-Activate Cartridge Guide Release 7.0.2 E18005-01" it is not obvious to understand. If you have a look in the table 2-1 page 2-15, I don't see all the mandatory field values to create a new destination bridges (for instance, what is the value of destination JNDI name?). Does anyone configure this part in the setting up OSM to the Order-to-Activate Solution?
Best regards.

The COM-SOM bridge is only required when COM and SOM are deployed on separate osm server instances and AIA Emulators are deployed (on both) for development/demo/quick testing purposes.
In QA/SIT/PRODUCTION environments, OSM should be integrated via AIA, this means that all participant applications ( CRM , OSM-COM, OMS-SOM, BRM ) should be using queue bridges (or SAF in 7.0.3)

[svn] 2773: Update excludes list for JBoss and WebSphere.

Revision: 2773
Author: [email protected]
Date: 2008-08-07 04:35:10 -0700 (Thu, 07 Aug 2008)
Log Message:
Update excludes list for JBoss and WebSphere.
Modified Paths:
blazeds/trunk/qa/features/excludes.properties

JGroups is an open source project that allows processes to send messages to one another. LiveCycle data services uses it for its messaging implementation (basically it configures the server to multicast messages to all the listening clients...even in a clustered environment across different LAN/WAN).
In most cases the default configuration will work fine, the problem is that if you are running a firewall on the server (or your local machine...i.e. windows firewall) the ports that JGroups uses for its communications can be blocked. In a local environment its easy enough to disable windows firewall and bounce your server to get things working.
In a production environment you need to open the ports that JGroups is using. These settings are in the Global Administration settings (as mentioned by WorkspaceUser above). If you export it and look at the JChannelConnectionProperties you'll see the ports its using and you can set your firewall to allow communication to those ports.
Bryan

Weblogic and Websphere intergration

Hi,
I would like to make a call from EJB bean deploeyd on WLS8.1 to another
bean deployed on Websphere 6.0 but I have no idea how to do that.
When I do sth like that in EJB in WLS:
InitialContext tx = new InitialContext();
Object obj =
(Object)tx.lookup("corbaname:iiop:localhost:2809#comarch/test/ejb/BasicCalculator");
I get the following exception:
javax.naming.NameNotFoundException: Exception in lookup.:
`comarch/test/ejb/Basi
cCalculator' could not be found. Root exception is
org.omg.CosNaming.Nami
ngContextPackage.NotFound:
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at
org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHe
lper.java:72)
at
org.omg.CosNaming._NamingContextStub.resolve(_NamingContextStub.java:
251)
at
weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:187)
at
weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:174)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at examples.HelloBean.hello(HelloBean.java:71)
BasicCalculator bean is deployed on websphere and websphere runs on
localhost.
What should i do to get it running?
Any help appreciated.

looser0 <[email protected]> writes:
BasicCalculator bean is deployed on websphere and websphere runs on
localhost.
What should i do to get it running?
Any help appreciated.This definitely works but there have been several patches to both
products to support things well. First of all check what name you
should actually use for websphere - I have a feeling that it has some
bizarre prefix on all of its names. Next make sure you are running
with WLS 8.1sp4. I don't know what version of WebSphere 6.0 you need -
I know there were fixes in WAS 5.1.3.
andy
--

Recent Kodo versions and WebSphere 4.0

Hi,
we may have to use WebSphere 4.0 with Kodo until the IT infrastructure
department supports the latest version WebSphere 5.0.
Is anyone still developing with Kodo and WebSphere 4.0? Can I use Kodo
2.5 / 3.0 with the 'old' version of WebSphere?
Thanks a lot!
Yours,
Carsten

Carsten-
Our only feedback is that Kodo has not been tested with Websphere
versions before 5.0.
Note that you can always just Kodo directly: the only hiccup might be in
the automatic global transaction synchronization. As long as Websphere
4.0 provides a JTA-compliant TransactionManager, though, you might be
able to solve any problems you see by writing a custom ManagedRuntime
implementation.
I'm sure the rest of the community will be interested in hearing the
results of your tests.
In article <bn38qa$d1i$[email protected]>, Carsten Jahn wrote:
Hi,
we may have to use WebSphere 4.0 with Kodo until the IT infrastructure
department supports the latest version WebSphere 5.0.
Is anyone still developing with Kodo and WebSphere 4.0? Can I use Kodo
2.5 / 3.0 with the 'old' version of WebSphere?
Thanks a lot!
Yours,
Carsten
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Weblogic and websphere colocated?

Has anyone ever had any experience running weblogic and websphere on the same machine? If so, what were your issues?
Thanks in advance.

Web sphere has a wide robust features which weblogic lacks some. Like the load balancing and admin console, clustering .
In Weblogic In many cases, code for applications deployed on WebLogic Server is arbitrarily structured and depends on the build process to make sense of it all. The implication of this is that existing code organization will very likely have to be changed as part of the migration effort. This may be very difficult (or even impossible) to accomplish while maintaining links to your code's history. Some organizations choose simply to archive their history and start fresh.
In WebSphere, Packaged with each module is an XML deployment descriptor that describes the organization of the components in the module and how they are configured at run time. hence applications can be migrated easily.

JMS, MQSeries 5.2 and Websphere 4.0.2

Similar Messages

Maybe you are looking for