Open main menu

CDOT Wiki β

Changes

OSTEP Websphere

850 bytes added, 12:19, 31 October 2014
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'''
=== Installation Script on Centos ===
Problem:
<pre>*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. </pre>
Solution:
*Make the following changes to the file "/opt/IBM/WebSphere/Downloads/ApplicationServerND/WAS/install"
<pre>
Make the following changes to the file "/opt/IBM/WebSphere/Downloads/ApplicationServerND/WAS/install"
* 433,434c433
< release=`cat /etc/redhat-release | awk '{print $7}'`
=== Installation Script on Centos ===
Problem:
<pre>*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. </pre>
Solution:
*Make the following changes to the file "/opt/IBM/WebSphere/Downloads/ApplicationServerNDSup/IHS/install"
<pre>
Make the following changes to the file "/opt/IBM/WebSphere/Downloads/ApplicationServerNDSup/IHS/install"
393c393,394
</pre>
=== Response File ===Problem:<pre>This file exists in the same directory as the installation script and must be modified with the correct responses for a successful installation.</pre>Solution:<pre>Make the following changes to the file "/opt/IBM/WebSphere/Downloads/ApplicationServerNDSup/IHS/response.txt"51,52c51,52< -OPT silentInstallLicenseAcceptance="false"< -OPT allowNonRootSilentInstall=false---> -OPT silentInstallLicenseAcceptance="true"> -OPT allowNonRootSilentInstall="true"62c62< #-OPT disableOSPrereqChecking="true"---> -OPT disableOSPrereqChecking="true"98c98< -OPT installLocation="/usr/IBM/HTTPServer"-!--> -OPT installLocation="/opt/IBM/WebSphere/HTTPServer"176,177c176,177< -OPT setupAdminUser="useridname"< -OPT setupAdminGroup="groupname"---> -OPT setupAdminUserFailed Configuration Action ="wasadmin"> -OPT setupAdminGroup="wasadmin"283c283< -OPT washostname="localhost"---> -OPT washostname="centos"</pre>
=== 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>
The installation completes only with a partial success, this "may" be enough to complete this project, but we should investigate why this is happening.
(29-Oct-2014 1:09:52 PM), Process, com.ibm.ws.install.ni.ismp.installtoolkitbridge.ISMPInstallToolkitBridgeForNIFramework, wrn, Config action failed: CallPostinst - /opt/IBM/WebSphere/HTTPServer/properties/version/nif/config/install/CallPostinst.ant
(29-Oct-2014 1:09:52 PM), Process, com.ibm.ws.install.ni.ismp.installtoolkitbridge.ISMPInstallToolkitBridgeForNIFramework, wrn, Config action failed: InstallWASPlugin - /opt/IBM/WebSphere/HTTPServer/properties/version/nif/config/install/InstallWASPlugin.ant
</pre>
Solution:
* No longer issue, moved to another bug
-->
 
=== Failed to run htpasswd ===
 
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>
None so far(29-Oct-2014 3:09:06 PM), Process, com.ibm.ws.install.ihs.ismp.actions.ExecWizardActionFromDirectory, err, java.io.IOException: Cannot run program "/opt/IBM/WebSphere/HTTPServer/bin/htpasswd" (in directory "/opt/IBM/WebSphere/HTTPServer"): java.io.IOException: error=2, No such file or directorySTACK_TRACE: 15java.io.IOException: Cannot run program "/opt/IBM/WebSphere/HTTPServer/bin/htpasswd" (in directory "/opt/IBM/WebSphere/HTTPServer"): java.io.IOException: error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:470) at java.lang.Runtime.exec(Runtime.java:604) at com.ibm.ws.install.ihs.ismp.actions.ExecWizardActionFromDirectory.executeProcess(ExecWizardActionFromDirectory.java:202) at com.ibm.ws.install.ihs.ismp.actions.ExecWizardActionFromDirectory.execute(ExecWizardActionFromDirectory.java:307) at com.installshield.wizard.StandardWizardListener.execute(StandardWizardListener.java:123) at com.installshield.wizard.StandardWizardListener.currentBeanChanged(StandardWizardListener.java:106) at com.installshield.wizard.Wizard$RunThread.run(Wizard.java:1569)Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory at java.lang.Throwable.</preinit>(Throwable.java:67) at java.lang.UNIXProcess.<init>(UNIXProcess.java:197) at java.lang.ProcessImpl.start(ProcessImpl.java:101) at java.lang.ProcessBuilder.start(ProcessBuilder.java:463) ... 6 more
</pre>
Solution:
* Install the missing libraries
<pre>
sudo yum install glibc*i686*
</pre>
= Package Websphere Fixpacks =
=== Installation Script on Centos ===
Problem:
<pre>*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.</pre>
Solution:
<pre>
</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
-->
198
edits