This chapter describes how to copy a provisioned IBM HTTP Server (IHS) 11g WebGate configuration from a test environment to a production environment. These same steps can also be used to copy a production environment to a test environment. This chapter includes the following sections:
Copying an IHS 11g WebGate configuration from a test environment to a production environment involves the following steps:
Copy the WebGate binary:
Archive the WebGate binary on the test system by using the copyBinary
command.
Transfer the archive to the production system.
Extract the archive in the production environment by using the pasteBinary
command.
Copy the WebGate configuration information:
Archive the WebGate instances on the test system using the copyConfig
command.
Transfer the archive to the production system.
(Optional.) Edit the file (moveplan.xml
) that contains the configuration settings used by the pasteConfig
command in the next step.
Extract the archive in the production environment using the pasteConfig
command.
Before continuing with the steps in this chapter, verify that you have completed the following requirements.
You must install and configure the IBM HTTP Server Web server in the production environment. The version and build numbers in the test and production environments must match.
You must copy the OAM Server configuration from the test environment to the production environment. For details, see "Moving Access Manager From a Test to Production Environment on IBM WebSphere" in the Third-Party Application Server Guide.
Verify that the transfer to production (T2P) tools are available. The tools are located here:
WebGate_Oracle_Home
/webgate/ihs/tools/WebGateT2P
The required command scripts for UNIX environments are:
copyBinary.sh
pasteBinary.sh
copyConfig.sh
pasteConfig.sh
Ensure that you have the cloningclientwg.jar
file.
Ensure that at least a version 1.6 JDK or JRE is installed.
Set the JAVA_HOME
environment variable to the location of the JDK/JRE path. For example, export JAVA_HOME=/home/software/jdk1.6.0_34
.
Note:
You can define a JAVA_HOME
environment variable on your systems and use the -javaHome
command option when you are running the test-to-production migration commands.
To copy the WebGate binary and WebGate configuration files, from a test environment to a production environment, do the following:
To replicate the WebGate binary:
In the test environment, create an archive of the binary using the copybinary.sh
command. The usage is as follows:
./copyBinary.sh [-javaHome
Java_Home_Path
] -archiveLoc
Archive_Dir
-sourceOHomeLoc
Source_WebGate_Oracle_Home
Move the archive created in the previous step to the production environment using FTP.
Also copy the WebGateT2P
directory from the Test environment to the Production environment in preparation for the next step.
In the production environment use the pastebinary.sh
command to extract the archive copied in the previous step. The usage is as follows:
./pasteBinary.sh [-javaHome
Java_Home_Path
] -archiveLoc
Archive_Dir
-targetOHomeLoc
Target_Oracle_Home_Location
To Replicate the WebGate configuration:
In the test environment, create an archive of the WebGate instance (the config) using the copyConfig.sh
command.
A file named Moveplan.xml
will be created at the archive location.
The copyConfig
command usage is as follows:
./copyConfig.sh [-javaHome
Java_Home_Path
] -archiveLoc
Archive_Dir
-sourceInstanceHomeLoc
Source_WebGate_Instance_Home
Move Moveplan.xml
and the archive created in the previous step to the production environment using FTP.
(Optional.) Open moveplan.xml
for editing and update the following parameters. These parameter are used by the pasteConfig.sh
command to configure the WebGate in the production environment.
Table 6-1 Configuration Parameters and Expected Value
Parameter Name | Expected Value |
---|---|
|
Valid OAM server name |
|
Valid OAM server proxy port |
|
WebGate Oracle home |
|
WebGate instance directory |
|
File path to the Web server config file, for example |
Set the LD_LIBRARY_PATH
and LIBPATH
environment variables on the production system before running pasteConfig.sh
.
In the production environment, run the pasteConfig.sh
command to extract the WebGate archive that you copied in step two. The pasteConfig.sh
command has two usage modes. Use the following mode if you defined the configuration parameters in the moveplan.xml
file:
./pasteConfig.sh [-javaHome
Java_Home_Path
] -archiveLoc
Archive_Location
-movePlanLoc
Path_to_the_ moveplan.xml_file
Or, to define the configuration parameters at the command line, use the following mode:
./pasteConfig.sh
[-javaHome
Java_Home_Path
] -archiveLoc
Archive_Location
-targetOHomeLoc
Target_Oracle_home_location
-targetInstanceHomeLoc
An_empty_directory
-webserverConfPath
Web_server_configuration_path
-oamHost
OAM_server_host
-oamPort
OAM_server_port