WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Configuring additional settings for the Access Gateway

You can configure name space bindings, which are used to provide configuration information to the Access Gateway. Some name space bindings provide integration points to other network elements while others provide runtime configuration. Depending on the requirements of your network, you can optionally configure several additional settings for the Access Gateway.

Before you begin
To configure the optional name space bindings, you must have completed the following tasks:
About this task

Complete the following steps on the deployment manager, and synchronize the changes with all nodes.

  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password. (Omit the password if security is not enabled.)
    3. Click Log in.
  2. In the navigation pane, click Environment > Naming > Name Space Bindings.
  3. To specify a scope, select the name of a cell in the drop-down list.
  4. Optional: Create a name space binding for the attachment expiration policy:
    1. Click New.
    2. Click String for the binding type, and click Next.
    3. In the Binding Identifier field, type (or paste) Attachment_expiration_policy.
    4. In the Name in Name Space field, type sca/attachments/ExpirationPolicy.
    5. In the String Value field, specify the amount of time (in milliseconds) that a SOAP attachment should be stored in cache before it is deleted. The default value is 300000 (5 minutes).
    6. Click Next.
    7. Click Finish.
    8. Click Save to save changes to the master configuration.
  5. Optional: To use a data source other than the default associated with the database that is caching the SOAP attachment content, create a name space binding for the database attachment cache:
    1. Click New.
    2. Click String for the binding type, and click Next.
    3. In the Binding Identifier field, type (or paste) Database_attachment_cache.
    4. In the Name in Name Space field, type sca/attachments/DatabaseCache.
    5. In the String Value field, specify the JNDI name of the data source that is used to connect to the database where you are caching the SOAP attachment content. If you are using a consolidated database topology, the recommended value is jdbc/TWSSDB. If you are using a distributed database topology, the recommended value is jdbc/AGDB.
    6. Click Next.
    7. Click Finish.
    8. Click Save to save changes to the master configuration.
  6. Optional: To change the number of threads that are created to perform SOAP attachment cleanup, create a name space binding for the SOAP attachment cleanup thread count:
    1. Click New.
    2. Click String for the binding type, and click Next.
    3. In the Binding Identifier field, type (or paste) SOAP_attachment_cleanup_thread_count.
    4. In the Name in Name Space field, type sca/attachments/CleanupThreadCount.
    5. In the String Value field, specify the number of threads to be created to perform SOAP attachment cleanup. The default value is 1.
    6. Click Next.
    7. Click Finish.
    8. Click Save to save changes to the master configuration.
  7. Optional: If you plan to send or receive SOAP attachments on request or response messages, you can limit the maximum size of the total attachment size, including all attachment parts. Configure the following name space binding:
    1. Click New.
    2. Click String for the binding type, and click Next.
    3. In the Binding Identifier field, type (or paste) MaxSizeAttachments.
    4. In the Name in Name Space field, type sca/attachments/MaxSizeAttachments.
    5. In the String Value field, specify the maximum size, in bytes, of all attachment parts. The value is an integer followed by the suffix M, m, K, k, B, or b. The default value is 1M (1 megabyte).
    6. Click Next.
    7. Click Finish.
    8. Click Save to save changes to the master configuration.
  8. Optional: If you plan to send or receive SOAP attachments on request or response messages, you can limit the maximum size of any one attachment part. Configure the following name space binding:
    1. Click New.
    2. Click String for the binding type, and click Next.
    3. In the Binding Identifier field, type (or paste) MaxSizeAttachmentPart.
    4. In the Name in Name Space field, type sca/attachments/MaxSizeAttachmentPart.
    5. In the String Value field, specify the maximum size, in bytes, for any single attachment part. The value is an integer followed by the suffix M, m, K, k, B, or b. The default value is 1M (1 megabyte).
    6. Click Next.
    7. Click Finish.
    8. Click Save to save changes to the master configuration.
  9. Optional: You can enable the Access Gateway to process SOAP attachments in memory, rather than using disk I/O operations. Doing this could result in improved performance. Configure the following name space binding:
    1. Click New.
    2. Click String for the binding type, and click Next.
    3. In the Binding Identifier field, type (or paste) InMemoryProcessing.
    4. In the Name in Name Space field, type sca/attachments/InMemoryProcessing.
    5. In the String Value field, specify True to enable the Access Gateway to process SOAP attachments in memory, or False to prevent the processing of SOAP attachments in memory. The default value is True. This default value is set for you when you run the First Steps script during initial setup of IBM® WebSphere® Telecom Web Services Server.
    6. Click Next.
    7. Click Finish.
    8. Click Save to save changes to the master configuration.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.