WebSphere adapter

dkuntze

I'm doing some testing using the OD WebSphere adapter, and all seems to work fine except when it trys to start the deployed application.

It unloads the app and installs it correctly, but when it comes to start it the process dies.

WASX7017E: Exception received while running file "C:\Interwoven\OpenDeployNG\adapters\delivery\appserver\websphere\bin\wsappinstall.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7025E: Error found in String ""; cannot create ObjectName.

Process return code is 105

I've narrowed it down to the jacl script not returning the appman variable.

Any ideas?

Darin Kuntze
Senior Programming Analyst
First National Bank Nebraska, Inc.

Migrateduser

Look at the WAS adapter log to see how the Jacl script was invoked. The log line starting with "Executing ..." captures the command that was run by the adapter.

For example:
2006-01-10 12:31:26,484 INFO Executing C:\PROGRA~1\WebSphere\DeploymentManager\
bin\wsadmin.bat -f C:\Interwoven\OpenDeployNG\adapters\delivery\appserver\websp
here\bin\wsappinstall.jacl server servername nodename install start c:/interwov
en/opendeployng/tmp/bogus.ear appname "{-contextroot /dir1/dir2
-distributeApp -installdir c:/temp -nopreCompileJSPs}"

Looks like something in Jacl script is getting set to empty string while it expects to have a good value. When the script tries to use the empty string value, you get the error message.

Using the command line from adapter log, try to run the Jacl script outside of OD i.e. in a cmd window. You can add echo etc. to Jacl script to see what exactly is missing and whereabout. Perhaps something is not set right in the adapter config and when it is passed to the Jcl script, it barfs.

Kuldip