Annies' Weblog

OpenESB in WebSphere

Monday Aug 13, 2007

Yes! Open ESB runs in WebSphere.

A servlet wrapped implementation of Open ESB has been developed as a proof of concept.

Instructions to run Open ESB in WebSphere 6.0

1)Download the war and deploy it following the default settings.

2)Now say, No Thanks!, to some of the attributes added to MBean names by WebSphere, by creating a custom property.

(i)Navigate to Servers > Application Servers > Server1(Server Infrastructure) >
Administration > Administration Services > Custom Properties.

(ii)Click New and supply the following values for name and value fields respectively
com.ibm.websphere.mbeans.disableRouting
<on>com.sun.jbi:*</on><on>com.sun.jbi.esb:*</on>

3)Start the application. Click on Enterprise Applications, select openesb-websphere-1_1_war and start it.

Instructions to administer Open ESB and run the demo

1)Download the client jar and unjar in <CLIENT_HOME>.

2)Configure the environment as follows and make sure ant is in your PATH.

set JAVA_HOME=<WAS_HOME>/AppServer/java

set CLASSPATH=<WAS_HOME>/AppServer/runtimes/com.ibm.ws.admin.client_6.1.0.
jar;<CLIENT_HOME>/jbi-admin-common.jar;<CLIENT_HOME>/jbi-ant-tasks.jar

3)Run the demo application.

Note: For demo purposes, I am using the following experimental components: SunFileBinding and SunTransformationEngine. These two components are attached to this blog. You can find sources for these two experimental components in File Binding Source and Transformation Engine Source.
Fully functional Open ESB components can be downloaded here.

(i)Download sun-wsdl-library, SunFileBinding, SunTransformationEngine,
FileTransformApp, sample_input.xml.

(ii)ant -f <CLIENT_HOME>/jbi_admin.xml -Djbi.port=2809
-Djbi.host=<hostname> -Djbi.username=<username>
-Djbi.password=<password> -Djbi.install.file=wsdlsl.jar
install-shared-library

(iii)ant -f <CLIENT_HOME>/jbi_admin.xml -Djbi.port=2809
-Djbi.host=<hostname> -Djbi.username=<username>
-Djbi.password=<password> -Djbi.install.file=file-binding.jar
install-component

(iv)ant -f <CLIENT_HOME>/jbi_admin.xml -Djbi.port=2809
-Djbi.host=<hostname> -Djbi.username=<username>
-Djbi.password=<password> -Djbi.install.file=transformation-engine.jar
install-component

(v)ant -f <CLIENT_HOME>/jbi_admin.xml -Djbi.port=2809
-Djbi.host=<hostname> -Djbi.username=<username>
-Djbi.password=<password> -Djbi.deploy.file=FileTransformApp.zip
deploy-service-assembly

(vi)ant -f <CLIENT_HOME>/jbi_admin.xml -Djbi.port=2809
-Djbi.host=<hostname> -Djbi.username=<username>
-Djbi.password=<password> -Djbi.service.assembly.name=FileTransformApp
start-service-assembly

(vii)Copy sample_input.xml to c:\tmp\test\input\transforminout and
see it magically transform into a html file and go to c:\tmp\test\output.

Like this post? del.icio.us | furl | slashdot | technorati | digg
Posted at 04:21PM Aug 13, 2007 by annies in Sun
Tags:
Comments:

Thanks Annie. BTW, what openesb functionality currently isn't available when deployed to websphere? I assume JavaEE SE. Any other openesb functionality?

Posted by Jason Baragry on August 15, 2007 at 12:03 AM PDT #

Annie, this is very useful for a current opportunity. Could you email me some more information to my Sun address about your proof of concept? Thanks.

Posted by Louis Polycarpou on August 15, 2007 at 05:54 AM PDT #

[Trackback] Nov 3rd was the Community Day events as part of Sun Tech Days, Beijing. GlassFish, Open Solaris and NetBeans Day were conducted as part of the event. This blog provides a report on GlassFish Day. The GlassFish Day started with...

Posted by Arun Gupta's Blog on November 06, 2007 at 07:26 AM PST #

[Trackback]

Posted by csdnexpert on December 16, 2007 at 06:17 PM PST #

Hi Annie
Wonderful that you managed to integrate OpenESB with WebSphere! That's exactly what we would like to use in our project. Installation of the component on WebSphere 6.1 worked like a charm. However, the ant installation script fails for the JBI components with the following error message: javax.management.InstanceNotFoundException: com.sun.jbi:ServiceName=ESBInstallationService,ComponentType=System
Do you have an idea on what's going wrong. It most probably has to do with the new WebSphere 6.1 version, however I cannot really figure out what to do to solve it. Can you help?
Thanks in advance
Daniel Frey

Posted by Daniel Frey on December 21, 2007 at 06:04 AM PST #

Hi Daniel,

This may not be related to WebSphere version. This MBean was introduced recently as part of an effort to modularize the common client interface. I will take a look to see what could be going wrong. In the meantime could you please confirm if you set up the disableRouting property for all com.sun.jbi MBeans as shown in step 2 item ii.

Thanks
Annies

Posted by Annies on December 21, 2007 at 11:47 AM PST #

Hi Annie,

Happy New Year! And thanks for your quick reply on my first post. As I am working on this project only once a week, my period of reply-time will be slightly larger ;-)

We updated to WebSphere 6.1.0.13 today. The "disableRouting" property was lost during the update, so we entered it again. To be clear, there is one property with name "com.ibm.websphere.mbeans.disableRouting" and value "<on>com.sun.jbi:*</on><on>com.sun.jbi.esb:*</on>".

