Changes

Jump to: navigation, search

OSTEP Websphere

75 bytes added, 16:54, 27 October 2014
no edit summary
= Project Plan =
This section will outline the steps that will need to be done in order to accomplish the goal of automating the Websphere deployment for nexj systems. Another section will be made for each of the steps, which will contain greater detail.
== Package Websphere ==
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.
=== Known Problems/Solutions ===
This section indicates specific problems and possible solutions for the Package Websphere step.
==== Max RPM size? ====
Problem:
''Is websphere installer too large for a rpm package? This will need to be looked into.''
''place solution here''
==== 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.''
''Place patch, command, or instructions to fix installation script here.''
==== Response File ====
Problem:
''This file exists in the same directory as the installation script and must be modified with the correct responses for a successful installation.''
''Place contents of response file on wiki here.''
== 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.
198
edits

Navigation menu