To configure the TIBCO® Adapter for SAP Component, perform these tasks:
You can select any version of the distributions installed in the Silver® Fabric Broker. By default, the latest versions of the distributions are displayed.
Specify a JDBC driver to publish with the TIBCO® Adapter for SAP Distribution for TIBCO Silver
® Fabric so that it can communicate with the TIBCO Administrator Domain database. When the TIBCO Administrator uses a database as the domain storage, you must upload a JDBC driver so the component can interact with it.
TIBCO Domain machine name: To activate use of the TIBCO Domain Logical Machine Name enter a value in the TIBCO Domain machine name field. The TIBCO Domain machine name can use alphanumeric characters, hyphen (-), or underscore (_) characters. Do not use other special characters, including period or comma. The name length must be less than 64 characters.
Add external JAR file(s) to the Adapter for SAP Component: As an option, JAR files can be uploaded for publishing with the TIBCO Silver Fabric Enabler for Adapter for SAP component.
The check box "Add the JAR file(s) in front of the ClassPath (check), otherwise at the end of the ClassPath (unchecked)" means just what it says. The JAR file name can be prepended in front of the ClassPath by checking the box and if it is left unchecked the JAR file name is appended at the end of the ClassPath. Of course, this setting does not apply if a JAR file is not uploaded for addition to the ClassPath.
AMI Hawk Service: specifies the TIBCO Hawk port number, for example, TIBCO Rendezvous connects with TIBCO Hawk on the default port 7474. AMI Hawk Service and AMI Hawk Daemon must be set with valid values together. Setting only one of them results in an error.
AMI Hawk Daemon: specifies the location of the TIBCO Hawk Daemon. A value of "tcp:yyyy" corresponds to a local Hawk Daemon where "yyyy" is the port number. A Hawk Daemon located elsewhere is specified by a value of the protocol, IP address, and port number: "tcp:xxx.xxx.xxx.xxx:yyyy".
AMI Hawk Network is generally, an empty string, and all three fields can be left empty. If all three fields are left empty then the enabler uses the default value"
7475" and "tcp:
7474".
String,
Environment,
System, or
Encrypted variables may be added to the Component to define and set runtime specific context variables.
Select a variable type from the Add Variable drop-down list or if required, edit the variable.
ARCHIVE_DETECTION_FREQUENCY is the periodic interval (the default value is
30 seconds) for detection of deployed archives and report to the broker. The broker uses this data to synchronize the archive with scaling rules.
To remove unwanted JAR files use the Menu button to display the list of Wizard configuration steps and select
Add/Override/Customize Container and Component-specific content files. Relative paths to external jar files that are added, can be removed with that window.
For more information on what and how the configure.xml can be changed refer to "The configure.xml File" section in the
TIBCO Silver® Fabric Developer’s Guide
The property, baseDir, in the
<configFiles> element is used to specify the path that includes the file to be updated. It can be modified if needed. For example, if the TIBCO Runtime Administrator (TRA) version was 5.8 instead of 5.7, then the
baseDir value would be
${TIBCO_HOME}/tra/
5.8/template/domainutility
The property, include, in
<configFiles> element is used to specify which file(s) need to be replaced. It can specify whatever files you want to change. The asterisk wild card may be used to represent a string of characters like for instance: "
*.tra" to change all of the
.tra files in
%baseDir%.
The property, pattern, in the
<regex> element is used to specify the contents that need to be replaced within the previously specified files. The value of
pattern can be a regular expression.
The property, replacement, in
<regex> element is used to specify the new contents of the node specified by the
pattern property value.
These final configurations are optional for TIBCO® Adapter for SAP Components. Refer to
TIBCO Silver® Fabric User’s Guide for more information on these configuration screens.
Click the Finish button to save your changes and then you can publish the Component as part of an Application Stack.
To do this, select Publish Component in the
Actions list located at the line of the Component you just created.