Reference: Example Runtime Instance Configuration File

Warning: Manually modifying this file should be done only by advanced users. Modify the configuration file as described.  Changes other than those described here may result in engine startup failure or failure to create or reconfigure instances. For assistance, use the user interface in the Administration perspective to set properties and values.

Adding or Editing Error and No Hit Transports

You can customize runtime instance properties by editing the 'value' attributes of one or more <Property> elements.  For example, every runtime instance needs an Error Transport and a No Hit Transport.  These are set using <Property> elements inside a <Configuration> element with a 'name' value which is the same as the name of the runtime instance.  The specific <Property> elements in this case would be:

<Property name="P_ERROR_TRANSPORT" value="" />

<Property name="P_NO_HIT_TRANSPORT" value="" />    

Assuming you had already defined messaging endpoints with the names nohit and error, you would change the aforementioned elements as follows:

<Property name="P_ERROR_TRANSPORT" value="sybase-ebd:configuration:rd:RC_MESSAGING:RT_JMS_TRANSPORT:nohit" />

<Property name="P_NO_HIT_TRANSPORT" value="sybase-ebd:configuration:rd:RC_MESSAGING:RT_JMS_TRANSPORT:error" />    

The prefix sybase-ebd:configuration:rd:RC_MESSAGING:RT_JMS_TRANSPORT:

identifies each queue as being of type JMS Transport.  The last  portion of the value is the name of the endpoint itself, as is displayed in the Endpoint Manager.

You will find it helpful to export data from the Endpoint Manager and have that available when looking for the proper values to specify for this type of property. Other runtime instance property types are simpler: some are integers or boolean values ("true" or "false"). You must select additional property values from an enumeration that is specific to that  property. For assistance, use the user interface in the Administration perspective to set properties and values. You can also contact Sybase Technical Support for assistance.

Adding or Editing Input Transports

You may also add input transports for a runtime instance by inserting a group of elements similar to the following:

        <Config name="<name_of_endpoint_representing_input_transport>" description=" " parentId=

"sybase-ebd:taxonomy:rd:RC_SERVICE_PLATFORM:RT_SERVICE_PLATFORM:<server_name:<runtime_instance_name>:RT_PS_ENGINE_TUNABLES"

            <Property name="P_SERVER_INSTANCE_RESOURCE_REF" value="sybase-ebd:configuration:rd:RC_MESSAGING:RT_JMS_TRANSPORT:input" />

            <Property name="P_COMMIT_INTERVAL" value="1" />

            <Property name="P_DEFAULT_MSG_TYPE" value="" />

            <Property name="P_CAPTURE_THREADS" value="1" />

            <Property name="P_DEFAULT_ENCODING" value="" />

            <Property name="com.sybase.ebd.eai.internal.resources.directory.IO_VERSION" value="4.3" />

            <Property name="P_DEFAULT_LOCALE" value="" />

            <Property name="P_DEFAULT_APP_GROUP" value="" />

            <Property name="com.sybase.ebd.eai.internal.resources.directory.RESOURCE_TYPE_ID" value="RT_PS_ENGINE_TUNABLES" />

        </Config>

Like the runtime instance properties <Config> element, this element should be inserted as a child of the <Configurations> element.  Make sure that you edit the <Config> element's 'name' attribute as well as the value of the   P_SERVER_INSTANCE_RESOURCE_REF property to match a queue transport from your Directory Services database.  You can also edit various properties of the input transport, such as the value of the P_CAPTURE_THREADS property.