Configuring TIBCO Information

See your TIBCO documentation for more information about TIBCO product.

If you are using a TIBCO messaging system, enter the following information on the TIBCO Messaging Information page of the Create Connection wizard:

  1. In the TIBCO Message Type field, choose:

  2. If you selected RV or RVCM as the TIBCO Message Type:

    1. Enter the name of the RV and RVCM transport in the Service Name field. The service name can be either a string value or a port number. By default, the value is 7500.

    2. Enter the name of the host name or IP address where the TIBCO Rendezvous daemon is running in the Network field.

      For example, enter job1-srvr.

    3. Enter the TIBCO Rendezvous daemon value in the Daemon field in the form:

      protocol:hostname:port
      

      For example, enter tcp:my_machine:7500.

      If you do not specify a value for the host name, it defaults to “localhost.”

      The default value is tcp:7500 which defaults to “localhost” on port 7500.

      If your TIBCO Rendezvous Daemon is running on a separate machine than RepConnector, you must specify the host name; for example, enter:

      tcp:mymachine:7500
      
    4. Enter the name of the subject or destination at which the client application is listening in the Subjects field. For example, enter sample.subject.

      You can specify more than one subject name separated by commas.

    5. If you are using a RVCM message type, enter the name of the certified messaging names in the CM Names field. For example, enter SAMPLE.CM1

      You can specify more than one subject name separated by commas.

    6. If you are using RVCM message type, enter in the CM Duration field minutes that TIBCO message system stores the unread messages in the cmledger.

      The default value is 0, which means the messaging system keeps messages in the cmledger forever.

      For example, enter 10 to have the messaging system keep unread messages for 10 minutes.

  3. If you selected AECM as the TIBCO Message Type, enter the information for AECM.

    sample.MyMsgGenerator
    
  4. If you are routing events from messaging system to database, enter the destination name in the Status Destination field. The status destination queue or topic you define is used for client application to listen an error message (if any) that may result in the event being sent to the database.

If you have just configured inbound information, go back to step 10 in “Adding and configuring a new connection”.