UNABLE TO INSTALL SIBWS Application

[arthur...@gmail.com]

So I have begun exploring installation of a webservices gateway but when I install this application (WAS 6, Windows 2000) by following the directions given here :

http://www-128.ibm.com/developerworks/websphere/techjournal/0502_reinitz/0502_reinitz.html

I get the following error when I do the following :

C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v6\bin>wsadmin -f ../util/si
bwsInstall.jacl INSTALL -installRoot "C:\\Program Files\\IBM\\Rational\\SDP\\6.0
\\runtimes\\base_v6" -serverName server1 -nodeName 41001-2019rNode01
WASX7209I: Connected to process "server1" on node 41001-2019rNode01 using SOAP c
onnector; The type of process is: UnManagedProcess
WASX7303I: The following options are passed to the scripting environment and are
available as argument that is stored in the argv variable: "[INSTALL, -installR
oot, C:\\Program Files\\IBM\\Rational\\SDP\\6.0\\runtimes\\base_v6, -serverName,
server1, -nodeName, 41001-2019rNode01]"
CWSWS5050I: Installing application : sibws.41001-2019rNode01.server1
ADMA5016I: Installation of sibws.41001-2019rNode01.server1 started.
ADMA5058I: Application and module versions validated with versions of deployment
targets.
ADMA5005I: The application sibws.41001-2019rNode01.server1 is configured in the
WebSphere Application Server repository.
ADMA5053I: The library references for the installed optional package are created
.
ADMA5005I: The application sibws.41001-2019rNode01.server1 is configured in the
WebSphere Application Server repository.
ADMA5001I: The application binaries are saved in C:\Program Files\IBM\Rational\S
DP\6.0\runtimes\base_v6/profiles/default\wstemp\Script10cfda4393b\workspace\cell
s\41001-2019rNode01Cell\applications\sibws.41001-2019rNode01.server1.ear\sibws.4
1001-2019rNode01.server1.ear
ADMA5005I: The application sibws.41001-2019rNode01.server1 is configured in the
WebSphere Application Server repository.
SECJ0400I: Successfuly updated the application sibws.41001-2019rNode01.server1 w
ith the appContextIDForSecurity information.
ADMA5011I: The cleanup of the temp directory for application sibws.41001-2019rNo
de01.server1 is complete.
ADMA5013I: Application sibws.41001-2019rNode01.server1 installed successfully.
CWSWS5060I: Saving configuration
CWSWS5061E: An error occurred saving the configuration : com.ibm.ws.scripting.Sc
riptingException: com.ibm.websphere.management.exception.ConfigServiceException:
WKSP0022E File validation failed --java.io.IOException: The URI length is great
er than the Windows limit of 259 characters. Unable to create or update file: C:
\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v6\profiles\default\wstemp\Scr
ipt10cfda4393b\workspace\cells\41001-2019rNode01Cell\applications\sibws.41001-20
19rNode01.server1.ear\deployments\sibws.41001-2019rNode01.server1\sibwswsdl.war\
META-INF\MANIFEST.MF.
WASX7309W: No "save" was performed before the script "../util/sibwsInstall.jacl"
exited; configuration changes will not be saved.

As you can see that it says the installation was successful however it has error in configuring.

In the console I get the same error :

[8/11/06 10:23:58:906 EDT] 00000034 WorkSpaceMast E The URI length is greater than the Windows limit of 259 characters. Unable to create or update file: C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v6\profiles\default\wstemp\Script10cfd9e022a\workspace\cells\41001-2019rNode01Cell\applications\sibws.41001-2019rNode01.server1.ear\deployments\sibws.41001-2019rNode01.server1\sibwswsdl.war\WEB-INF\ibm-web-bnd.xmi
[8/11/06 10:27:31:234 EDT] 0000003b SystemErr R java.io.IOException: URI length is greater than Windows limit of 259 characters. C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v6\profiles\default\wstemp\Script10cfda14c64\workspace\cells\41001-2019rNode01Cell\applications\sibwshttp1.41001-2019rNode01.server1.ear\deployments\sibwshttp1.41001-2019rNode01.server1\SOAPHTTPChannel1.war\META-INF\MANIFEST.MF
at com.ibm.ws.management.application.task.MetadataTask.checkURILength(MetadataTask.java:592)
at com.ibm.ws.management.application.task.MetadataTask.getFOStream(MetadataTask.java:582)
at com.ibm.ws.management.application.task.MetadataTask.save2File(MetadataTask.java:536)
at com.ibm.ws.management.application.task.MetadataTask.saveArchiveConfigDocs(MetadataTask.java:522)
at com.ibm.ws.management.application.task.MetadataTask.saveEarConfigDocs(MetadataTask.java:454)
at com.ibm.ws.management.application.task.MetadataTask.performTask(MetadataTask.java:87)
at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:253)
at java.lang.Thread.run(Thread.java:570)

