Open main menu

CDOT Wiki β

Changes

OSTEP Websphere

3,544 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 =
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.
 
'''Manual Websphere Setup:''' [[OSTEP_Websphere_Manual_Setup | Manual Websphere Setup]]
'''Websphere Version:'''
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'''
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!
 
'''Manual Websphere Setup:'''
[[OSTEP_Websphere_Manual_Setup | Manual Websphere Setup]]
'''Single Node 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.
This section indicates specific problems and possible solutions for the packaging Websphere application.
=== Max RPM size? Installation Script on Centos ===Problem: <pre>Is websphere installer too large *The installation script for a rpm package? Websphere on linux assumes that you are using redhat. This will need to be looked intocause 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>
This should not actually be a issue.* 433,434c433< release=`cat /etc/redhat-release | awk '{print $7}'`---> #release=`cat /etc/redhat-release | awk '{print $7}'`> release=`cat /etc/centos-release | awk '{print $4}'`
</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:
<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 "393c393,394< release=`cat /optetc/IBMredhat-release | awk '{print $7}'`---> #release=`cat /WebSphereetc/Downloads/ApplicationServerNDredhat-release | awk '{print $7}'`> release=`cat /WASetc/install"centos-release | awk '{print $4}'`* 433433c434,434c433435
< release=`cat /etc/redhat-release | awk '{print $7}'`
---
</pre>
<!--=== Response File 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>(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(29-Oct-2014 1:09:52 PM), Process, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, target platform: name="Linux" version="3.10.0-123.6.3.el7.x86_64" arch="amd64"(29-Oct-2014 1:09:52 PM), Process, com.installshield.wizardx.conditions.PlatformWizardBeanCondition, dbg.platform, condition platform: name="Windows .*" version="." arch="."(29-Oct-2014 1:09:52 PM), Process, com.ibm.ws.install.ni.ismp.actions.SettleNIFRegistryAction, msg1, Current install/uninstall process is successful. Process type is: install(29-Oct-2014 1:09:52 PM), Process, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=2(29-Oct-2014 1:09:52 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFPARTIALSUCCESS</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>
This (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 exists or directorySTACK_TRACE: 15java.io.IOException: Cannot run program "/opt/IBM/WebSphere/HTTPServer/bin/htpasswd" (in the same directory as the installation script and must be modified with the correct responses for a successful installation"/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.<init>(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>
Make the following changes to the file "/opt/IBM/WebSphere/Downloads/ApplicationServerND/WAS/response.nd.txt"35c35< -OPT silentInstallLicenseAcceptance="false"---> -OPT silentInstallLicenseAcceptance="true"58c58< # -OPT allowNonRootSilentInstall="true"---> -OPT allowNonRootSilentInstall="true"70c70< # -OPT disableOSPrereqChecking="true"---> -OPT disableOSPrereqChecking="true"76c76< # -OPT disableNonBlockingPrereqChecking="true"---> -OPT disableNonBlockingPrereqChecking="true"95c95< # -OPT checkFilePermissions="true"---> -OPT checkFilePermissions="true"140c140< -OPT profileType="cell"---> -OPT profileType="none"145c145< # -OPT feature="noFeature"---> -OPT feature="noFeature"185c185< -OPT PROF_enableAdminSecurity="true"---> -OPT PROF_enableAdminSecurity="false"206c206< # -OPT installLocation="/usr/IBM/WebSphere/AppServer"---> -OPT installLocation="/opt/IBM/WebSphere/AppServer"236c236< # -OPT cimSelected="true"---> -OPT cimSelected="false"sudo yum install glibc*i686*
</pre>
=== 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
-->
Oatley
198
edits
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/wiki/Special:MobileDiff/106534...106635"