Configuring the Outbound Adapter Configuration

The outbound adapter configuration does not need additional configuration in TIBCO Business Studio to be able to respond to dynamic changes to the application server environment.

The following properties need to be set in the adapter launcher file to enable this feature for an outbound adapter configuration.
  • adr3.discovery

    Use this property to turn on or off the dynamic discovery feature.

    The feature is commented by default. To turn it on, uncomment the property.

  • adr3.discovery.pid

    Use this property to specify program IDs on which to register the gateway of the discovered application server.

    If the dynamic discovery feature is turned on, this is a mandatory property. The adapter configuration exit on starting up with an appropriate error if this property is not specified.

    You can specify multiple program IDs as comma-separated values.

    For example:

    adr3.discovery.pid=tibcotest

    adr3.discovery.pid=tibcotest,IDoctest

    Note: Discovery Agent: The outbound adapter log does not give any error when it establishes a connection to a program ID sent by the discovery message, and this program ID does not exist in the SAP System.
  • adr3.discovery.listenerSubject

    Use this property to specify the subject to listen on to subscribe to the discovery message published by the Discovery Agent. The discovery message contains the list of active application servers. Ensure that the adr3.discovery.listenerSubject property matches the publishing subject on the Discovery Agent side.

    For example:

    adr3.discovery.listenerSubject=APPSERVER.DISCOVERY.DYNAMIC

    If not specified, this property defaults to R3.APPSERVERS.ACTIVE.

  • adr3.discovery.listenerSession

    Use this property to specify the TIBCO Rendezvous or JMS session to use for the discovery listener.

    A valid session by this name should be available in the project.

    For example:

    adr3.discovery.listenerSession=MyDiscoverySession

    If not specified, this property defaults to R3RVSession.

  • adr3.discovery.maxconnections

    Use this property to specify the maximum number of connections that can be established to the gateway of each discovered application server.

    If not specified, it defaults to 1.

  • adr3.discovery.maxretryinterval

    Use this property to specify the maximum number for the retry interval.

    This property defines the behavior of the outbound adapter in the event of connection to the SAP Gateway server. Connection loss can result from network glitches or a planned shutdown. Because the adapter cannot distinguish between the two causes, it can behave in exactly the same way in both situations.

    If an SAP Gateway server has been brought down because of a planned shutdown, it will still continue to establish a valid connection until the maximum retry interval is reached.

    For example:

    adr3.discovery.maxretryinterval=120

    Note that the maximum retry interval must be specified in seconds.

    If not specified, maxretryinterval defaults to 60 seconds. If the value supplied is less than 1 second then maxretryinterval would default to 1 second.

  • adr3.discovery.appserver.suffix

    This property is appended with the server names returned back by the Discovery Agent.

    For example, if the server name returned by the Discovery Agent is tibdemo and the value specified is na.tibco.com, then the server connection can use server name tibdemo.na.tibco.com.

    It is good practice to use this property when DNS services are required for connectivity.

Contents
Search Results