WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

7. Create an application server profile using the
/profileTemplates/management profile template and specify
-serverType as ADMIN_AGENT to create the administrative agent profile.
8. Create an Application Server Profile using the
/profileTemplates/secureproxy template.
Note: The profiles for the administrative agent and the DMZ secure proxy
are for administration purposes only. The DMZ secure proxy server is a
configuration-only profile. This means that the server cannot be started or
used for any work. This server is an administrative place-holder for the
DMZ secure proxy server on System A. If you try to start the
configuration-only profile, it will fail with the following error message in the
SystemOut.log:
Caused by:
com.ibm.ws.proxy.deployment.ProxyServerDisabledException: This
secure proxy server is part of a configuration-only installation
and cannot be started.
Tip: It is recommended to name the proxy server and the node name in the
configuration-only profile on System C the same as you did when creating
the proxy server on System A using parameters: -serverName and
-nodeName when running manageprofiles.
9. Register the DMZ secure proxy configuration-only profile to the Administrative
agent.
10.Use the Integrated Solutions Console from the administrative agent to
manage the DMZ secure proxy configuration-only template.
11.Export the configuration-only DMZ secure proxy to move the changes over to
the real DMZ secure proxy. You need to perform the following steps:
a. Go to the /bin directory of the configuration-only DMZ
secure proxy profile.
b. Start wsadmin -lang jython -conntype NONE.
c. Run the command shown in Example 5-2 to export the proxy profile.
Example 5-2 Sample code to export proxy profile
AdminTask.exportProxyProfile('[-archive
/DMZProxy.car]'
12.Copy the file /DMZProxy.car to System A.
Chapter 5. Topologies 159