198
edits
Changes
no edit summary
= 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 =
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 [http://www-01.ibm.com/support/docview.wss?uid=swg27009661 site].
'''Nexj Plugin'''Get the latest NexJ Plugins for Websphere.
'''Known Problems/Solutions'''
</pre>
<!--
=== Failed Configuration Action ===
</pre>
Solution:
* None so far.No longer issue, moved to another bug-->
=== Failed to run htpasswd ===
Place contents of response file on wiki here.
</pre>
<!--
= Package Nexj Plugins =
This section indicates specific problems and possible solutions for packaging Nexj Plugins
-->
= RPM Repository =
== 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
-->