- PowerCenter 10.4.0
- All Products
Name you want to use for this connection.
Code page the Integration Service uses to extract data from the TIBCO. When using relaxed code page validation, select compatible code pages for the source and target data to prevent data inconsistencies.
Default subject for source and target messages. During a session, the Integration Service reads messages with this subject from TIBCO sources. It also writes messages with this subject to TIBCO targets.
You can overwrite the default subject for TIBCO targets when you link the SendSubject port in a TIBCO target definition in a mapping.
Service attribute value. Enter a value if you want to include a service name, service number, or port number.
Network attribute value. Enter a value if your machine contains more than one network card.
TIBCO daemon you want to connect to during a session. If you leave this option blank, the Integration Service connects to the local daemon during a session.
If you want to specify a remote daemon, which resides on a different host than the Integration Service, enter the following values:
For example, you can enter
host2:7501to specify a remote daemon.
Select if you want the Integration Service to read or write certified messages.
Unique CM name for the CM transport when you choose certified messaging.
Enter a relay agent when you choose certified messaging and the node running the Integration Service is not constantly connected to a network. The Relay Agent name must be fewer than 127 characters.
Enter a unique ledger file name when you want the Integration Service to read or write certified messages. The ledger file records the status of each certified message.
Configure a file-based ledger when you want the TIBCO daemon to send unconfirmed certified messages to TIBCO targets. You also configure a file-based ledger with Request Old when you want the Integration Service to receive unconfirmed certified messages from TIBCO sources.
Select if you want PowerCenter to wait until it writes the status of each certified message to the ledger file before continuing message delivery or receipt.
Select if you want the Integration Service to receive certified messages that it did not confirm with the source during a previous session run. When you select Request Old, you should also specify a file-based ledger for the Ledger File attribute.
Register the user certificate with a private key when you want to connect to a secure TIB/Rendezvous daemon during the session. The text of the user certificate must be in PEM encoding or PKCS #12 binary format.
Enter a user name for the secure TIB/Rendezvous daemon.
Enter a password for the secure TIB/Rendezvous daemon.
Updated July 21, 2022