TIBCO® API Exchange Gateway Distribution for TIBCO Silver
® Fabric contains the expanded product installation used to publish and run any and all of the following:
−
|
TIBCO® API Exchange Gateway - Configuration GUI (asg-configui)
|
−
|
TIBCO® API Exchange Gateway - Core Engine (asg-core)
|
−
|
TIBCO® API Exchange Gateway - Core Engine (asg-core) with the Cache Agent Enabled (asg-caching-core)
|
−
|
TIBCO® API Exchange Gateway - Global Throttle Manager (asg-gtm)
|
−
|
TIBCO® API Exchange Gateway - Cache Agent (asg-cache)
|
−
|
TIBCO® API Exchange Gateway - Cleanup Agent (asg-cache-cleanup)
|
−
|
TIBCO® API Exchange Gateway - APIX Central Logger (asg-cl)
|
Publish the TIBCO® API Exchange Gateway component after you complete these tasks and at runtime, access TIBCO Configuration GUI, using the TIBCO Silver Fabric VirtualRouter address:
http://Virtualrouter:9200/ConfigUI/
or directly with the Engine URL:
http://SilverFabricEngine:9200/ConfigUI/
Refer to the TIBCO Silver® Fabric Enabler for TIBCO
® API Exchange Gateway
Readme for more information on supported distributions.
|
Make sure that the TIBCO_RV_distribution is present as is shown above. TIBCO Rendezvous must be published with the TIBCO ® API Exchange Gateway Distribution for TIBCO Silver ® Fabric to provide messaging.
|
The TIBCO® API Exchange Gateway: Configuration User Interface or Engine page and each of the configuration parameters are described here. Enter appropriate values for each field as applicable.
•
|
Enabler will launch - The "Enabler will launch" parameter determines whether this component will publish and install the TIBCO ® API Exchange Gateway Configuration UI or run one of its Engines or Agents. Another option allows for manual testing of an Engine or Agent after configuration and installation.
|
−
|
Configuration UI - enables component configuration of the TIBCO ® API Exchange Gateway User Interface.
|
−
|
Engine - enables component configuration of the TIBCO ® API Exchange Gateway Engines/Agents and directly running that Engine/Agent when published and run in a Stack.
|
The selected Enabler will launch option determines what Component Wizard pages are displayed next.
•
|
Configuration directory path - When empty the location is the value of the runtime variable: TIBCO_HOME_CFGMGMT_DIR (set to ${ENGINE_WORK_DIR}/cfg_data To set a value other than the default simply enter a relative directory path such as: usr/myname/someDirectory
|
•
|
Change parameters - When this checkbox is selected the Logging Level and the HTTP Channel Base Port parameter values will apply. When this checkbox is not checked these parameter values will not be changed regardless of what values are input in the HTTP Channel Base Port fields below.
|
•
|
Logging Level - The logging level can be set to Debug (0), Info (1), Warning (2), Error (3), No Logging (4).
|
•
|
Façade HTTP Channel Base Port / Façade HTTPS Channel Base Port - The client facing HTTP /HTTPS (SSL) base port starting point. This value is used as the reference so additional Engine instances derived from the same Component on the same machine get incremented HTTP/HTTPS port values to avoid port conflict. Refer to the TIBCO API Exchange Gateway User’s Guide for more information about use of the ports.
|
•
|
OAuth HTTP Channel Base Port / OAuth HTTPS Channel Base Port - TIBCO API Exchange Gateway OAuth Server HTTP /HTTPS (SSL) base port starting point. This value is used as the reference so additional Engine instances derived from the same Component on the same machine get incremented OAuth HTTP/HTTPS port values to avoid port conflict. Refer to the TIBCO API Exchange Gateway User’s Guide for information about use of OAuth Server.
|
Where the EngineInstanceValue is the Engine number where the application is running. For example on a dual-core machine, the default number of Engines is two (one per core). The first
EngineInstanceValue will have a value of
zero, the second will have a value of
one.
Enable Reporting - Enable reporting (event messaging) with a Central Logger. When the Enable Reporting checkbox is selected a Central Logger Component must be set as a dependency for the Configuration UI Component and it must be present in the Stack.
Enabler Facade/Target JMS Transport - Leave this checkbox unselected to use TIBCO Rendezvous as the default messaging transport between component servers. When Rendezvous is the preferred messaging transport no further messaging configuration is necessary.
JMS Delivery Mode - Select a JMS delivery mode for TIBCO API Exchange Gateway servers. The delivery mode may be
NON_PERSISTENT, PERSISTENT, or RELIABLE as is described in the table below:
|
|
|
|
|
|
|
|
RELIABLE (requires use of TIBCO Enterprise Message Service)
|
|
|
JMS Acknowledgment Mode - consult the following table
|
|
|
|
|
|
|
|
|
|
|
NO_ACKNOWLEDGE (requires use of TIBCO Enterprise Message Service)
|
|
Note Sessions created in NO_ACKNOWLEDGE receipt mode cannot be used to create durable subscribers.
Note Also, queue receivers on a queue that is routed from another server are not permitted to specify NO_ACKNOWLEDGE mode.
|
EXPLICIT_CLIENT_ACKNOWLEDGE (requires use of TIBCO Enterprise Message Service)
|
|
•
|
EXPLICIT_CLIENT_ACKNOWLEDGE is like CLIENT_ACKNOWLEDGE except it acknowledges only the individual message, rather than all messages received in the session.
|
•
|
One example of when EXPLICIT_CLIENT_ACKNOWLEDGE would be used is when receiving messages and putting the information in a database. If the database insert operation is slow, you may want to use multiple application threads all doing simultaneous inserts. As each thread finishes its insert, it can use EXPLICIT_CLIENT_ACKNOWLEDGE to acknowledge only the message that it is currently working on.
|
|
|
|
•
|
EXPLICIT_CLIENT_DUPS_OK_ACKNOWLEDGE mode is like TIBEMS-DUPS-OK-ACKNOWLEDGE except it "lazily" acknowledges only the individual message, rather than all messages received so far on the session.
|
|
Refer to the TIBCO Enterprise Message Service User’s Guide for more details on the JMS message delivery and acknowledgement modes.
When Enable Facade/Target JMS Transport is checked, four additional component configuration pages are added to enable settings for SOAP/JMS and ESD for both Facade and Target transport messaging where it may be applicable for your implementation. Click
Next to enable and configure those settings.
Enable Transport - You may enable one or many of the transport settings for either the Façade (client request) or Target (data services/sources) using either SOAP/JMS and/or ESB transports. Configuration settings may be modified if you enable a transport for the component.
Request Queue - Specifies the queue name for the requests channel communication. An exact match request queue must exist on the JMS provider at the facade/target side when the component is started.
Reply Queue - Specifies the queue name for the reply (response) channel communication. An exact match reply (response) queue must exist on the JMS provider at the facade/target side when the component is started.
JNDI Context Factory - The default value for the initial Java Naming and Directory Interface (JNDI) context factory points to TIBCO Enterprise Message Service. If you’re using another JMS provider you can change the JNDI context factory here.
Topic Connection Factory Name - Specifies the name of TopicConnectionFactory object stored in JNDI. This object is used to create a topic connection on either the facade or target side depending on which configuration page it is being specified.
Queue Connection Factory Name - Specifies the name of QueueConnectionFactory object stored in JNDI. This object is used to create a queue connection with ESB services at either the facade or target side depending on which configuration page it is being specified. The Queue Connection Factory Name specified has to match the Queue Connection Factory Name defined for use in the JMS provider. When using a third-party JMS provider the Queue Connection Factory Name must match in this field and in the JMS provider.
Use Exported JMS Connection Settings from EMS Component - If you are using TIBCO Enterprise Message Service you can check this box and skip configuration of the parameters described below. Checking this box will add a Component Wizard page (shown below) to allow you upload the appropriate JAR files (
jms-2.0.jar and
tibjms.jar for TIBCO EMS) to set and establish connections.
Note: A relative path can be specified, but it is not necessary.
JMS Provider URL - Specifies the connection URL for either the JMS provider or TIBCO EMS used for either the facade or target operation requests.
JNDI Context URL - Specifies the URL to the JNDI service provider used for facade or target operation requests within the communication domain.
JMS Username - Specifies the user name for logging into the JMS provider or TIBCO EMS in the domain at either the facade or the target side.
JMS Password - Specifies the password for logging into the JMS provider
JNDI Username - Specifies the user name for logging into the JNDI server in the domain at either the facade or the target side. If the JNDI provider does not require access control, this field can be empty.
JNDI Password - Specifies the password for logging into the JNDI server communication domain at the facade or target side. If the JNDI provider does not require access control, this field can be empty.
Refer to the TIBCO Enterprise Message Service User’s Guide and the
TIBCO API Exchange Gateway User’s Guide for more details.
When the Enable Reporting checkbox is selected, this page will appear to enable configuration of the log reporting.
Log Reporting Messaging Transport Type: Rendezvous or JMS. If TIBCO Rendezvous is used no further settings are necessary. If your implementation requires use of JMS for reporting, then consider proper values for the parameters.
JMS Transaction Report Destination Name - Specifies the name of the JMS destination to which the transaction reports are sent to the Central Logger by the Core Engine.
JMS Transaction Report Destination Type - Queue or Topic. Specifies the type of the JMS destination to which the transaction reports are sent to the Central Logger by the Core Engine. The default value is queue.
Use Exported JMS Connection Settings from EMS Component- If you are using TIBCO Enterprise Message Service you can check this box and skip configuration of JMS Provider URL, JNDI Context URL, JMS Username, JMS password, JNDI Username, and JNDI password.
When the Enabler is set to launch a TIBCO® API Exchange Gateway Engine, Agent, or processing unit you will want to specify the parameters and properties for launching the API Service Gateway Engine (asg-engine).
Refer to the TIBCO® API Exchange Gateway User’s Guide for information on the command line parameters, options, and properties files used to run the TIBCO
® API Exchange Gateway Core Engine.
Using the various command line options presented in the Component Wizard you can programmatically launch and run a specific TIBCO® API Exchange Gateway processing unit or an agent as is described in the
Processing Units of TIBCO API Exchange Gateway Engine section of the
TIBCO® API Exchange Gateway User’s Guide.
Upload EAR file (optional) - Upload a TIBCO
® API Exchange Gateway enterprise archive (EAR) to publish and run when the Component is instantiated at runtime.
Launch action: -u parameter - allows selection, configuration, installation, and launch from the following list of options:
When Reporting is enabled refer to Log Reporting Messaging for a description of how to set those identical settings parameters.
Polling Period (in seconds) for TIBCO® API Exchange Gateway
verification (required) - This setting specifies the interval of time (in seconds) between verifications that TIBCO
® API Exchange Gateway is still running. If TIBCO
® API Exchange Gateway becomes unresponsive to this verification then the process is automatically restarted.
Automatically Restart Silver Fabric Engine if TIBCO® API Exchange Gateway
fails to restart N successive times (required) - Enter an integer to specify the number of restart retries for the TIBCO
® API Exchange Gateway before the TIBCO Silver Fabric Engine will be restarted. A successful restart will reset the count.
JDBC URL - Provides the protocol, database type, host and port to locate your database for the Central Logger
Username and Password - Make sure that a matching profile exists on the database. Required privileges are listed in the
TIBCO API Exchange Gateway User’s Guide in the section, Database Setup and Configuration for Central Logger.
JDBC Driver Class - Sets the class path for the driver.
Upload JDBC Jar - Upload the third-party JDBC driver for your database so the component can be publish it with the Distribution.
String,
Environment,
System, or
Encrypted variables may be added to the Component to define and set runtime specific context variables. Review the settings that were made previously and if required you can add or edit variables as necessary.
Select a variable type from the Add Variable pull-down list or
Add from Enabler.
To change a variable value select the row and click Edit to change its value. Selected rows may also be removed.
More information on using statistics for micro-scaling or archive scaling is available in the TIBCO Silver® Fabric Cloud Administration Guide and more about Component Archive scaling within a Stack is covered in this guide.
The remaining screens of the Component Wizard are generic for all Silver® Fabric Enablers. The configuration of these is optional for the TIBCO
® API Exchange Gateway component.
Refer to TIBCO Silver® Fabric User’s Guide for more information on these configuration screens.
After you click the Finish button, make sure that the Component is published to make it available when creating a Stack.
To do this, select Publish Component in the Actions drop-down list located at the line of the Component you just created.