OSTEP Websphere

Overview

Plan for a automated deployment of Websphere software on nexj development systems. This deployment will take place inside a centos virtual machine. The virtual machine image will be installed with a kickstart file, which means, all that is needed to deploy a development environment, is a link to the kickstart file. The kickstart will pull in the basic installation package set, followed by the installation of custom repositories hosted online, which contain all the websphere software and plugins. This custom repository would contain websphere installations, fix packs, nexj plugins, and perhaps some other packages that may be needed in a development deployment. All the packages in the repository could be updated easily(and automatically if needed), in case a new fix pack comes out, or a new nexj plugin build. From this repository it would be easy to deploy any software from it through a simple installation of the rpm packages.

Getting Started

This section will outline where to get information or files for any of the projects. Until this wiki page is complete, you may need to search google for some files or information, or ask someone.

Websphere Version: We are deploying websphere version 7

Websphere Files: All of the websphere related files and plugins can be found in the following location. Host: bahamas Directory: /data/nexj-resources/

Websphere Fix Packs Not every Fix Pack will be required. Download the latest Websphere Fix Packs. The latest Websphere Fix Packs can be found on this site.

Nexj Plugin Get the latest NexJ Plugins for Websphere.

Known Problems/Solutions Please read the known problems and solutions of each project. If you find a new problem that may need a manual fix, place the new problem and fix under the correct project. Document!

Manual Websphere Setup: Manual Websphere Setup

Single Node Configuration The single node configuration has mostly been documented, but you may need more resources in order to complete it. You can find many resources for wsadmin and commands to create members, servers, clusters, etc, all on the command line.

• add cluster commands
• create cluster commands
• cluster configuration
• create servers commands

Package Websphere

This step requires that the Websphere application is packaged within a rpm file. This step should include documentation on how it was packaged, any modifications made to the installation scripts/response files, and any difficulties that were experienced during the installation/packaging.

Who is working on this: place name here

Manual Installation

Manual Websphere Application Server ND Installation

Progress

No progress has been made yet

Known Problems/Solutions

This section indicates specific problems and possible solutions for the packaging Websphere application.

Max RPM size?

Problem:

Is websphere installer too large for a rpm package? This will need to be looked into.

Solution:

This should not actually be a issue.

Installation Script on Centos

Problem:

The installation script for Websphere on linux assumes that you are using redhat. This will cause a problem if you try and install using a centos system. 

Solution:

Make the following changes to the file "/opt/IBM/WebSphere/Downloads/ApplicationServerND/WAS/install"
* 433,434c433
<               release=`cat /etc/redhat-release | awk '{print $7}'`
---
>               #release=`cat /etc/redhat-release | awk '{print $7}'`
>               release=`cat /etc/centos-release | awk '{print $4}'`

Response File

Problem:

This file exists in the same directory as the installation script and must be modified with the correct responses for a successful installation.

Solution:

Make the following changes to the file "/opt/IBM/WebSphere/Downloads/ApplicationServerND/WAS/response.nd.txt"
35c35
<   -OPT silentInstallLicenseAcceptance="false"
---
>   -OPT silentInstallLicenseAcceptance="true"
58c58
< # -OPT allowNonRootSilentInstall="true"
---
>  -OPT allowNonRootSilentInstall="true"
70c70
< # -OPT disableOSPrereqChecking="true"
---
>  -OPT disableOSPrereqChecking="true"
76c76
< # -OPT disableNonBlockingPrereqChecking="true"
---
>  -OPT disableNonBlockingPrereqChecking="true"
95c95
< # -OPT checkFilePermissions="true"
---
>  -OPT checkFilePermissions="true"
140c140
<   -OPT profileType="cell"
---
>   -OPT profileType="none"
145c145
< # -OPT feature="noFeature"
---
>  -OPT feature="noFeature"
185c185
<   -OPT PROF_enableAdminSecurity="true"
---
>   -OPT PROF_enableAdminSecurity="false"
206c206
< # -OPT installLocation="/usr/IBM/WebSphere/AppServer"
---
>  -OPT installLocation="/opt/IBM/WebSphere/AppServer"
236c236
< # -OPT cimSelected="true"
---
>  -OPT cimSelected="false"

Package Websphere Fixpacks

This step requires that the Websphere Fix Packs are packaged within a rpm or multiple rpm files. This step should include documentation on how each were packaged, any modifications made to the installation scripts/response files, and any difficulties that were experienced during the installation/packaging. The installation of Fix Packs can only be completed after the Websphere software is installed. Automated packaging of this package rpm will be part of another step, these are not updated often, but rpms should be updated when the Fix Packs change.

Who is working on this: place name here

Progress

No progress has been made yet

Known Problems/Solutions

This section indicates specific problems and possible solutions for the Packaging Websphere Fix Packs

Installation Script on Centos

Problem:

The installation script for Websphere on linux assumes that you are using redhat. This will cause a problem if you try and install using a centos system.

Solution:

Place patch, command, or instructions to fix installation script here.

Response File

Problem:

This file exists in the same directory as the installation script and must be modified with the correct responses for a successful installation.

Solution:

Place contents of response file on wiki here.

Package Nexj Plugins

This step require the Nexj Plugins for Websphere are packaged in a rpm. This step should be very simple and shouldn't require any modifications or the files or during installation. Automated packaging of this package rpm will be part of another step, since these may be updated often.

Who is working on this: place name here

Progress

No progress has been made yet

Known Problems/Solutions

This section indicates specific problems and possible solutions for packaging Nexj Plugins

RPM Repository

Some simple questions and information will be needed for this part. Will need to find the location to keep the repository, whether it can be public or private, access to certain resources(Nexj Plugins), a way for the other scripts to automatically upload files to the repository.

Who is working on this: place name here

Progress

No progress has been made yet

Known Problems/Solutions

This section indicates specific problems and possible solutions for the RPM Repository

Centos Kickstart File

Kickstart file that installs a basic centos system with all the tools we need for the websphere deployment. Probably want this to pull in minimal packages to save on size(?), as well as installing the custom repository that allows this installation access to our websphere software, fix packs, plugins, and configuration packages. This may also just kick off the installation of websphere and start all the services when it's ready.

Who is working on this: place name here

Progress

No progress has been made yet

Known Problems/Solutions

This section indicates specific problems and possible solutions for the Centos Kickstart File

Script to Automate Websphere Fix Pack Packaging

This step requires a script to be made which will automatically package, latest Nexj Plugin files, into a rpm package and update the repository.

Who is working on this: place name here

Progress

No progress has been made yet

Known Problems/Solutions

This section indicates specific problems and possible solutions for the Script to Automate Websphere Fix Pack Packaging

Script to Automate Nexj Plugins Packaging

This step requires a script to be made which will automatically package, latest Nexj Plugin files, into a rpm package and update the repository.

Who is working on this: place name here

Progress

No progress has been made yet

Known Problems/Solutions

This section indicates specific problems and possible solutions for the Script to Automate Nexj Plugins Packaging

Websphere Single Node Configuration

This step may need more planning and testing. This is the final step which is done after the Websphere installation, Websphere Fix Packs installation, and Nexj Plugins installation. This step could become a part of a package that installs a single node configuration to websphere, it could be a script that runs the proper wsadmin commands to configure websphere, or it could be a puppet instance to deploy the configuration. No matter which option is chosen, it should be packaged and stored in the repository to keep with the same deployment method.

Who is working on this: place name here

Progress

No progress has been made yet

Known Problems/Solutions

This section indicates specific problems and possible solutions for the Websphere Single Node Configuration