198
edits
Changes
→Project Plan
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.
= Project Plan Getting Started =This section will outline the steps that will need where to be done in order to accomplish the goal get information or files for any of automating the Websphere deployment for nexj systemsprojects. Another section will be made Until this wiki page is complete, you may need to search google for each of the stepssome files or information, which will contain greater detailor ask someone.
== Websphere Version ==
We are deploying websphere version 7
== Websphere Files ==
All of the websphere related files and plugins can be found in the following location.
<pre>
Host: bahamas
Directory: /data/nexj-resources/
</pre>
== 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 ==
Please read the known problems and solutions of each project. If you find a new problem that may need a manual fix, place the new problem and fix under the correct project. Document!
== Single Node Configuration ==
The single node configuration has mostly been documented, but you may need more resources in order to complete it. You can find many resources for wsadmin and commands to create members, servers, clusters, etc, all on the command line.
<pre>
[http://www-01.ibm.com/support/knowledgecenter/SSAW57_7.0.0/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/txml_addcluster.html add cluster commands]
[http://www-01.ibm.com/support/knowledgecenter/SSFTDH_7.5.1/com.ibm.wbpm.imuc.sbpm.doc/topics/tins_create_cluster.html create cluster commands]
[http://www-01.ibm.com/support/knowledgecenter/SSAW57_7.0.0/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rxml_atclusterconfig.html cluster configuration]
[http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rxml_atservermanagement.html create servers commands]
</pre>
= Package Websphere =