Since the update, ant is not able to connect to WebSphere - with the same command we issued before the update and delivered the error described first. The ant command we are issuing is "ant -f jbi_admin.xml -Djbi.port=2809 -Djbi.host=ki06 -Djbi.username=<user> -Djbi.password=<pass> -Djbi.install.file=file-binding.jar install-component" where the <user> and <pass> are the same as we used and still use to connect to the IBM Integrated Solutions Console. The machine name is resolved correctly (can be entered in any browser) and the port is open (netstat -a shows ki06:2809 with LISTENING). We restarted the server after installation and after configuring the property.

I think I cannot say anything about the problem we met first because we are not able to connect properly, whereas before the update I suppose we were able to connect. The error is the following:

jbi_admin.xml:372: Install component failed. [
ERROR:(UICMN2094)Unable to connect to [host = ki06, port = 2809] for user admin.
Check the connection settings and ensure that the server is running.
]

Maybe you have an idea on what is going wrong here.

Thank you in advance!

Daniel Frey

Posted by Daniel Frey on January 11, 2008 at 02:47 AM PST #

Hi Annie,

Short update: I have just seen that you updated the "client.jar" and "war" which I have installed and am using for the ant task. The error remains the same, except the line has changed:

jbi_admin.xml:382: Install component failed. [
ERROR:(UICMN2094)Unable to connect to [host = ki06, port = 2809] for user admin.
Check the connection settings and ensure that the server is running.
]

Daniel Frey

Posted by Daniel Frey on January 11, 2008 at 03:11 AM PST #

Hi Daniel,

Sorry. I did not have time to test with the latest build, as I was in the middle of some other deliverables. I will get back to you by Wednesday.

Thanks
Annies

Posted by Annies on January 11, 2008 at 09:07 AM PST #

Hi, Annie, I am a student working in a free internship for IBM. I am a novice at WAS administration, but I have been assigned the task of finding a decent BPEL execution engine that can run on WAS 6.1. I noticed that I have the same error as Daniel when I try running ant to install the sun components. I have all of the environment variables set up correctly. WAS spits out some stack trace information when it starts up, here is the abbreviated version:

[2/7/08 13:15:22:691 MST] 0000001a SystemErr R javax.management.InstanceAlreadyExistsException: com.sun.jbi:cell=MEYERS-ADNode01Cell,ControlType=Statistics,JbiName=server,node=MEYERS-ADNode01,ServiceName=DeploymentService,process=server1,ComponentType=System

[2/7/08 13:15:23:099 MST] 0000001a framework E JBIFW0003: Unable to initialize Management Service due to an exception: javax.jbi.JBIException(javax.management.InstanceNotFoundException: com.sun.jbi:JbiName=server,ServiceName=AdminService,ControlType=Lifecycle,ComponentType=System). Stack trace follows.
javax.jbi.JBIException: javax.management.InstanceNotFoundException: com.sun.jbi:JbiName=server,ServiceName=AdminService,ControlType=Lifecycle,ComponentType=System
at com.sun.jbi.management.system.ManagementService.initService(ManagementService.java:209)

Posted by Wolfgang Meyers on February 07, 2008 at 12:16 PM PST #

Hi

Could you please send me the entire server log so I could find out what is going wrong. I have not tried this out in 6.1.1 yet. The bpel engine had one minor bug that prevented it from working in WebSphere. I believe this has been fixed. I am planning to update this blog with sample SA that uses bpel engine and http binding. I will get to that in a week or two.

Thanks
Annies

Posted by 76.199.137.117 on February 08, 2008 at 07:59 AM PST #

Hi Annie
I am trying to run openesb on web sphere 6.1 version , even I am facing the same problem when I try to install the components \jbi_admin.xml:241: Install shared library failed. [
ERROR:(UICMN2094)Unable to connect to [host = HLBLSWSLEP0057, port = 2809] for user admin.
Check the connection settings and ensure that the server is running.
]
Kindly help me in resolving this ……. Thanks in advance ……
natesh

Posted by natesh on February 27, 2008 at 10:53 PM PST #

Hi Natesh,

This seems to be a issue specific to 6.1.
Could you please send me the entire server log
to annies_aatyahoodotcom
Would you be able to try this out in 6.0?

Thanks
Annies

Posted by Annies on February 28, 2008 at 02:21 PM PST #

I am running websphere 6.1 and set the mbean disable routing.I am getting the following error . could somebody help in resolving this.

C:\Documents and Settings\Administrator>ant -f C:/openesb/websphere/jbi_admin.xm
l -Djbi.port=2809 -Djbi.host=localhost:9080 -Djbi.username=admin -Djbi.p
assword=adminadmin -Djbi.install.file=wsdlsl.jar install-shared-library
Buildfile: C:\openesb\websphere\jbi_admin.xml

-pre-jbi-admin-setup:

-jbi-admin-setup:
[taskdef] Could not load definitions from resource com/sun/jbi/ui/ant/antlib.x
ml. It could not be found.

BUILD FAILED
C:\openesb\websphere\jbi_admin.xml:52: taskdef class com.sun.jbi.ui.ant.util.I18
NEchoTask cannot be found

Total time: 0 seconds

Posted by manishi on March 31, 2008 at 10:15 AM PDT #

Hi Annie: After struggling for couple of hours i was able to correct the prob. It was a classpth problem.I was able to successfully deploy the war files and the was able to run the ant commands for the sample. The message said the BUILD i ssuccessfull. But when i put the input.xml file in the input/transforminout folder i dont see any file in the output folder.

