Isolating Running Web Applications from Productive Client Requests 

Use

You can isolate one or more of the Web applications running on the J2EE Engine from being reachable for requests of productive clients while the applications are still running. You would most probably need that function to perform application support activities (such as debugging on a productive system).

The above behavior is controlled by the ApplicationStoppedAliases property of the Web Container Service. If you add the application alias of an application to the value of this property, the customers that request the application will get a response that the application is stopped (either a standard one, or a custom one if you have configured the ApplicationStoppedFile property of the Web Container Service). However, the application is not stopped practically, and can be accessed, for example, using an application zone.

You can also specify a complex alias (that is, the <application alias + zone separator + zone name>) as a value of the ApplicationStoppedAliases property to isolate requests to applications running within zones.

Procedure

To complete this task use the Visual Administrator tool:

...

       1.      Open the Properties tab of the Web Container Service.

       2.      Find the ApplicationStoppedAliases property and enter the list of application aliases that you want to restrict access to. Use a comma (,) to separate the entries in the list.

       3.      To add the new value to the list of properties, choose Update.

       4.      To make your changes permanent, choose  (Save Properties).