[8/11/06 10:27:31:234 EDT] 0000003b SystemErr R at com.ibm.ws.management.application.task.MetadataTask.checkURILength(MetadataTask.java:592)
[8/11/06 10:27:31:234 EDT] 0000003b SystemErr R at com.ibm.ws.management.application.task.MetadataTask.getFOStream(MetadataTask.java:582)
[8/11/06 10:27:31:234 EDT] 0000003b SystemErr R at com.ibm.ws.management.application.task.MetadataTask.save2File(MetadataTask.java:536)
[8/11/06 10:27:31:234 EDT] 0000003b SystemErr R at com.ibm.ws.management.application.task.MetadataTask.saveArchiveConfigDocs(MetadataTask.java:522)
[8/11/06 10:27:31:234 EDT] 0000003b SystemErr R at com.ibm.ws.management.application.task.MetadataTask.saveEarConfigDocs(MetadataTask.java:454)
[8/11/06 10:27:31:250 EDT] 0000003b SystemErr R at com.ibm.ws.management.application.task.MetadataTask.performTask(MetadataTask.java:87)
[8/11/06 10:27:31:250 EDT] 0000003b SystemErr R at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:253)
[8/11/06 10:27:31:250 EDT] 0000003b SystemErr R at java.lang.Thread.run(Thread.java:570)
[8/11/06 10:30:45:828 EDT] 00000036 WorkSpaceMast E WKSP0022E: File validation failed --java.io.IOException: The URI length is greater than the Windows limit of 259 characters. Unable to create or update file: C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v6\profiles\default\wstemp\Script10cfda4393b\workspace\cells\41001-2019rNode01Cell\applications\sibws.41001-2019rNode01.server1.ear\deployments\sibws.41001-2019rNode01.server1\sibwswsdl.war\META-INF\MANIFEST.MF
at com.ibm.ws.sm.workspace.impl.WorkSpaceMasterRepositoryAdapter.checkURILength(WorkSpaceMasterRepositoryAdapter.java:1025)
at com.ibm.ws.sm.workspace.impl.WorkSpaceMasterRepositoryAdapter.validateFileLength(WorkSpaceMasterRepositoryAdapter.java:417)
at com.ibm.ws.sm.workspace.impl.WorkSpaceMasterRepositoryAdapter.update(WorkSpaceMasterRepositoryAdapter.java:506)
at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.update(RepositoryContextImpl.java:1767)
at com.ibm.ws.sm.workspace.impl.RepositoryContextImpl.synch(RepositoryContextImpl.java:1713)
at com.ibm.ws.sm.workspace.impl.WorkSpaceImpl.synch(WorkSpaceImpl.java:473)
at com.ibm.ws.management.configservice.ConfigServiceImpl.save(ConfigServiceImpl.java:515)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java(Compiled Code))
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1012)
at mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java(Compiled Code))
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java(Compiled Code))
at mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:86)
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java(Compiled Code))
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java(Compiled Code))
at mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(ContextClassLoaderMBeanServerInterceptor.java:167)
at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1249)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:990)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:906)
at com.ibm.ws.management.connector.AdminServiceDelegator.invoke(AdminServiceDelegator.java:157)
at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at com.ibm.ws.management.connector.soap.SOAPConnector.invoke(SOAPConnector.java(Compiled Code))
at com.ibm.ws.management.connector.soap.SOAPConnector.service(SOAPConnector.java:212)
at com.ibm.ws.management.connector.soap.SOAPConnection.handleRequest(SOAPConnection.java:55)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:680)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:484)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1470)

[arthur...@gmail.com]

By the way I noticed in the admin console that the application has not started.

Meaning the application sibws.node1.server1 and the application sibws.http1.node1.server1 has not started.

Why does something like an add-on component have to be so painful and difficult to install? The people who make these products are just plain lazy and wish to offload the work to the enduser/developer. This is a horrendous waste of our time.