Could you please help me what might be the problem.

Posted by manishi on April 02, 2008 at 10:47 AM PDT #

Hi Manishi,
Do you see errors in the server log?
Thanks
Annies

Posted by 192.18.101.5 on April 02, 2008 at 10:57 AM PDT #

Hi Annie: I restarted the websphere appserver. I ran the above mentioned commands. Now i get the output, but the out files arr err output file.
The only text it contains is:
================================
Invalid pattern null for {http://sun.com/transform-file.wsdl}transformServicefiletxEP.com.sun.jbi.binding.file.FileCommand.execute(FileCommand.java:295)
com.sun.jbi.binding.file.framework.WorkThread.processCommand(WorkThread.java:231)
com.sun.jbi.binding.file.framework.WorkThread.run(WorkThread.java:150)
java.lang.Thread.run(Thread.java:797)
================================================

I don't know what is the problem. could you please let me know what is the problem.

Regards
Ravi.n

Posted by Manishi on April 02, 2008 at 11:18 AM PDT #

Hi Annie:

I looked up the app server logs. Below are the messages.Please let me know what is wrong
==========================================================================
[4/2/08 14:09:58:406 EDT] 0000005e management I Deploying service assembly FileTransformApp to target server.
[4/2/08 14:09:59:031 EDT] 0000005e DeploymentSer I JBIMA0402: Service Assembly file:/C:/openesb/websphere/FileTransformApp.zip has been deployed.
[4/2/08 14:11:25:031 EDT] 0000005f management I Starting service assembly FileTransformApp on target server.
[4/2/08 14:11:25:734 EDT] 000000a0 SunTransforma I Found TE Endpoint.
[4/2/08 14:11:25:812 EDT] 000000a0 SunTransforma I Checking WSDL file: true
[4/2/08 14:11:25:859 EDT] 000000a0 SystemOut O #####Retived delimiter is==null*
[4/2/08 14:11:25:875 EDT] 000000a0 SystemOut O ######Typexml
[4/2/08 14:11:25:937 EDT] 000000a4 SunTransforma I Service activated is ={http://www.sun.com/ns/jbi/engines/transformation/deploy/service-config}transformService3:JbiEP
[4/2/08 14:11:25:984 EDT] 000000a5 SunFileBindin I Starting deployment FileTransformApp-FileBinding.
[4/2/08 14:11:26:000 EDT] 000000a5 SunFileBindin I Processed folder C:\tmp\test\processed does not exist or does not have write permission.
[4/2/08 14:11:26:062 EDT] 000000a5 SunFileBindin I Created folder C:\tmp\test\processed.
[4/2/08 14:11:26:062 EDT] 000000a5 SunFileBindin I Started deployment FileTransformApp-FileBinding.
[4/2/08 14:11:26:078 EDT] 000000a6 SunFileBindin I Running thread Thread-55
[4/2/08 14:11:26:078 EDT] 000000a7 SunFileBindin I Running thread Thread-56
[4/2/08 14:11:26:296 EDT] 000000a6 SunFileBindin E Invalid pattern null for {http://sun.com/transform-file.wsdl}transformServicefiletxEP.
[4/2/08 14:11:26:312 EDT] 000000a6 SunFileBindin E Could not send message.
[4/2/08 14:11:26:328 EDT] 000000a7 SunFileBindin E Invalid pattern null for {http://sun.com/transform-file.wsdl}transformServicefiletxEP.
[4/2/08 14:11:26:328 EDT] 000000a7 SunFileBindin E Could not send message.
[4/2/08 14:13:13:906 EDT] 000000a6 SunFileBindin E Invalid pattern null for {http://sun.com/transform-file.wsdl}transformServicefiletxEP.
[4/2/08 14:13:13:921 EDT] 000000a6 SunFileBindin E Could not send message.
[4/2/08 14:13:29:609 EDT] 000000a7 SunFileBindin E Invalid pattern null for {http://sun.com/transform-file.wsdl}transformServicefiletxEP.
[4/2/08 14:13:29:640 EDT] 000000a7 SunFileBindin E Could not send message.
[4/2/08 14:18:41:453 EDT] 000000a6 SunFileBindin E Invalid pattern null for {http://sun.com/transform-file.wsdl}transformServicefiletxEP.
[4/2/08 14:18:41:484 EDT] 000000a6 SunFileBindin E Could not send message.
[4/2/08 14:28:31:312 EDT] 0000003f CacheServiceI I DYNA1001I: WebSphere Dynamic Cache instance named ws/WSSecureMapNotShared initialized successfully.
[4/2/08
=========================================================================

Posted by manishi on April 02, 2008 at 11:39 AM PDT #

Annie:

Below are the messages from error log.Hope this helps.the problem seems to be in "filecommand" java file.

=========================================================================
[4/2/08 14:11:26:406 EDT] 000000a7 SystemErr R java.lang.Exception: Invalid pattern null for {http://sun.com/transform-file.wsdl}transformServicefiletxEP.
[4/2/08 14:11:26:406 EDT] 000000a7 SystemErr R at com.sun.jbi.binding.file.FileCommand.execute(FileCommand.java:295)
[4/2/08 14:11:26:406 EDT] 000000a7 SystemErr R at com.sun.jbi.binding.file.framework.WorkThread.processCommand(WorkThread.java:231)
[4/2/08 14:11:26:406 EDT] 000000a7 SystemErr R at com.sun.jbi.binding.file.framework.WorkThread.run(WorkThread.java:150)
[4/2/08 14:11:26:406 EDT] 000000a7 SystemErr R at java.lang.Thread.run(Thread.java:797)
=====================================================================

Posted by manishi on April 02, 2008 at 11:51 AM PDT #

Hi Annie: Did u had a chance to look into the errors i posted earlier. I desperately need those answers. I also would like to know any production implementations of this solution. Any examples of limitations.

we have to decide very soon whether this will. If you get a chance please try to look into this.

Also i would like to ask Daniel Frey who has posted earlier in this blog if they have implemented any such solution or not.if yes then what are the challenges they faced and what was his experience.

Thanks in advance
Regards
Ravi.n

Posted by ravi on April 03, 2008 at 08:06 AM PDT #

Hi Annie, hi Ravi and hi Manishi

We did try to circumvent the deployment problems for the JBI components described in my first comments to this blog. However, we did no manage to deploy them. So as a quick solution and given the timeline to meet we decided to handle all workflow relevant logic in a static way. However, we are still interested in this product, as sooner or later we will need to have an orchestration framework and tooling doing exactly what OpenESB does.

Manishi managed to deploy the components and is already trying to run a simple use case. So his experiences to deploy the components would be valuable for all of us. Question to

--> Manishi: Could you share the crucial changes you did to your classpath?

I am not sure whether Annie did post new versions of the WAR and client JAR, as I cannot find any version information. Up to now I did compare the contents of the libraries to see whether something changed.

--> Annie: Could you post a short note upon updates of any of the involved artifacts?

I think we should be able to make OpenESB up and running on WebSphere 6.1!

Cheers
Daniel

Posted by Daniel Frey on April 03, 2008 at 08:41 AM PDT #

Daniel:

Thanks for the feedback. I installed the web application as described by annie above. I just followed the steps,but i had challenges in each stpe.
My main challenge is was get the Ant command in the classpath.Once i got that worked out.
I started the commands as mentioned above.
The commands i used are are as follows:

set JAVA_HOME=C:/Program Files/IBM/WebSphere/AppServer/java

set CLASSPATH=C:/Program Files/IBM/WebSphere/AppServer/runtimes/com.ibm.ws.admin.client_6.1.0.jar;C:/openesb/websphere/jbi-admin-common.jar;C:/openesb/websphere/jbi-ant-tasks.jar

ant -f C:/openesb/websphere/jbi_admin.xml -Djbi.port=2809 -Djbi.host=localhost -Djbi.username=admin -Djbi.password=adminadmin -Djbi.install.file=wsdlsl.jar install-shared-library

ant -f C:/openesb/websphere/jbi_admin.xml -Djbi.port=2809 -Djbi.host=localhost -Djbi.username=admin -Djbi.password=adminadmin -Djbi.install.file=file-binding.jar install-component

ant -f C:/openesb/websphere/jbi_admin.xml -Djbi.port=2809 -Djbi.host=localhost -Djbi.username=admin -Djbi.password=adminadmin -Djbi.install.file=transformation-engine.jar install-component

ant -f C:/openesb/websphere/jbi_admin.xml -Djbi.port=2809 -Djbi.host=localhost -Djbi.username=admin -Djbi.password=adminadmin -Djbi.deploy.file=FileTransformApp.zip deploy-service-assembly

ant -f C:/openesb/websphere/jbi_admin.xml -Djbi.port=2809 -Djbi.host=localhost -Djbi.username=admin -Djbi.password=adminadmin -Djbi.service.assembly.name=FileTransformApp start-service-assembly

Then i had to unjar some of the jar files inside client.jar which were not in the classpath.The root folder should be where the jbi_admin.xml file is. all the files mentioned by Annie has to be in the same folder as the jbi_admin.xml.

Hope this helps.
also i would like to know whether you were planning to have it deployed in a cluster environment. were u planning ti do it as a webapp on a single node and scale it horizontally or vertically based on ur needs or you were planning to install it with other apps. I think if you are going use the full potential of Openesb then you have to deploy it as a single app on a single node.Let me know your thoughts on this.

Annie: Please send any documentation regarding this deployment.also let me know(if you know) what is the process of deploying other BC's or SE's in the Openesb on wehsphere. I mean the steps to do it.That would be really helpful.

Posted by manishi on April 03, 2008 at 09:21 AM PDT #

Hi Manishi

Thanks for your contribution. I will try that out as soon as the scope of our project spotlights the incorporation of the OpenESB again. But for the next two months that will not be the case, as we have to deploy our first verision. But still I am very much interested in the experiences made by you guys/women.

Concerning clustering I think it makes generally more sense to cluster horizontally, as server/service drop outs are better covered and performance gets really increase by adding addtional CPUs. But that's just a very superficial thought, it depends a lot on the reasons for having clusters at all.

Cheers
Daniel

Posted by Daniel Frey on April 03, 2008 at 01:56 PM PDT #

Hi Daniel, Ravi and Manishi

Sorry I could not respond earlier. I was held up with other deliverables.
The problem that Manishi reported is specific to the experimental component that I posted.

Please take a look at my latest posting to see an example that includes a composite application that uses sun-bpel-engine and sun-file-binding.

Manishi - As shown in the example, you can use the install-component ant target to install any JBI component (BindingComponent or ServiceEngine).

Daniel - I have a 6.1 setup and everything works fine. Were you able to try this in a setup without the update?

Meyers - I believe the problem that you faced, InstanceNotFound for the AdminService MBean is due to the configuration property setting not kicking in. I observed that sometimes the server needs to be bounced once for this property to take effect.

Thanks
Annies

Posted by 75.37.21.194 on April 04, 2008 at 04:33 PM PDT #

Annie:
Thank you for replying. and thank you for updating the exp component.I downloaded he updated components and ran the commands as you mentioned previously.
I see that you have updated the "openesb-websphere-client" components. The rest of the components are same. Let me know if i am wrong.
I am still getting the same error as i was getting earler which is as follows:

===================================================================================================================================================================================
[4/7/08 10:51:02:359 EDT] 00000033 SystemErr R java.lang.Exception: Invalid pattern null for {http://sun.com/transform-file.wsdl}transformServicefiletxEP.
[4/7/08 10:51:02:359 EDT] 00000033 SystemErr R at com.sun.jbi.binding.file.FileCommand.execute(FileCommand.java:295)
[4/7/08 10:51:02:359 EDT] 00000033 SystemErr R at com.sun.jbi.binding.file.framework.WorkThread.processCommand(WorkThread.java:231)
[4/7/08 10:51:02:359 EDT] 00000033 SystemErr R at com.sun.jbi.binding.file.framework.WorkThread.run(WorkThread.java:150)
[4/7/08 10:51:02:359 EDT] 00000033 SystemErr R at java.lang.Thread.run(Thread.java:797)
====================================================================================================================================================================================

I would like to know couple of things because i feel that i am wokring with black box.Knowing these things are very important for teh success of our project. This is a high priority .It would be helpful if you can clarify the questions.

1) I want to get clarification what each components does in the sample.The components which i installed for the demo are :
a) sun-wsdl-library - I am understanding this is the shared library. I would like to know what it does?I would like to know what is the role of this component?How do you compare this component with OpenESB components?
b) SunFileBinding - This is the same BC which you get with the installation with OpenESB. so i know what it is.
c) SunTransformationEngine - I dont know what this does. what JBI component it is?I would like to know what is the role of this component?How do you compare this component with OpenESB components?
d) FileTransformApp - I think is the service assembly file which i used to deploy on OpenESB.It contains 2 SU's (TransformationEngine and FileBinding).
e) Sample_input.xml - This is the sample test file.

2) I also would like to know what are the steps to deploy on OpenESB on websphere.If i understand correctly These are following steps.
a) Install the BC's,SE's and shared libraries using the install command you used in your sample.
b) Deploy the service assembly and then start the service assembly.

3) I saw that there was another post by you on Apr4th. If i understand it corrrectly the post on Aug 13th 2007 is the post to install openesb on websphere 6.1 and demo to test the install. The post on Apr 4th is install bpel engine into OpenESB installed on websphere.This clog also contains the a demo test the installation.

