Patterns: Implementing Self-Service in an SOA Environment

466 Patterns: Implementing Self-Service in an SOA Environment

For example:

./wsadmin.sh -f /opt/WebSphere/AppServer/util/sibwsInstall.jacl INSTALL_RA

-installRoot /opt/WebSphere/AppServer -nodeName myNode01 -profileName

new_profile_name

In our Rational test environment we entered:

wsadmin -f c:/Rational/RSA/runtimes/base_v6/util/sibwsInstall.jacl

INSTALL_RA -installRoot “c:/Rational/RSA/runtimes/base_v6” -nodeName Node01

2. Look for the message that confirms that the SIB_RA installation completed

successfully.

Install the SIBWS application

The core application is required tor making bus-generated WSDL available. To

install the core application:

1. Run the following command in Example A-3.

Example: A-3 Installing the core application

cd <was_install>\bin

wsadmin.ext -f <was_install>/util/sibwsInstall.jacl INSTALL

-installRoot <was_install> -serverName server_name

-nodeName node_name

You can specify installation on either a server and node or a cluster. For

example:

./wsadmin.sh -f /opt/WebSphere/AppServer/util/sibwsInstall.jacl INSTALL

-installRoot /opt/WebSphere/AppServer -serverName server1 -nodeName

myNode01 -profileName new_profile_name

If you are installing on a cluster, you should run the following command

instead:

Tip: The second <was_install> must have elements in the path separated

by a forward slash (/) even on Windows system. So a path of

c:\WebSphere\AppServer becomes c:/WebSphere/AppServer.

Tip: The concept of nodes is not apparent in a standalone application server.

If you are not sure what your node name is, select Servers → Application

Servers in the administrative console. The node name is listed next to the

server in the application server list.