Changes

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

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. == Current 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. == Current Progress ==No progress has been made yet == Known Problems/Solutions ==This section indicates specific problems and possible solutions for packaging Nexj Plugins.