Difference between revisions of "OSTEP Websphere"
| Line 9: | Line 9: | ||
= Package Websphere = | = 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. | 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. | ||
| + | |||
| + | == Who is working on this? == | ||
| + | place name here | ||
== Current Progress == | == Current Progress == | ||
| Line 18: | Line 21: | ||
=== Max RPM size? === | === Max RPM size? === | ||
Problem: | Problem: | ||
| − | + | <pre> | |
| + | Is websphere installer too large for a rpm package? This will need to be looked into. | ||
| + | </pre> | ||
Solution: | Solution: | ||
| − | + | <pre> | |
| + | place solution here | ||
| + | </pre> | ||
=== Installation Script on Centos === | === Installation Script on Centos === | ||
Problem: | 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: | Solution: | ||
| − | + | <pre> | |
| + | Place patch, command, or instructions to fix installation script here. | ||
| + | </pre> | ||
=== Response File === | === Response File === | ||
Problem: | 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: | Solution: | ||
| − | + | <pre> | |
| + | Place contents of response file on wiki here. | ||
| + | </pre> | ||
= Package Websphere Fixpacks = | = 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. | 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. | ||
| + | |||
| + | == Who is working on this? == | ||
| + | place name here | ||
== Current Progress == | == Current Progress == | ||
| Line 45: | Line 63: | ||
=== Installation Script on Centos === | === Installation Script on Centos === | ||
Problem: | 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: | Solution: | ||
| − | + | <pre> | |
| + | Place patch, command, or instructions to fix installation script here. | ||
| + | </pre> | ||
=== Response File === | === Response File === | ||
Problem: | 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: | Solution: | ||
| − | + | <pre> | |
| + | Place contents of response file on wiki here. | ||
| + | </pre> | ||
= Package Nexj Plugins = | = 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. | 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. | ||
| + | |||
| + | == Who is working on this? == | ||
| + | place name here | ||
| + | |||
| + | == Current Progress == | ||
| + | No progress has been made yet | ||
| + | |||
| + | == Known Problems/Solutions == | ||
| + | This section indicates specific problems and possible solutions for packaging Nexj Plugins | ||
| + | |||
| + | = Script to Automate Websphere Fix Pack 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. | ||
| + | |||
| + | == Who is working on this? == | ||
| + | place name here | ||
| + | |||
| + | == 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. | ||
| + | |||
| + | == Who is working on this? == | ||
| + | place name here | ||
| + | |||
| + | == 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. | ||
| + | |||
| + | == Who is working on this? == | ||
| + | place name here | ||
== Current Progress == | == Current Progress == | ||
| Line 62: | Line 127: | ||
== Known Problems/Solutions == | == Known Problems/Solutions == | ||
| − | This section indicates specific problems and possible solutions for | + | This section indicates specific problems and possible solutions for the Websphere Single Node Configuration |
Revision as of 16:49, 27 October 2014
Contents
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.
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.
Who is working on this?
place name here
Current Progress
No progress has been made yet
Known Problems/Solutions
This section indicates specific problems and possible solutions for the packaging Websphere application.
Max RPM size?
Problem:
Is websphere installer too large for a rpm package? This will need to be looked into.
Solution:
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.
Solution:
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.
Solution:
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. 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.
Who is working on this?
place name here
Current Progress
No progress has been made yet
Known Problems/Solutions
This section indicates specific problems and possible solutions for the Packaging Websphere Fix Packs
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:
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.
Solution:
Place contents of response file on wiki here.
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.
Who is working on this?
place name here
Current Progress
No progress has been made yet
Known Problems/Solutions
This section indicates specific problems and possible solutions for packaging Nexj Plugins
Script to Automate Websphere Fix Pack 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.
Who is working on this?
place name here
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.
Who is working on this?
place name here
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.
Who is working on this?
place name here
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