Annie: Your help would be really helpful. we are planning to install other BC's and/or SE's into OpenESB on websphere from the existing OpenESB component library.
I will also be testing the bpel on OpenESB on websphere.

I also would like to know who in Sun will be the right person to talk about this challenge of making different components work in OpenESB on websphere. I have to agree that running OpenESB on websphere gives you a bit of challenge when compared tom aking it work on netbeans/glassfish environment.

Thanks a bunch in advance.

Regards
Ravi

Posted by ravi on April 07, 2008 at 08:32 AM PDT #

Annie: I also tried the bpel-engine on websphere. That sample app too did not work. all the components and shared libraries are installed fine but the sample did not run. for FYI, I am posting the "list-all" ant command. i see everything is fine. Let me know what needs to be done.

Regards
Ravi.n

Posted by ravi on April 07, 2008 at 10:34 AM PDT #

The list all command is as follows:
=======================================================================

C:\Documents and Settings\Administrator>ant -f C:/openesb/websphere-latest/jbi_admin.xml -Djbi.port=2809 list-all
Buildfile: C:\openesb\websphere-latest\jbi_admin.xml

-pre-jbi-admin-setup:

-jbi-admin-setup:

-init-macrodef-echo-info:

init-jbi-admin:

-init-list-options:

-list-service-engines-in-xml-ouput:

