'''Who is working on this:''' place name here

No progress has been made yet

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.

No progress has been made yet

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.

No progress has been made yet

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.

No progress has been made yet

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.

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.

No progress has been made yet

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

No progress has been made yet

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.

No progress has been made yet

== Known Problems/Solutions ==

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