198
edits
Changes
no edit summary
== Known Problems/Solutions ==
This section indicates specific problems and possible solutions for the RPM Repository
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, websphere fixpacks into a rpm package and update the repository.
'''Who is working on this:''' place name here
== 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.
== 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.
== Known Problems/Solutions ==
This section indicates specific problems and possible solutions for the Websphere Single Node Configuration
-->