Set a DMZ Secure Proxy Server for IBM WAS using the admin console

Set a DMZ Secure Proxy Server for IBM WAS using the admin console

We can create a DMZ Secure Proxy Server for IBM WAS inside of a network deployment cell using the admin console of an administrative agent. We can then export the secure proxy server to a node in the DMZ into which we can then import the configuration. After the secure proxy server is created on a node in the DMZ, administration can be done locally or it can be done using the Job Manager console.
Before beginning, complete these tasks.

Install the DMZ Secure Proxy Server for IBM WAS code.
See the Installing the DMZ Secure Proxy Server for IBM WAS image topic for more details.
Create a secure proxy server (configuration-only) profile on a network-deployment installation using either the Profile Management Tool or the manageprofiles command.
See Create a secure proxy profile for more information on creating the profile using the Profile Management Tool.
Create an administrative agent profile on the network-deployment installation using either the Profile Management Tool or the manageprofiles command.
See Create a management profile with an administrative agent for additional details.

The DMZ Secure Proxy Server for IBM WAS does not contain a web container and therefore does not have an admin console. Secure proxy server configurations can also be managed within a network deployment appserver cell and then imported locally into the DMZ Secure Proxy Server for IBM WAS using wsadmin commands. The configurations are created and maintained inside the network deployment appserver cell as configuration-only profiles. The profiles are registered with the administrative agent and are then managed using the admin console. You configure the secure proxy server profile in the network deployment application server cell, export the configuration to a configuration archive (CAR) file using exportProxyProfile or exportProxyServer wsadmin command, transmit the CAR file to the local secure proxy server installation using FTP, and import the configuration into the DMZ Secure Proxy Server for IBM WAS using the importProxyProfile or importProxyServer wsadmin command. You then repeat the process if any changes are made to the secure proxy server configuration.

Start an administrative agent on a network-deployment installation.
Register the secure proxy (configuration-only) profile with the administrative agent using the registerNode command.
Restart the administrative agent.
When the administrative agent prompts you with a list of the nodes that it manges, select the node from the secure proxy (configuration-only) profile.
From the admin console of the administrative agent, select Servers > Server Types > WebSphere proxy servers.
Click New to access the Proxy Server Creation wizard.
Select the DMZ Secure Proxy Server for IBM WAS node.
Complete the steps in the wizard to create a new secure proxy server.
This new secure proxy server will only be used as a configuration. It cannot be started inside of the cell.
Save the configuration.
Use wsadmin, connect to the secure proxy server profile.
See Starting the wsadmin scripting client for more information.
Export the configuration to be used inside of the DMZ; we can export the entire profile or export the server.

To export the profile, run the exportProxyProfile command. For example:
AdminTask.exportProxyProfile (['-archive', 'c:\]myCell.car'])

To export the server, run the exportProxyServer command. For example:
AdminTask.exportProxyServer ('[-archive c:\myServer.ear -nodeName node1 -serverName proxy1]')

Use FTP, transfer the configuration archive to the local secure proxy server node.
Start wsadmin on the secure proxy server profile.
Import the entire profile, or import the server.

Use the importProxyProfile command to import the profile. For example:
AdminTask.importProxyProfile(['-archive', '/myCell.car'])

Use the importProxyServer command to import the server. For example:
AdminTask.importProxyServer('[-archive /myServer.ear -nodeInArchive node1 -serverInArchive proxy1]')

Save the configuration changes...
AdminConfig.save()

Results
Successful completion of this procedure results in deployment of the DMZ Secure Proxy Server for IBM WAS on a node in the DMZ.

Next steps
We can now start and begin to use the DMZ Secure Proxy Server for IBM WAS.

Set secure routing for a DMZ Secure Proxy Server for IBM WAS

Related concepts

WebSphere DMZ Secure Proxy Server for IBM WAS

Related tasks

Create a management profile with an administrative agent
Create a secure proxy profile
DMZ Secure Proxy Server for IBM WAS administration options
Administer nodes using the administrative agent
Administer nodes using the job manager
Set up the proxy server

Related

startServer