[Stephen Cocks]

Arthur, As you hopefully spotted in the error message you're running up
against a windows path length limit.
You're likely to see this problem installing any application with a long-ish
name in this scenario.

There are several contributory factors including

(i) the default install root of the WAS runtime under RAD is long to start
with

C:\\Program Files\\IBM\\Rational\\SDP\\6.0\\runtimes\\base_v6

(ii) the default location of the configuration workspace "wstemp" directory
is under the profile root
%WAS_INSTALL_ROOT%/profiles/default/wstemp

(iii) the number of characters in the node name (each character counts 3
times in this case)
41001-2019rNode01

A couple of techniques can be used post-install to lessen this impact

(i) subst W: C:\\Program Files\\IBM\\Rational\\SDP\\6.0\\runtimes\\base_v6
Then run wsadmin from W:\bin

(ii) Relocate the wstemp directory used by wsadmin by passing in an extra
java option
e.g. wsadmin -javaoption "-Dworkspace.root=C:/wstemp" -f .........

--
Stephen Cocks
WESB/WPS System Administration

<arthur...@gmail.com> wrote in message
news:857957649.1155306896...@ltsgwas009.sby.ibm.com...

[arthur...@gmail.com]

I attempted both the following measures. And I still get the same error. As you can see I am using an alias for the WAS_HOME as W:\ using the subst command as you indicated. then I also passed the -javaoption etc.?

I hope I don't have to start writing assembly line code now in order to install a plugin component. Thanks for your help. Apparently it says it started it successfully but it never shows up on the admin console's enterprise Applications list.

The install path I am using is not unusual. These are defaults provided upon installation.

W:\bin>wsadmin -javaoption "-Dworkspace.root=C:\\wstemp" -f ../util/sibwsInstall
jacl INSTALL -installRoot W:\\ -serverName server1 -nodeName 41001-2019rNode01

WASX7209I: Connected to process "server1" on node 41001-2019rNode01 using SOAP c
onnector; The type of process is: UnManagedProcess
WASX7303I: The following options are passed to the scripting environment and are
available as argument that is stored in the argv variable: "[INSTALL, -installR

oot, W:\\, -serverName, server1, -nodeName, 41001-2019rNode01]"

CWSWS5050I: Installing application : sibws.41001-2019rNode01.server1
ADMA5016I: Installation of sibws.41001-2019rNode01.server1 started.
ADMA5058I: Application and module versions validated with versions of deployment
targets.
ADMA5005I: The application sibws.41001-2019rNode01.server1 is configured in the
WebSphere Application Server repository.
ADMA5053I: The library references for the installed optional package are created
.
ADMA5005I: The application sibws.41001-2019rNode01.server1 is configured in the
WebSphere Application Server repository.
ADMA5001I: The application binaries are saved in C:\Program Files\IBM\Rational\S

DP\6.0\runtimes\base_v6/profiles/default\wstemp\Script10cfec5505f\workspace\cell

s\41001-2019rNode01Cell\applications\sibws.41001-2019rNode01.server1.ear\sibws.4
1001-2019rNode01.server1.ear
ADMA5005I: The application sibws.41001-2019rNode01.server1 is configured in the
WebSphere Application Server repository.
SECJ0400I: Successfuly updated the application sibws.41001-2019rNode01.server1 w
ith the appContextIDForSecurity information.
ADMA5011I: The cleanup of the temp directory for application sibws.41001-2019rNo
de01.server1 is complete.
ADMA5013I: Application sibws.41001-2019rNode01.server1 installed successfully.
CWSWS5060I: Saving configuration
CWSWS5061E: An error occurred saving the configuration : com.ibm.ws.scripting.Sc
riptingException: com.ibm.websphere.management.exception.ConfigServiceException:
WKSP0022E File validation failed --java.io.IOException: The URI length is great
er than the Windows limit of 259 characters. Unable to create or update file: C:
\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v6\profiles\default\wstemp\Scr

ipt10cfec5505f\workspace\cells\41001-2019rNode01Cell\applications\sibws.41001-20
19rNode01.server1.ear\deployments\sibws.41001-2019rNode01.server1\sibwswsdl.war\
WEB-INF\ibm-web-ext.xmi.

WASX7309W: No "save" was performed before the script "../util/sibwsInstall.jacl"
exited; configuration changes will not be saved.

[Charly Oz]

Arthur,

