File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Websphere and the fly likes WebSphere 6.0.2.9 Delployment Problem Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WebSphere 6.0.2.9 Delployment Problem" Watch "WebSphere 6.0.2.9 Delployment Problem" New topic
Author

WebSphere 6.0.2.9 Delployment Problem

Santosh Kumar
Greenhorn

Joined: Jan 03, 2002
Posts: 28
Hi,
My WebSphere Application Server version details are as follows.
IBM WebSphere Application Server - ND, 6.0.2.9
Build Number: cf90614.22
Build Date: 4/7/06

The app server is running on AIX box.

I have one EAR file which contains two EJB jars (CMT.jar and BMT.jar). There are JMS as well. I am using JMS 1.1 version. One JMS resource type is javax.jms.TopicConnectionFactory and the other one is javax.jms.QueueConnectionFactory.

Now while deployement of EAR at step 6, Warning message is displayed...

---------------------------------------------------------------------------
ADMA8019E: The resources that are assigned to the application are beyond the deployment target scope. Resources are within the deployment target scope if they are defined at the cell, node, server, or application level when the deployment target is a server, or at the cell, cluster, or application level when the deployment target is a cluster. Assign resources that are within the deployment target scope of the application or confirm that these resources assignments are correct as specified.

Step 6 - Map resource references to resources resulted in the following resouce warnings. If application validation is set to fail, you will not be able to continue past.

Module:
Name: CMT
URI: CMT.jar, META-INF/ejb-jar.xml
Target: WebSphere:cell=aaa,node=bbb,server=ccc

Resource Reference:
Name: abcXAtcf_userprofile
Type: javax.jms.TopicConnectionFactory

Resource Assignment:
Name: USERPROFILE_TOPIC_CONNECTION_FACTORY
Scope: WebSphere:cell=abc,node=bbb,server=ccc

Type: JMSProvider
JNDI: jms/USERPROFILE_TOPIC_CONNECTION_FACTORY

Module:
Name: BMT
URI: BMT.jar,META-INF/ejb-jar.xml
Target: WebSphere:cell=aaa,node=bbb,server=ccc

Resource Reference:
Name: abcXAtcf_userprofile
Type: javax.jms.TopicConnectionFactory

Resource Assignment:
Name: FOUNDATION_SERVER_TOPIC_CONNECTION_FACTORY
Scope: WebSphere:cell=abc,node=bbb,server=ccc

Type: JMSProvider
JNDI: jms/FOUNDATION_SERVER_TOPIC_CONNECTION_FACTORY
-----------------------------------------------------------------------

In the summary page of the deployment it shows these warnings...

-----------------------------------------------------------------
ADMA0139W: Resource Assignment of name chordiantXAtcf_userprofile and type javax.jms.TopicConnectionFactory, with JNDI name jms/USERPROFILE_TOPIC_CONNECTION_FACTORY is found within scope of module CMT with URI CMT.jar, META-INF/ejb.jar.xml deployed to target WebSphere:cell=aaa,node=bbb,server=ccc, but of wrong resource type JMS. The expected resource type is JMSProvider.

ADMA0139W: Resource Assignment of name chordiantXAtcf_userprofile and type javax.jms.TopicConnectionFactory, with JNDI name jms/FOUNDATION_SERVER_TOPIC_CONNECTION_FACTORY is found within scope of module BMT with URI BMT.jar, META-INF/ejb.jar.xml deployed to target WebSphere:cell=aaa,node=bbb,server=ccc, but of wrong resource type JMS. The expected resource type is JMSProvider.
---------------------------------------------------------------------

I tried to find the solution but no success. Though in book WebSphere for z-OS V6 Connectivity Handbook.pdf page number 418 says something about resource type in this regard. But I dont think this is the solution. Can anybody please let me know the solution for this?


Santoh Kumar<br /> India<br />SCJP 1.4 <br />SCWCD 1.4
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WebSphere 6.0.2.9 Delployment Problem