-list-service-engines-in-text-output:
[jbi-list-service-engines] ============================================================
[jbi-list-service-engines] List of Service Engines for Target "server"
[jbi-list-service-engines] ============================================================
[jbi-list-service-engines] Name : SunTransformationEngine
[jbi-list-service-engines] State : Started
[jbi-list-service-engines] Description: This is Transformation Engine. This engine transforms XML and CSV data based on provided XSL styleshet.
[jbi-list-service-engines] ------------------------------------------------------------
[jbi-list-service-engines] Name : sun-bpel-engine
[jbi-list-service-engines] State : Started
[jbi-list-service-engines] Description: This is a bpel service engine.
[jbi-list-service-engines] ------------------------------------------------------------

list-service-engines:

-list-binding-components-in-xml-ouput:

-list-binding-components-in-text-output:
[jbi-list-binding-components] ============================================================
[jbi-list-binding-components] List of Binding Components for Target "server"
[jbi-list-binding-components] ============================================================
[jbi-list-binding-components] Name : SunFileBinding
[jbi-list-binding-components] State : Started
[jbi-list-binding-components] Description: Binding to send messages to sample engine.
[jbi-list-binding-components] ------------------------------------------------------------
[jbi-list-binding-components] Name : sun-file-binding
[jbi-list-binding-components] State : Started
[jbi-list-binding-components] Description: File binding
[jbi-list-binding-components] ------------------------------------------------------------

list-binding-components:

