DMZ Secure Proxy Server for IBM WAS administration options
The DMZ Secure Proxy Server for IBM WAS is administered differently than the WebSphere proxy server. The DMZ Secure Proxy Server for IBM WAS is a separate binary installed in the DMZ. Installing the DMZ Secure Proxy Server for IBM WAS in the DMZ requires that administration be managed differently for security reasons. Several admin options are available for administering the DMZ Secure Proxy Server for IBM WAS to provide different levels of balance between security and usability.
The most secure way to administer the DMZ Secure Proxy Server for IBM WAS is locally using wsadmin. The DMZ Secure Proxy Server for IBM WAS does not have web container therefore local administration can only be done via the command line. Using the wsadmin commands locally to manage the DMZ Secure Proxy Server for IBM WAS is the most secure option available because it does not require any external listening ports to be opened.
The DMZ Secure Proxy Server for IBM WAS configurations can also be managed within the network deployment appserver cell and then imported locally using the wsadmin commands. The configurations are maintained inside the cell as configuration only profiles. The profiles are registered with the Admin Agent and are then managed using the admin console. After you implement any changes to the profile, you export the configuration to an configuration archive (CAR) file using exportProxyProfile or exportProxyServer wsadmin commands. After you transmit the CAR file to the local DMZ Secure Proxy Server for IBM WAS installation using ftp, the CAR file is imported using importProxyProfile or importProxyServer wsadmin commands. This option is also considered to be local administration.
The DMZ Secure Proxy Server for IBM WAS can be managed remotely from the Job Manager console. We can create, delete, start, stop and modify the DMZ Secure Proxy Server for IBM WAS configuration using the Job Manager console. However, typically before managing the DMZ Secure Proxy Server for IBM WAS using the Job Manager console, the DMZ Secure Proxy Server for IBM WASs would be created and configured using one of the other admin options explained above. Using the Job Manager console is useful for centrally managing multipleDMZ Secure Proxy Server for IBM WASs but is less secure than the other options because it requires the SOAP connector listener port to be opened for communication with the Job Manager console.
Related concepts
WebSphere DMZ Secure Proxy Server for IBM WAS
DMZ Secure Proxy Server for IBM WAS start up user permissions
DMZ Secure Proxy Server for IBM WAS routing considerations
Error handling security considerations for the DMZ Secure Proxy Server for IBM WAS
Administrative agent
Job manager
Related tasks
Administer jobs in a flexible management environment using scripting
Tuning the security properties for the DMZ Secure Proxy Server for IBM WAS
Related
ConfigArchiveOperations
ProxyManagement