198
edits
Changes
no edit summary
= 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
== Current Progress ==
=== Max RPM size? ===
Problem:
Solution:
=== Installation Script on Centos ===
Problem:
Solution:
=== Response File ===
Problem:
Solution:
= 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
== Current Progress ==
=== Installation Script on Centos ===
Problem:
Solution:
=== Response File ===
Problem:
Solution:
= 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
== Current Progress ==
No progress has been made yet
== Known Problems/Solutions ==
This section indicates specific problems and possible solutions for packaging Nexj Plugins
= 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
== Current 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
== Current 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
== Current Progress ==
== Known Problems/Solutions ==
This section indicates specific problems and possible solutions for packaging Nexj Plugins.the Websphere Single Node Configuration