-list-shared-libraries-in-xml-ouput:

-list-shared-libraries-in-text-output:
[jbi-list-shared-libraries] ============================================================
[jbi-list-shared-libraries] List of Shared Libraries for Target "server"
[jbi-list-shared-libraries] ============================================================
[jbi-list-shared-libraries] Name : sun-encoder-library
[jbi-list-shared-libraries] State : Installed
[jbi-list-shared-libraries] Description: Encoder SharedLibrary. Encoders supported: customencoder-1.0 hl7encoder-1.0 cocoencoder-1.0
[jbi-list-shared-libraries] ------------------------------------------------------------
[jbi-list-shared-libraries] Name : sun-shared-util-library
[jbi-list-shared-libraries] State : Installed
[jbi-list-shared-libraries] Description: A collection of shared utilities for JBI components.
[jbi-list-shared-libraries] ------------------------------------------------------------
[jbi-list-shared-libraries] Name : sun-wsdl-library
[jbi-list-shared-libraries] State : Installed
[jbi-list-shared-libraries] Description: This library provides WSDL 1.1/2.0 parsing support and message-wrapping utilities used to send WSDL 1.1-defin
ed messages over the Normalized Message Router (NMR).
[jbi-list-shared-libraries] ------------------------------------------------------------

list-shared-libraries:

-list-service-assemblies-in-xml-ouput:

-list-service-assemblies-in-text-output:
[jbi-list-service-assemblies] ============================================================
[jbi-list-service-assemblies] List of Service Assemblies for Target "server"
[jbi-list-service-assemblies] ============================================================
[jbi-list-service-assemblies] Name : CompositeApp1
[jbi-list-service-assemblies] State : Started
[jbi-list-service-assemblies] Description: Represents the Service Assembly of CompositeApp1
[jbi-list-service-assemblies] Service units in this service assembly [2]
[jbi-list-service-assemblies] Service unit : CompositeApp1-BpelModule1
[jbi-list-service-assemblies] State : Started
[jbi-list-service-assemblies] Deployed on: sun-bpel-engine
[jbi-list-service-assemblies] Description: Represents this Service Unit
[jbi-list-service-assemblies] Service unit : CompositeApp1-sun-file-binding
[jbi-list-service-assemblies] State : Started
[jbi-list-service-assemblies] Deployed on: sun-file-binding
[jbi-list-service-assemblies] Description: Represents this Service Unit
[jbi-list-service-assemblies] ------------------------------------------------------------
[jbi-list-service-assemblies] Name : FileTransformApp
[jbi-list-service-assemblies] State : Started
[jbi-list-service-assemblies] Description: A demo SA using Filebinding and TransformationEngine
[jbi-list-service-assemblies] Service units in this service assembly [2]
[jbi-list-service-assemblies] Service unit : FileTransformApp-FileBinding
[jbi-list-service-assemblies] State : Started
[jbi-list-service-assemblies] Deployed on: SunFileBinding
[jbi-list-service-assemblies] Description: Represents this Service Unit
[jbi-list-service-assemblies] Service unit : FileTransformApp-TransformationEngine
[jbi-list-service-assemblies] State : Started
[jbi-list-service-assemblies] Deployed on: SunTransformationEngine
[jbi-list-service-assemblies] Description: Represents this Service Unit
[jbi-list-service-assemblies] ------------------------------------------------------------

list-service-assemblies:

list-all:

BUILD SUCCESSFUL
Total time: 4 minutes 5 seconds
========================================================================
Regards
Ravi.n

Posted by ravi on April 07, 2008 at 10:35 AM PDT #

Annie: I got the bpel-engine sample working. It was a silly mistake. The input file name was "input.txt.txt" so when i changed it to input.txt it worked.

But i am still not able to make the first sample work. also i notices that there are 2 file binding components. "filebc" and "file-binding" could you let me know the difference between these two. the first one is from openesb components but what about the second?

Regards
Ravi.n

Posted by ravi on April 07, 2008 at 10:58 AM PDT #

Annie: The other problem i am facing is stopping the openesb-websphere_war application . i used several techniques : admin console, windows service and also via command line. none of them are working. do u hv any tips or tricks.

Regards
Ravi.n

Posted by ravi on April 07, 2008 at 12:42 PM PDT #

Hi Ravi,

sun-file-binding is developed as part of the Open JBI components project at
https://open-jbi-components.dev.java.net/.
This is being actively developed and maintained.

The file binding used in the demo for the first posting is an experimental component used primarily for testing purposes.

Regarding, not being able to stop the application, let me try that out and get back to you.

Thanks
Annies

Posted by 192.18.43.225 on April 08, 2008 at 12:11 PM PDT #

Hi Ravi,

After stopping all the components and service assemblies, I am able to stop the web application. Could you please try that?

For example:
ant -f jbi_admin.xml -Djbi.component.name=sun-file-binding stop-component
ant -f jbi_admin.xml -Djbi.service.assembly.name=CompositeApp1 stop-service-assembly

However I observed that during stop all the MBeans are not removed hence a start after that reports some issues. If this is important for you, I can look into why stop is not unregistering the MBeans. I can get to this next week.

In the mean time, if you would like to work on this, please refer to the code in open-esb repository under runtime/framework.
Please let me know if you have any questions.

Thanks
Annies

Posted by 192.18.43.225 on April 08, 2008 at 05:32 PM PDT #

