Tasks to configure the Dynamic Service Activator are:
The general properties for Dynamic Service Activator determine the behavior of the application rather than the relationship between a gateway client and the application.
To configure general properties for Dynamic Service Activator:
The client still must provide a valid client name and password, and the client name must be configured to access at least one method (for Dynamic Service Activator or PCMM) to access methods of that type. By default, gateway clients have access only to methods and scripts that you specify in the configuration. Access control should be disabled only for troubleshooting purposes.
You configure which types of information identify subscribers to the SAE. The subscriber types that you can configure are the same subscriber types that you can use in applications created with the SAE CORBA remote API.
To configure subscriber types:
Type a name for the new configuration in the dialog box, and click OK.
The configuration appears in the side pane.
You create a NIC proxy for each subscriber type to be configured. The name of the NIC proxy must match the name configured for the NIC proxy namespace.
Subscriber types that have different subscriber ID types can use the same NIC proxy. For example, a subscriber type configured as SubscriberType1 that has a subscriber ID type of interface-name, and a subscriber type configured as subscriberType2 that has a subscriber ID type of interface-index can both use the same NIC proxy. Likewise, a subscriber type configured as SubscriberType1 and a subscriber type configured as subscriberType2 that both have a subscriber ID type of address can use the same NIC proxy.
To configure NIC proxies:
Type a name for the new configuration in the dialog box, and click OK.
The configuration appears in the side pane.
Configuring access to methods and scripts involves adding methods, scripts, and clients to the configuration and configuring access properties between each client and each method or script.
![]() |
Note: Client profiles are cached by Dynamic Service Activator for 30 minutes. If you change the password or role of a client that has been used within the last 30 minutes, it can take up to 30 minutes before these changes take effect. When permissions are configured, roles are assigned to application server user objects automatically. The first time you add a method or script for a client, the DSA role is added to the corresponding application server user; and when the last method or script is deleted, the DSA role is removed from the corresponding user. Only role and password changes take up to 30 minutes to take effect. If you do not want to wait 30 minutes for the changes to take effect, restart the Web application server. |
Dynamic Service Activator interacts with the Web application server to determine whether a gateway client has access to a method or script. The name and credentials, such as a password, that are used to authenticate the gateway client are configured on the Web application server as user accounts.
Access constraints are regular expressions that the arguments for the method or script in the SOAP request must match. If the arguments for the method or script in a particular SOAP request do not match these regular expressions, then Dynamic Service Activator rejects the request.
To configure methods for Dynamic Service Activator:
To configure access to methods for Dynamic Service Activator:
Type a name for the new configuration in the dialog box, and click OK. You must use the same name for the gateway client that is configured on the Web application server.
The configuration appears in the side pane.
To configure scripts for Dynamic Service Activator:
Type a name for the new configuration in the dialog box, and click OK. Use the text string that exactly matches the name of the script.
The configuration appears in the side pane.
To configure access to scripts:
Type a name for the new configuration in the dialog box, and click OK. You must use the same name for the gateway client that is configured on the Web application server.
The configuration appears in the side pane.
Type a name for the new configuration in the dialog box, and click OK. Use the text string that exactly matches the name of the script.
The configuration appears in the side pane.
To modify logging destinations to store log messages in a file:
To create logging destinations to store log messages in a file:
The logger appears in the side pane.
To modify logging destinations to send log messages to the system logging facility:
To create logging destinations to send log messages to the system logging facility:
The logger appears in the side pane.