test

Sun Update Connection - Enterprise 1.0 User's Guide

WebSphere

WebSphere is another popular licensed application that is not included in vendor distributions.

If you have the WebSphere CD and a valid license, you can use this scenario to make installation faster and to ensure that your servers are completely managed by Sun Update Connection – Enterprise. After you have uploaded WebSphere as an NCO to the local knowledge base, the Local Expansion Technology generates rules for it. These rules ensure that WebSphere will work as an integral part of your environment.

ProcedureTo Deploy WebSphere on Multiple Machines

This procedure uses a script that calls up the WebSphere response file during automated installation.

  1. Upload the WebSphere RPM to the local knowledge base.

    The RPM will be listed under Local -> Local RPMs. See Adding Undetected Linux Software.

  2. Create a Local File Declaration that is the path where the response file should be installed.

    For example, the path is /tmp/WSresponse.txt

    See Creating File Declarations.

  3. Upload the response file as a Local Configuration File under the File Declaration.

    See Uploading Local Configuration Files.

  4. Create a script that runs WebSphere integrated installation procedures with the response file and then starts WebSphere.


    #!/bin/sh 

# In this example, the installation directory should be 
# on a local filesystem. Should be updated for NFS if 
# moved to a non-standalone demo system 

SOURCE_DIR=”/root/demoscripts/websphere/WAS5Trial” 
WS_DIR=”/opt/WebSphere/AppServer/bin” 

# Ensure that the installation directory is available 

if [ ! -f $SOURCE_DIR/install ] ; 
then 
   echo “WebSphere installer not available.” 
   exit 1 
fi 

#Install WebSphere using response file 

$SOURCE_DIR/install -options /tmp/wsresponse.rsp 

# Start the WebSphere server 

$WS_DIR/startServer.sh server1 

exit 0

  5. Upload the script under Local -> Post-actions -> postinstallWS.

    See Uploading Actions.

  6. Create a script that creates WebSphere users and groups.


    #!/bin/sh 

# In this example, the installation directory should be 
# on a local filesystem. Should be updated for NFS if 
# moved to a non-standalone demo system 

SOURCE_DIR=”/root/demoscripts/websphere/WAS5Trial” 

# Users and groups needed if installing the Messaging Sub-system 
# (MQ Series) 

groupadd mqm 
groupadd mqbrkrs 

useradd -g mqm -G mqbrkrs mqm 

# Ensure that the installation directory is available 

if [ ! -f $SOURCE_DIR/install ] ; 
then 
   echo “WebSphere installer not available.” 
   exit 1 
fi 

exit 0

  7. Upload the script under Local -> Post-actions -> postsetupWS.

    See Uploading Actions.

  8. Create a profile that requires the following:

    • WebSphere RPM

    • Local -> Configuration files -> response file

    • Local -> Post-actions -> postinstallWS

    See To Create a Profile.

  9. Create a profile that requires Local -> Post-actions -> postsetupWS.

    See To Create a Profile.

  10. Create a complex job that deploys the first profile and then the second profile on selected hosts.

    See Creating Complex Jobs.