Hi Annie: I installed the latest version of (4/15) openesb-websphere war file. The installation was successful but the samples are not yet all working. do u hv any suggestion.should i still use the old version?are the samples compatible with new version?. the error i am getting is
==========================================================================
BUILD FAILED
C:\openesb\websphere-latest\jbi_admin.xml:241: Install shared library failed. [
com.sun.jbi:ServiceName=ESBInstallationService,ComponentType=System
]
=======================================================================
I do not get any messages on systemerr log file or systemout log files while running the ant commands.
although i do get errors when i start the web app.
below are the errors
=======================================================================
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R javax.management.InstanceAlreadyExistsException: com.sun.jbi:cell=PGSJM4FZF1LARLNode01Cell,ControlType=Statistics,JbiName=server,node=PGSJM4FZF1LARLNode01,ServiceName=DeploymentService,process=server1,ComponentType=System
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:470)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1428)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:954)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:355)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:515)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.management.PlatformMBeanServer.registerMBean(PlatformMBeanServer.java:469)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jbi.management.support.MBeanSet.register(MBeanSet.java:350)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jbi.management.system.ModelSystemService.bootstrap(ModelSystemService.java:184)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jbi.management.system.ManagementService.createDeploymentService(ManagementService.java:374)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jbi.management.system.ManagementService.initService(ManagementService.java:123)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jbi.framework.JBIFramework.init(JBIFramework.java:193)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.WebSphereJBIFramework.load(WebSphereJBIFramework.java:143)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at java.lang.reflect.Method.invoke(Method.java:615)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.WebSphereJBIBootstrap.invoke(WebSphereJBIBootstrap.java:337)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.WebSphereJBIBootstrap.loadJBIFramework(WebSphereJBIBootstrap.java:205)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.WebSphereJBIBootstrap.start(WebSphereJBIBootstrap.java:115)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.JBIServlet.initFramework(JBIServlet.java:149)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.JBIServlet.init(JBIServlet.java:95)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at javax.servlet.GenericServlet.init(GenericServlet.java:256)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:185)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:316)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1119)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:149)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:99)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:741)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:421)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:274)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:271)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:88)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:653)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:606)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:333)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:549)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1295)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1129)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:567)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:814)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:948)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2114)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:340)
[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R javax.management.InstanceAlreadyExistsException: com.sun.jbi:cell=PGSJM4FZF1LARLNode01Cell,ControlType=Logger,JbiName=server,node=PGSJM4FZF1LARLNode01,ServiceName=DeploymentService,process=server1,ComponentType=System,LoggerName=com.sun.jbi.management.DeploymentService
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:470)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1428)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:954)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:355)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:515)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.management.PlatformMBeanServer.registerMBean(PlatformMBeanServer.java:469)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jbi.management.support.MBeanSet.register(MBeanSet.java:350)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jbi.management.system.ModelSystemService.bootstrap(ModelSystemService.java:184)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jbi.management.system.ManagementService.createDeploymentService(ManagementService.java:374)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jbi.management.system.ManagementService.initService(ManagementService.java:123)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jbi.framework.JBIFramework.init(JBIFramework.java:193)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.WebSphereJBIFramework.load(WebSphereJBIFramework.java:143)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at java.lang.reflect.Method.invoke(Method.java:615)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.WebSphereJBIBootstrap.invoke(WebSphereJBIBootstrap.java:337)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.WebSphereJBIBootstrap.loadJBIFramework(WebSphereJBIBootstrap.java:205)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.WebSphereJBIBootstrap.start(WebSphereJBIBootstrap.java:115)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.JBIServlet.initFramework(JBIServlet.java:149)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.sun.jbi.framework.websphere.JBIServlet.init(JBIServlet.java:95)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at javax.servlet.GenericServlet.init(GenericServlet.java:256)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:185)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:316)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1119)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:149)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:99)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:741)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:421)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:274)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:271)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:88)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:653)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:606)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:333)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:549)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1295)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1129)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:567)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:814)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:948)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2114)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:340)
[4/16/08 11:16:06:437 EDT] 00000016 SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)

========================================================================

Pls advice what needs to be done ASAP.

Posted by ravi on April 16, 2008 at 08:33 AM PDT #

Hi Ravi,
I see the following in your log.

[4/16/08 11:16:06:421 EDT] 00000016 SystemErr R javax.management.InstanceAlreadyExistsException:

Looks like the MBeans were not unregistered properly upon.stop/uninstall.
Could you please restart the server and see if the MBeans are getting registered?

Thanks
Annies

Posted by 192.18.101.5 on April 16, 2008 at 08:37 AM PDT #