It looks like you're still having issues with the wstemp location.
1) Have you tried adding the -Dworkspace.root=C:\\wstemp to the generic
server startup arguments in the admin console?
2) Have you created the directory C:\\wstemp ?
3) Perhaps try using C:/wstemp

Hope this helps.

Charly.

<arthur...@gmail.com> wrote in message
news:1795810678.115532599...@ltsgwas009.sby.ibm.com...

[Stephen Cocks]

Arthur, Sorry. Stupid me. The techniques I listed work well if you're in
"-conntype NONE" mode (which you could use in this case). Because then its
the local wsadmin JVM that's actually installing the application. In your
scenario the commands are being sent to the server, so it's the server's
knowledge of install roots and wstemp locations that matters.

I believe you could pass the "-Dworkspace.root=" option using the JVM
options setting for the server. I haven't had the chance to verify this
works.

I appreciate these are the standard default directories and that you're not
doing something that should be this difficult.

--
Stephen Cocks
WESB/WPS System Administration

<arthur...@gmail.com> wrote in message
news:1795810678.115532599...@ltsgwas009.sby.ibm.com...

[Athar Shiraz]

Stephen,

Would you please elaborate on what you wrote in this post please.

Would I have to pass anymore parameters? If so which ones? are you asking me to pass "-conntype NONE"?

I tried that and still would not install :

W:\bin>wsadmin -conntype NONE -javaoption "-Dworkspace.root=C:\\wstemp" -f../uti
l/sibwsInstalljacl INSTALL -installRoot W:\\ -serverName server1 -nodeName 41001
-2019rNode01
WASX7357I: By request, this scripting client is not connected to any server proc
ess. Certain configuration and application operations will be available in local
mode.
WASX7411W: Ignoring the following provided option: [-f../util/sibwsInstalljacl,
INSTALL, -installRoot, W:\\, -serverName, server1, -nodeName, 41001-2019rNode01]

WASX7029I: For help, enter: "$Help help"

--

This sucks : if it takes days just to get something to install in an enterprise environment and with our deadlines I am just amazed how anyone gets anything done without calling in IBM consultants...
A

> Arthur, Sorry. Stupid me. The techniques I listed
> work well if you're in
> "-conntype NONE" mode (which you could use in this
> case). Because then its
> the local wsadmin JVM that's actually installing the
> application. In your
> scenario the commands are being sent to the server,
> so it's the server's
> knowledge of install roots and wstemp locations that
> matters.
>
> I believe you could pass the "-Dworkspace.root="
> option using the JVM
> options setting for the server. I haven't had the
> chance to verify this
> works.
>
> I appreciate these are the standard default
> directories and that you're not
> doing something that should be this difficult.
>
> --
> Stephen Cocks
> WESB/WPS System Administration
>

> 19rNode01.server1.ear\deployments\sibws.41001-2019rNod

[Stephen Cocks]

Arthur,

Yes, one option is to install the application in disconnected mode using
"-conntype NONE".

You nearly had the command right, but missed a space between the "-f" and
the "../util" which appears to cause more problems than you might expect
(the WASX7411W message indicates that all the interesting options and
parameters are being ignored).

--
Stephen Cocks
WESB/WPS System Administration

"Athar Shiraz" <arthur...@gmail.com> wrote in message
news:1481577506.115556446...@ltsgwas010.sby.ibm.com...

[Athar Shiraz]

> Arthur,
>
> Yes, one option is to install the application in
> disconnected mode using
> "-conntype NONE".
>
> You nearly had the command right, but missed a space
> between the "-f" and
> the "../util" which appears to cause more problems
> than you might expect
> (the WASX7411W message indicates that all the
> interesting options and
> parameters are being ignored).

Ok I fixed that with the following command and error :

W:\bin>wsadmin -conntype NONE -javaoption "-Dworkspace.root=C:\\WUTemp" -f ../ut
il/sibwsInstall.jacl INSTALL -installRoot W:\\ -serverName server1 -nodeName 410

01-2019rNode01
WASX7357I: By request, this scripting client is not connected to any server proc
ess. Certain configuration and application operations will be available in local
mode.

