You will need to make sure that your deployment manager is running, if you are installing the EIF WebSphere JMS Provider in a managed node.
Extract the EIF WebSphere JMS Provider image (tec-390-fo1-ceiext.jar) to a directory on a machine where the IBM WebSphere Application Server 6.0.x is already installed.
From a command
window, enter the following command:
<WASDIR>\java\bin\java -jar <image_dir>\tec-390-fo1-ceiext.jar
-profilePath <was_profile_path>
-tecHost <hostname>
[-tecPort <port>]
From a command
shell enter the following commands:
<WASDIR>/java/bin/java -jar <image_dir>/tec-390-fo1-ceiext.jar
-profilePath <was_profile_path>
-tecHost <hostname>
[-tecPort <port>]
where
echo "WAS_USER=Administrator:WAS_PASSWORD=password" |
"C:\Program Files\IBM\WebSphere\AppServer\java\bin\java"
-jar tec-390-fo1-ceiext.jar
-profilePath "C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01"
-tecServer localhost
echo "WAS_USER=root:WAS_PASSWORD=password" |
/usr/WebSphere/AppServer/java/bin/java -jar tec-390-fo1-ceiext.jar
-profilePath /usr/WebSphere/AppServer/profiles/AppSrv01
-tecServer localhost
-tecPort 0
WebSphere Application Server needs to be restarted for the installation to take effect. The EIF WebSphere JMS Provider is started when WebSphere Application Server is started and stopped when WebSphere Application Server is stopped.
The installation utility creates the following two log files which can be used for debugging installation problems,
where
Related topics
Verifying installation
Installing EIF WebSphere JMS Provider in a cluster
Parent topic
Overview of installation