Hi Annies: It seem that mbean is not getting registered . i restarted couple of times. could u tell me what is the prob and how to solve it?
here is the systemout.log file at server start up
================================================================
[4/16/08 11:51:27:281 EDT] 00000018 WebGroup A SRVE0169I: Loading Web Module: openesb-websphere.war.
[4/16/08 11:51:27:500 EDT] 00000018 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\ffdc\server1_3de83de8_08.04.16_11.51.27_0.txt
[4/16/08 11:51:27:531 EDT] 00000018 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\ffdc\server1_3de83de8_08.04.16_11.51.27_0.txt
[4/16/08 11:51:27:656 EDT] 00000018 Configuration I Failed to add the logger MBean for service ConfigurationService and logger name com.sun.jbi.management.ConfigurationService, as a listener on the Logger Configuration MBean com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System. com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System
[4/16/08 11:51:27:671 EDT] 00000018 messaging I Failed to add the logger MBean for service MessageService and logger name com.sun.jbi.messaging, as a listener on the Logger Configuration MBean com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System. com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System
[4/16/08 11:51:27:687 EDT] 00000018 management I Failed to add the logger MBean for service ManagementService and logger name com.sun.jbi.management, as a listener on the Logger Configuration MBean com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System. com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System
[4/16/08 11:51:27:875 EDT] 00000018 DeploymentSer I Failed to add the logger MBean for service DeploymentService and logger name com.sun.jbi.management.DeploymentService, as a listener on the Logger Configuration MBean com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System. com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System
[4/16/08 11:51:27:890 EDT] 00000018 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl open FFDC0009I: FFDC opened incident stream file C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\ffdc\server1_3de83de8_08.04.16_11.51.27_1.txt
[4/16/08 11:51:27:921 EDT] 00000018 ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream FFDC0010I: FFDC closed incident stream file C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\ffdc\server1_3de83de8_08.04.16_11.51.27_1.txt
[4/16/08 11:51:27:921 EDT] 00000018 PlatformMBean W Failed to activate MBean com.sun.jbi:cell=PGSJM4FZF1LARLNode01Cell,ControlType=Statistics,JbiName=server,node=PGSJM4FZF1LARLNode01,ServiceName=DeploymentService,process=server1,ComponentType=System
[4/16/08 11:51:27:937 EDT] 00000018 PlatformMBean W Failed to activate MBean com.sun.jbi:cell=PGSJM4FZF1LARLNode01Cell,ControlType=Logger,JbiName=server,node=PGSJM4FZF1LARLNode01,ServiceName=DeploymentService,process=server1,ComponentType=System,LoggerName=com.sun.jbi.management.DeploymentService
[4/16/08 11:51:27:953 EDT] 00000018 PlatformMBean W Failed to activate MBean com.sun.jbi:cell=PGSJM4FZF1LARLNode01Cell,ControlType=Lifecycle,JbiName=server,node=PGSJM4FZF1LARLNode01,ServiceName=DeploymentService,process=server1,ComponentType=System
[4/16/08 11:51:27:984 EDT] 00000018 InstallationS I Failed to add the logger MBean for service InstallationService and logger name com.sun.jbi.management.InstallationService, as a listener on the Logger Configuration MBean com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System. com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System
[4/16/08 11:51:28:000 EDT] 00000018 LoggingServic I Failed to add the logger MBean for service LoggingService and logger name com.sun.jbi.management.LoggingService, as a listener on the Logger Configuration MBean com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System. com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System
[4/16/08 11:51:28:015 EDT] 00000018 AdminService I Failed to add the logger MBean for service AdminService and logger name com.sun.jbi.management.AdminService, as a listener on the Logger Configuration MBean com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System. com.sun.jbi:JbiName=server,ServiceName=ConfigurationService,ControlType=LoggingService,ComponentType=System
[4/16/08 11:51:28:015 EDT] 00000018 management E javax.management.InstanceNotFoundException: com.sun.jbi:JbiName=server,ServiceName=AdminService,ControlType=Lifecycle,ComponentType=System
[4/16/08 11:51:28:031 EDT] 00000018 framework E JBIFW0003: Unable to initialize Management Service due to an exception: javax.jbi.JBIException(javax.management.InstanceNotFoundException: com.sun.jbi:JbiName=server,ServiceName=AdminService,ControlType=Lifecycle,ComponentType=System). Stack trace follows.
javax.jbi.JBIException: javax.management.InstanceNotFoundException: com.sun.jbi:JbiName=server,ServiceName=AdminService,ControlType=Lifecycle,ComponentType=System
at com.sun.jbi.management.system.ManagementService.initService(ManagementService.java:175)
at com.sun.jbi.framework.JBIFramework.init(JBIFramework.java:193)
at com.sun.jbi.framework.websphere.WebSphereJBIFramework.load(WebSphereJBIFramework.java:143)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
====================================================================

Posted by ravi on April 16, 2008 at 08:57 AM PDT #

Hi Ravi,

Could you also please verify if the configuration to disable MBean routing is setup?

Thanks
Annies

Posted by 192.18.101.5 on April 16, 2008 at 09:01 AM PDT #

Hi Annies: the custom property which you described above in step2 are there. i verified it more than 2 times. i also restarted the server still has same prob.

Regards
ravi

Posted by ravi on April 16, 2008 at 09:07 AM PDT #

Hi Annies: I am still getting the same error message. I see that the disable routing property is set up.Could you tell me
what could be the problem? is there another way to register MBean in websphere? may be command line etc.
or if there is source code and if you can tell where exactly is it registering then may be i can debug. i just want

I also would like to ask you if there are any plans to develop similar component for weblogic.we are trying to deploy
openesb on both websphere and weblogic. so i am interested in it.

Regards
Ravi

Posted by ravi on April 17, 2008 at 08:41 AM PDT #

Hi annie, i had the same ravi issue. The property is correctly set but it doesn't work.

Posted by Roberto on June 03, 2008 at 05:49 AM PDT #

Hi Roberto: I made a mistake here. there are 2 places in websphere where you can set custom properties.

one under

Servers > Application Servers > Server1(Server Infrastructure) > Administration > Custom Properties

and the second other at

Servers > Application Servers > Server1(Server Infrastructure) > Administration > Administration Services > Custom Properties

you should be changing the properties at the 2nd option.

Posted by ravi on June 03, 2008 at 06:09 AM PDT #

Hi Ravi,

i tried both path but it still doesn't work. I tried to post the server logs but the message was cutted and marked as span due to its size

Posted by Roberto on June 03, 2008 at 06:36 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed