198
edits
Changes
no edit summary
[[Category:OSTEP SOP]][[Category:OSTEPWebsphere]]
= 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 =
This section will outline where to get information or files for any of the projects. Until this wiki page is complete, you may need to search google for some files or information, or ask someone.
We are deploying websphere version 7
All of the websphere related files and plugins can be found in the following location.
Host: bahamas
Directory: /data/nexj-resources/</pre>
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].
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!
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.
* [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]
= Package Websphere Application Server =
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.
== Current Manual Installation ==[[OSTEP_Websphere_Manual_Setup#Install_Websphere_Application_Server | Manual Websphere Application Server ND Installation]] == Progress ==
No progress has been made yet
This section indicates specific problems and possible solutions for the packaging Websphere application.
=== Max RPM size? Installation Script on Centos ===Problem: *The installation script for Websphere on linux assumes that you are using redhat. This will cause a problem if you try and install using a centos system. Solution:*Make the following changes to the file "/opt/IBM/WebSphere/Downloads/ApplicationServerND/WAS/install"
<pre>
</pre>
= Package Websphere Application Server Supplements =
This step requires that the Websphere application server supplements 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
== Manual Installation ==
[[OSTEP_Websphere_Manual_Setup#Install_Websphere_Application_Server_Supplements | Manual Websphere Application Server ND Supplements Installation]]
== Progress ==
No progress has been made yet
== Known Problems/Solutions ==
This section indicates specific problems and possible solutions for the packaging Websphere application supplements.
=== Installation Script on Centos ===
Problem:
*The installation script for Websphere supplements on linux assumes that you are using redhat. This will cause a problem if you try and install using a centos system.
Solution:
*Make the following changes to the file "/opt/IBM/WebSphere/Downloads/ApplicationServerNDSup/IHS/install"
<pre>
</pre>
<!--=== Installation Script on Centos Failed Configuration Action ===
Problem:
*The installation completes only with a partial success, this "may" be enough to complete this project, but we should investigate why this is happening.
<pre>
</pre>
Solution:
Problem:
*This program has packed a local version of the htpasswd binary inside it, this specific binary requires libraries that are unavailable by default.
<pre>
</pre>
Solution:
* Install the missing libraries
<pre>
</pre>
= 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.
== Current Progress ==
No progress has been made yet
=== Installation Script on Centos ===
Problem:
Solution:
<pre>
</pre>
<!--
= 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.
== Current Progress ==
No progress has been made yet
This section indicates specific problems and possible solutions for packaging Nexj Plugins
-->
= RPM Repository =
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.
== Current Progress ==
No progress has been made yet
== Known Problems/Solutions ==
This section indicates specific problems and possible solutions for the RPM Repository
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.
== Current Progress ==
No progress has been made yet
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.
== 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.
== 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.
== Current Progress ==
No progress has been made yet
== Known Problems/Solutions ==
This section indicates specific problems and possible solutions for the Websphere Single Node Configuration
-->
