IBM WebSphere Application Server용 DMZ 보안 프록시 서버 administration options
The IBM® WebSphere® Application Server용 DMZ 보안 프록시 서버 is administered differently than the WebSphere proxy server. The IBM WebSphere Application Server용 DMZ 보안 프록시 서버 is a separate binary installed in the DMZ. Installing the IBM WebSphere Application Server용 DMZ 보안 프록시 서버 in the DMZ requires that administration be managed differently for security reasons. Several administrative options are available for administering the IBM WebSphere Application Server용 DMZ 보안 프록시 서버 to provide different levels of balance between security and usability.
The most secure way to administer the IBM WebSphere Application Server용 DMZ 보안 프록시 서버 is locally using the wsadmin tool. The IBM WebSphere Application Server용 DMZ 보안 프록시 서버 does not have web container. Therefore, local administration can only be done via the command line. Using the wsadmin commands locally to manage the IBM WebSphere Application Server용 DMZ 보안 프록시 서버 is the most secure option available because it does not require any external listening ports to be opened.
The IBM WebSphere Application Server용 DMZ 보안 프록시 서버 configurations can also be managed within the network deployment application server 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 administrative console. After you implement any changes to the profile, you export the configuration to a configuration archive (CAR) file using the exportProxyProfile or exportProxyServer wsadmin commands. After you transmit the CAR file to the local IBM WebSphere Application Server용 DMZ 보안 프록시 서버 installation using ftp, the CAR file is imported using the importProxyProfile or importProxyServer wsadmin commands. This option is also considered to be local administration.