WASX7303I: The following options are passed to the scripting environment and are
available as argument that is stored in the argv variable: "[INSTALL, -installR
oot, W:\\, -serverName, server1, -nodeName, 41001-2019rNode01]"
CWSWS5050I: Installing application : sibws.41001-2019rNode01.server1
ADMA5016I: Installation of sibws.41001-2019rNode01.server1 started.
ADMA5058I: Application and module versions validated with versions of deployment
targets.
ADMA5005I: The application sibws.41001-2019rNode01.server1 is configured in the
WebSphere Application Server repository.
ADMA5053I: The library references for the installed optional package are created
.
ADMA5005I: The application sibws.41001-2019rNode01.server1 is configured in the
WebSphere Application Server repository.

ADMA5001I: The application binaries are saved in C:\\WUTemp\cells\41001-2019rNod
e01Cell\applications\sibws.41001-2019rNode01.server1.ear\sibws.41001-2019rNode01

server1.ear
ADMA5005I: The application sibws.41001-2019rNode01.server1 is configured in the
WebSphere Application Server repository.
SECJ0400I: Successfuly updated the application sibws.41001-2019rNode01.server1 w
ith the appContextIDForSecurity information.
ADMA5011I: The cleanup of the temp directory for application sibws.41001-2019rNo
de01.server1 is complete.
ADMA5013I: Application sibws.41001-2019rNode01.server1 installed successfully.
CWSWS5060I: Saving configuration
CWSWS5061E: An error occurred saving the configuration : com.ibm.ws.scripting.Sc
riptingException: com.ibm.websphere.management.exception.ConfigServiceException:

WKSP0009E Workspace is invalid

\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v6\profiles\default\wstemp\Scr

ipt10d0db34d44\workspace\cells\41001-2019rNode01Cell\applications\sibws.41001-20
19rNode01.server1.ear\deployments\sibws.41001-2019rNode01.server1\META-INF\ibm-a
pplication-bnd.xmi.

WASX7309W: No "save" was performed before the script "../util/sibwsInstall.jacl"
exited; configuration changes will not be saved.

--

So I figured that since the workspace is invalid (though where did the C:\Program Files go? ) so I removed the -javaoption part with the workspace.root variable:

W:\bin>wsadmin -conntype NONE -f ../util/sibwsInstall.jacl INSTALL -installRoot

W:\\ -serverName server1 -nodeName 41001-2019rNode01

WASX7357I: By request, this scripting client is not connected to any server proc
ess. Certain configuration and application operations will be available in local
mode.

WASX7303I: The following options are passed to the scripting environment and are
available as argument that is stored in the argv variable: "[INSTALL, -installR
oot, W:\\, -serverName, server1, -nodeName, 41001-2019rNode01]"
CWSWS5050I: Installing application : sibws.41001-2019rNode01.server1

CWSWS5066I: The application W:\/installableApps/sibws.ear has already been insta
lled.
CWSWS5060I: Saving configuration
WASX7017E: Exception received while running file "../util/sibwsInstall.jacl"; ex
ception information: com.ibm.ws.scripting.ScriptingException: AdminControl servi
ce not available

At a previous attempt however, I had sibws showing up in the enterprise Applications section however there was neither a green arrow nor a red cross but a greyed out circl with a slash in it that said unavailable (I believe).

[Athar Shiraz]

By the way when I look into installed apps I see a host of sibws ear files as well as a sibws.ear file and a SIBMsgMigrationUtility.ear and a sibwsauthbean.ear, sibwshttpchannel1.ear, sibwsjmschannel1.ear

Why is it there in the installed apps but not showing up on the admin console browser?

[Athar Shiraz]

W:\bin>wsadmin -conntype NONE -f ../util/sibwsInstall.jacl INSTALL -installRoot
W:\\ -serverName server1 -nodeName 41001-2019rNode01
WASX7357I: By request, this scripting client is not connected to any server proc
ess. Certain configuration and application operations will be available in local
mode.
WASX7303I: The following options are passed to the scripting environment and are
available as argument that is stored in the argv variable: "[INSTALL, -installR
oot, W:\\, -serverName, server1, -nodeName, 41001-2019rNode01]"
CWSWS5050I: Installing application : sibws.41001-2019rNode01.server1
CWSWS5066I: The application W:\/installableApps/sibws.ear has already been insta
lled.
CWSWS5060I: Saving configuration
WASX7017E: Exception received while running file "../util/sibwsInstall.jacl"; ex
ception information: com.ibm.ws.scripting.ScriptingException: AdminControl servi
ce not available

--

By the way the error says it has already been installed but it has not. Secondly everytime I create a directory for workspace.root and execute a command pointing to the temp directory the entire directory disappears.