Before using this information, be sure to read the general information under Appendix A. Notices.
Your feedback is important in helping to provide the most accurate and highest quality information.
Be sure to include the document name and number, the WebSphere Application Server version that you are using, and (if applicable) the specific page, table, or figure number on which you are commenting.
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
Run the Feature Pack for Service Component Architecture (SCA) installation program to install the feature pack on an existing installation of a WebSphere® Application Server Version 7.0 product. The Feature Pack for Service Component Architecture is an optionally installable product extension for WebSphere Application Server that delivers an integrated, open implementation of SCA technology specified by IBM and other industry leaders through the Open SOA Collaboration.
Before starting this installation, do the following:
For example, create two directories, sca_download and sca_installation_image. Download the feature pack to the sca_download directory and then extract the downloaded file to the sca_installation_image directory. Do not move any files from the sca_installation_image directory.
This topic describes how to install the SCA feature pack using the installation wizard. To install the feature pack silently, read the Installing Feature Pack for SCA silently topic.
The installation program installs the following program files if they are not already installed:
Consider your current product topography before installing the feature pack because it installs maintenance packages that may affect the version of your application server product. If the application server is already at or above the levels of maintenance included with the feature pack, then the installation of these maintenance packages is skipped.
Run the ls -al command at the root of the application server installation to find the user ID that was used to install the product.
Stop the application server and any other product processes. For example, for the Network Deployment product, stop the deployment manager, the node agent, and all application server processes.
Run the installation executable from the command line in the SCA directory:
Keep the Launch the Profile management tool console default selection.
The installation wizard installs the feature pack and records installation events in the installation log files, which are located in the app_server_root/logs/sca/install directory.
Troubleshooting
Examine messages that the installation program displays. If the feature pack does not install successfully, read the messages to identify why the installation failed. Correct the problems identified and try installing the product again.
./install -is:javaconsole
install.exe -is:javaconsole
To use the feature pack functionality, you must create a new profile with the feature pack functionality or augment an existing profile with the feature pack.
Create a new profile
Create a new profile to use the feature pack functionality. Follow these steps to create a profile using the Profile Management tool:
After you create the profile, start the server and open the administrative console for the application server.
Augment an existing profile
You can run the manageProfiles command or the Profile Management tool to augment a profile. For example, to augment an application server profile with SCA functionality using the manageProfiles, open a command prompt in the app_server_root/bin directory, enter the following command to augment the AppSrv01 profile:
manageProfiles -augment -profileName AppSrv01 -templatePath app_server_root/profileTemplates/SCA/default.scafep
After you augment the profile, start the server and open the administrative console for the application server.
Network Deployment
If you installed the feature pack on top of a Network Deployment product, do the following after you create or augment the profiles:
Read the profile topics for more information.
Run the Feature Pack for Service Component Architecture (SCA) installation program to silently install the feature pack on an existing installation of a WebSphere Application Server Version 7.0 product. The Feature Pack for Service Component Architecture is an optionally installable product extension for WebSphere Application Server that delivers an integrated, open implementation of SCA technology specified by IBM and other industry leaders through the Open SOA Collaboration.
Before starting this installation, do the following:
For example, create two directories, sca_download and sca_installation_image. Download the feature pack to the sca_download directory and then extract the downloaded file to the sca_installation_image directory. Do not move any files from the sca_installation_image directory.
This topic describes how to install the feature pack silently. To install the feature pack using the installation wizard, read the Installing Feature Pack for SCA on distributed operating systems topic.
The installation program installs the following program files if they are not already installed:
Consider your current product topography before installing the feature pack because it installs maintenance packages that may affect the version of your application server product. If the application server is already at or above the levels of maintenance included with the feature pack, then the installation of these maintenance packages is skipped.
Run the ls -al command at the root of the application server installation to find the user ID that was used to install the product.
Set values for the following options:
Option | Description |
---|---|
-OPT silentInstallLicenseAcceptance="true" |
You must accept the enclosed license agreement to install the feature pack. |
-OPT allowNonRootSilentInstall="true" |
You must uncomment this line if you are installing the product with a non-root or non-administrator ID. |
-OPT installLocation=app_server_root |
Set app_server_root to the root directory of your application server product. |
-OPT checkFilePermissions="true" |
Uncomment this option if you want the feature pack installer to verify whether the current user has permission to write to the specified directories and files. |
-OPT disableNonBlockingPrereqChecking="true" |
Uncomment this option in order to install application server and SDK fix packs, if they are required. The installer will fail if you have not uncommented this option and your application server still requires the fix packs bundled with the feature pack. Uncomment this line to notify the installer to continue with the installation and log the warnings even though prerequisite checking failed. |
For example, for the Network Deployment product, stop all application server processes, the node agent, and the deployment manager.
Run the install executable file in the root directory of the feature pack installation image and point to the Java Virtual Machine (JVM) already included with the application server, where app_server_root is the root directory of your existing application server product: At a command prompt in the root directory of the installation image, enter the following command:
The installation program runs silently in the background.
The installation program records installation events in the installation log files and installs the feature pack.
After the program runs, examine the logs in app_server_root/logs/sca/install directory. If the feature pack does not install successfully, correct the problems identified in the logs and install the product again.
If the product installs successfully, to use the feature pack functionality, create a new profile using the Profile Management tool or the manageprofiles command. Read the profile topics for more information.
Uninstall the feature pack product files, leaving the application server product intact.
The uninstall command calls the uninstaller program that is created during installation. The uninstaller program is customized for each product installation, with specific disk locations and routines for removing installed features.
Uninstall any feature packs first before you uninstall the application server. If you have a feature pack installed, uninstalling the WebSphere Application Server product using the uninstaller program causes the feature pack to fail. However, you should still uninstall the feature pack after uninstalling the application server to remove all feature pack product entries and artifacts which might prevent a successful reinstallation. See Troubleshooting for more information.
Uninstallation unaugments application server profiles that were previously augmented for the feature pack, rendering them unusable.
Log on using the same user ID that
was used when the product was installed or as a user that has write
permissions to the installation directory. Issue the ls -al command
at the root of the WebSphere Application Server installation to find
the user ID that was used to install the product.
Log on as a user who belongs to the administrators
group or as a user who has write permissions to the installation directory.
Stop the node agent process that might be running on the machine. For example, issue the following command from the profile_root/bin directory of a federated node on a Linux workstation to stop the node agent process:
./stopNode.sh
If servers are running and security is enabled, then use the following command:
./stopNode.sh -user user_ID -password password
For example, issue the following command on a Linux workstation from the profile_root/bin directory of the deployment manager profile:
./stopManager.sh -user user_ID -password password
Stop
all server processes in all profiles associated with the target product
instance. You do not have to stop processes related to other instances
of the product on your machine. For example, issue the following command
from the profile_root/bin directory
to stop the server1 process in the application server profile:
./stopServer.sh server1
./stopServer server1
If a server
is running and security is enabled, use the following command:
./stopServer.sh server1 -user user_ID -password password
./stopServer server1 -user user_ID -password password
If you have multiple servers,
you can use the serverStatus command to find running
application servers associated with the target product instance. Issue
the following command from the profile_root/bin directory
to determine which servers, if any, are running:
./serverStatus.sh -all
./serverStatus -all
Use the backupConfig command to back up configuration files and profiles. Read the "backupConfig command" topic for more information.
The uninstallation wizard begins and displays the Welcome panel.
You can also uninstall silently by running the uninstall command with the silent parameter:
uninstall -silent
The uninstaller wizard displays a confirmation panel that lists a summary of the components that you are uninstalling.
This procedure results in uninstalling the feature pack product.
Troubleshooting
Uninstalling the application server before uninstalling
the feature pack might result in the failure of configuration actions
that are responsible for removing Linux shortcuts. Uninstall any feature
pack installations first before uninstalling the application server
to ensure that both products are uninstalled cleanly. If you have
already uninstalled the application server, then run the feature pack
uninstaller to clean up the feature pack installation and to remove
any product registry entries. You can ignore the failed configuration
actions from the application server uninstallation process. However,
manually remove the entire application server directory afterwards.
Install the feature pack directly from your IBM® i operating system onto an existing Version 7.0 application server. The Feature Pack for Service Component Architecture is an optionally installable product extension for WebSphere Application Server that delivers an integrated, open implementation of SCA technology specified by IBM and other industry leaders through the Open SOA Collaboration.
Before starting this installation, complete the following actions:
For example, create two directories, sca_download and sca_installation_image. Then, download the feature pack to the sca_download directory and then extract the downloaded file to the sca_installation_image directory. Do not move any files out of the sca_installation_image directory.
This topic describes how to install the Feature Pack for SCA silently using the installation program. You can install the feature pack from Qshell using the INSTALL command. You can also use the RUNJVA command to invoke the installation wizard.
Set values for the following options where app_server_root is the directory path to your WebSphere Application Server installation:
Option | Description |
---|---|
-OPT silentInstallLicenseAcceptance="true" |
You must accept the enclosed license agreement to install the feature pack. |
-OPT installLocation=app_server_root |
Set app_server_root to the root directory of your application server product. |
Stop the application server and any other product processes. For example, for the Network Deployment product, stop the deployment manager, the node agent, and all application server processes.
The host server jobs allow the installation code to run on IBM i. On a CL command line, enter the following command:
STRHOSTSVR SERVER(*ALL)
Run the INSTALL command from Qshell or use the RUNJVA command from the CL command line.
In the following example commands, path/responsefile represents the fully qualified path of the response file that you edited:
install -options path/responsefile
At the CL command line, enter the RUNJVA command in the root directory of the extracted installation image. Enter the full command on one line. The command is shown here on multiple lines for formatting clarity:
RUNJVA CLASS(run) PARM('-options' 'path/responsefile') CLASSPATH('path/setup.jar') PROP( ('Xbootclasspath/p' 'java/endorsed/xml.jar') (java.version 1.5) (is.debug 1) )
The installation program records events in the log files located in the app_server_root/logs/sca/install directory.
If the product installs successfully, to use the feature pack functionality, create a new profile using the Profile Management tool or the manageprofiles command. Read the profile topics for more information.
Applying maintenance
Use the Update Installer to install maintenance packages for any of the installable WebSphere software components in the product package. Read the Installing maintenance packages topic for more information.
You can uninstall a feature pack product by running the feature pack uninstall command from your IBM i server.
The uninstall command calls the uninstaller program that is created during installation. The uninstaller program is customized for each product installation, with specific disk locations and routines for removing installed features.
Uninstall any feature packs first before you uninstall the application server. If you have a feature pack installed, then uninstalling the WebSphere Application Server product using the uninstaller program causes the feature pack to stop working. However, you should still uninstall the feature pack after uninstalling the application server to remove all feature pack product entries and artifacts which might prevent a successful reinstallation. See Troubleshooting for more information. This same limitation applies if you are uninstalling a customized installation package (CIP) created with IBM WebSphere Installation Factory.
Use this procedure to uninstall a feature pack from a WebSphere Application Server for IBM i installation.
Stop the application server and any other product processes. For example, for the Network Deployment product, stop the deployment manager, the node agent, and all application server processes.
The host server jobs allow the installation code to run on IBM i. On a CL command line, enter the following command:
STRHOSTSVR SERVER(*ALL)
To uninstall the feature pack, run the following command from the Qshell command line in the app_server_root/uninstall_sca directory:
uninstall -silent
After completing the procedure, the feature pack is uninstalled. Uninstalling the feature pack from the IBM i server removes feature pack libraries and directories.
If the feature pack does not uninstall successfully, examine the logs in the app_server_root/logs/sca/uninstall directory to identify why the uninstallation failed. Correct the problems identified and try uninstalling the product again.
You can use the System Modification Program / Extended (SMP/E) to install the Feature Pack for SCA on WebSphere Application Server for z/OS Version 7.0 .
The Feature Pack for Service Component Architecture (SCA) is an optionally installable product extension for WebSphere Application Server that delivers an integrated, open implementation of SCA technology specified by IBM and other industry leaders through the Open SOA Collaboration. Quality-of-service capabilities such as transactions and security, and ease-of-use features, such as policy-set definitions for Web Services are available with the feature pack. This integration ensures that all of WebSphere's capabilities work together with SCA applications to provide a natural environment for both the SCA and existing applications.
Before starting this installation, perform the following actions:
The Feature Pack for SCA is included as service with the WebSphere Application Server for z/OS optional materials.
This PTF includes JCL to allocate and initialize a file system to hold the Feature Pack for SCA product code. Follow the instructions contained in this PTF to create the Feature Pack for SCA file system.
This PTF contains the Feature Pack for SCA product code, which is installed into a subdirectory of the Optional Materials directory.
When you have finished the installation, you can create a WebSphere Application Server on z/OS runtime environment that includes Feature Pack for SCA functions. To use the feature pack functionality, you must create a new profile with the feature pack functionality or augment an existing profile with the feature pack.
Use the workstation-based Profile Management Tool, which can be launched from the WebSphere Customization Tools, to generate customization jobs and associated instructions for Feature Pack for SCA profile creation and augmentation.
You can create a standalone application server that is enabled for this feature pack, or you can enable an existing application server with this feature pack using profile augmentation. Creating a standalone application server is the usual approach; if you are enabling both the Feature Pack for SCA and another feature pack on the same application server, however, you would use the enabling procedure. In the second case, you create a standalone application server that is enabled for one feature pack and then immediately enable the other feature pack on that application server.
To use the Feature Pack for SCA in a Network Deployment cell, you can create a deployment manager that is enabled for the Feature Pack for SCA or enable the deployment manager in an existing Network Deployment cell for the feature pack. Unlike standalone application servers, deployment managers can be augmented with a feature pack at any time, not just immediately after creation.
Profile augmentation depends on the type of profile, whether you changed the configuration information, and so on. You must have the correct combination of feature packs in order to add a node, manage clusters, install applications, and manage server templates. Use these rules and limitations to ensure a properly functioning feature pack environment.
To use the functionality provided in the Feature Pack for SCA, you must either augment existing profiles or create new profiles enabled with feature-pack functionality. Profile creation and augmentation are done using the customization jobs and the associated instructions created by the Profile Management Tool.
You can have a mix of augmented and unaugmented profiles that share a single WebSphere Application Server installation. Feature-pack functionality is available only within profiles that have been augmented.
The following table provides additional augmentation rules for particular types of profiles.
Profile | Supported | Not supported |
---|---|---|
Application server |
|
Augmentation of an existing federated application server profile |
Deployment manager |
|
Augmentation of an existing deployment manager if the version of any federated node in the cell is lower than Version 7.0 |
Managed (custom) node |
|
|
Network Deployment cell |
|
|
Administrative agent | Creation or augmentation of an administrative
agent to enable it for a feature pack
However, you can use an administrative agent in a feature-pack environment. |
|
Job manager | Creation or augmentation of a job manager
to enable it for a feature pack
However, you can use a job manager in a feature-pack environment. |
|
Secure proxy server | Creation or augmentation of a secure proxy
server to enable it for a feature pack
However, you can use a secure proxy server in a feature-pack environment. |
|
Secure proxy administrative agent | Creation or augmentation of a secure proxy
administrative agent to enable it for a feature pack
However, you can use a secure proxy administrative agent in a feature-pack environment. |
When you perform tasks between nodes or between nodes and the deployment manager, the feature packs must be compatible.
Function | Rules |
---|---|
Addition of a node |
|
Application installation |
|
Server configuration template use |
|
Cluster management |
|
Configuration-archive export and import |
|
You cannot unaugment profiles that have been enabled with feature-pack functionality in WebSphere Application Server for z/OS Version 7.0.
Maintenance for the WebSphere Application Server optional materials is similar to that for the base WebSphere Application Server for z/OS product. Maintenance is applied using the System Modification Program / Extended (SMP/E), and then it is moved into production. The optional materials include feature packs and other interim deliverables.
In general, feature-pack maintenance levels for WebSphere Application Server Version 7.0 are closely linked to base WebSphere Application Server maintenance levels. On distributed platforms, feature-pack maintenance is applied automatically when base maintenance is installed. On z/OS systems, customers are responsible for upgrading feature-pack levels whenever base service levels are upgraded. If the WebSphere Application Server base service level is higher than the feature-pack service level, feature-pack enabled servers do not start.
The WebSphere Application Server for z/OS service support Web site provides program temporary fix (PTF) lists for the base WebSphere Application Server for z/OS product and for each feature pack or other interim deliverable. The general rule is that each feature-pack level runs correctly with the base WebSphere Application Server product at the same level or one level higher. Therefore, feature-pack Version 7.0.0.13 will run with base WebSphere Application Server Version 7.0.0.13 or Version 7.0.0.14. If you upgrade the base product code to Version 7.0.0.15, you also need to install a new level of feature-pack Version 7.0.0.15.
Contact the IBM Software Support Center or consult the WebSphere Application Server for z/OS service support Web site to determine the PTFs for the required feature pack or interim deliverable maintenance levels, and order or download these PTFs.
The base product and the optional materials can be applied using either a single APPLY command in SMP/E or separate APPLY commands.
When the post-installer runs for each node, it makes any necessary configuration file system changes for both the base WebSphere Application Server product and any feature packs enabled on the node. The applyPTF.sh command output will contain a log of all changes made.
The WebSphere Application Server for z/OS nodes that are upgraded to the new service level are now running with compatible WebSphere Application Server for z/OS and optional-materials maintenance.
Restarting a WebSphere Application Server for z/OS node at a previous service level normally involves simply switching the runtime to use the previous level of code (datasets and product file system); the post-installer checks that any configuration changes made since the old level are backwards compatible.
New service levels that are not backwards compatible have this fact flagged in an ACTION HOLD statement for the service PTFs; customers who need to restart at the earlier service level will need to run the backoutPTF.sh command. To back out configuration changes for feature packs or other optional materials, specify the feature-pack identifier (rather than "WebSphere") in the backoutPTF.sh command:
backoutPTF.sh SCA target_service_level
References in product information to app_server_root, profile_root, and other directories infer specific default directory locations. This topic describes the conventions in use for WebSphere Application Server.
The node may be of any type--application server, deployment manager, or unmanaged for example. Each node has its own app_server_root. Corresponding product variables are was.install.root and WAS_HOME.
The default varies based on node type. Common defaults are configuration_root/AppServer and configuration_root/DeploymentManager.
The configuration_root contains the various app_server_root directories and certain symbolic links associated with them. Each different node type under the configuration_root requires its own cataloged procedures under z/OS.
The default is /wasv7config/cell_name/node_name.
Corresponding product variables are server.root and user.install.root.
In general, this is the same as app_server_root/profiles/profile_name. On z/OS, this will be always be app_server_root/profiles/default because only the profile name "default" is used in WebSphere Application Server for z/OS.
The corresponding product variable is smpe.install.root.
The default is /usr/lpp/zWebSphere/V7R0.
These file paths are default locations. You can install the product and other components in any directory where you have write access. You can create profiles in any valid directory where you have write access. Multiple installations of WebSphere Application Server products or components require multiple locations.
A CIP is a WebSphere Application Server Network Deployment product bundled with optional maintenance packages, an optional configuration archive, one or more optional enterprise archive files, and other optional files and scripts.
JVM | Directory |
---|---|
Classic JVM | /QIBM/ProdData/Java400/jdk6 |
32-bit IBM Technology for Java | /QOpenSys/QIBM/ProdData/JavaVM/jdk60/32bit |
64-bit IBM Technology for Java | /QOpenSys/QIBM/ProdData/JavaVM/jdk60/64bit |
The profiles and profileRegistry subdirectories are created under this directory when you install the product.
The following file paths are default locations. You can install the product and other components or create profiles in any directory where you have write access. Multiple installations of WebSphere Application Server Network Deployment products or components require multiple locations. Default values for installation actions by root and non-root users are given. If no non-root values are specified, then the default directory values are applicable to both root and non-root users.
User | Directory |
---|---|
Root |
|
Non-root |
|
User | Directory |
---|---|
Root |
|
Non-root |
|
User | Directory |
---|---|
Root |
|
Non-root |
|
product_root/gsk7
product_root\gsk7
User | Directory |
---|---|
Root |
|
Non-root |
|
User | Directory |
---|---|
Root |
|
Non-root |
|
User | Directory |
---|---|
Root |
|
Non-root |
|
User | Directory |
---|---|
Root |
|
Non-root |
|
References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility.
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the following address:
For trademark attribution, visit the IBM Terms of Use Web site (http://www.ibm.com/legal/us/).