![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
After creating an ActiveMatrix SOA project, a composite file for this project is automatically generated. For detailed information about configuring the composite, refer to Configuring Composites.Composites must have a service added to it. For detailed information about how to add a composite service, refer to Creating a Composite Service. In order for the composite service to be accessible from the external client, you need to add a TIBCO Shared Resource.
1. Select your ActiveMatrix SOA project in the Project Explorer Panel, and then select File > New > TIBCO Shared Resources... from the Menu. The TIBCO Resource Wizard dialog appears.Figure 40 TIBCO Resource Wizard - Select a Wizard
−
− For SOAP service, select HTTP Server.
For TIBCO ActiveMatrix Adapter Service Engine for Siebel, only JMS and SOAP services are available.
3. Enter or select the parent folder for the newly created TIBCO Shared Resource file and enter the name for the shared resource file in the File name field. The default shared resource file name is HTTP Server Shared Resource or JMS Shared Resource.
4. Click the Finish button to close the dialog. The newly created TIBCO Shared Resource is displayed in the Project Explorer panel.
1. Double-click the shared resource file under the ActiveMatrix SOA project folder in the Project Explorer Panel. The Shared Resource Editor panel appears on the right.
−
The default name is JMS Shared Resource. The server URL used to create the connection factory. This field is required only for connections to a TIBCO Enterprise Message Service server. See documentation for TibjmsConnectionFactory in TIBCO Enterprise Message Service product documentation (Javadoc) for more information.The default value is tcp://localhost:7222. The factory for creating connections to the JMS server. Set to com.tibco.tibjms.TibjmsConnectionFactory for Enterprise Message Service or progress.message.jclient.ConnectionFactory for SonicMQ.The default value is com.tibco.tibjms.TibjmsConnectionFactory. JNDI Configuration Name A JNDI shared resource definition that specifies the JNDI connection information. Click Browse from the drop-down list to select a JNDI configuration resource. The ConnectionFactory object stored in JNDI. This object is used to create a topic or queue connection with a JMS application.See your JNDI provider documentation for more information about creating and storing ConnectionFactory objects. The default value is GenericConnectionFactory.To create an SSL connection to the JMS server, specify SSLGenericConnectionFactory or any other connection factory with SSL configuration provisioned on the JNDI server. Client Certificate Password Not all JMS servers require user names and passwords. Refer to your JMS provider documentation and consult your system administrator to determine if your JMS server requires a user name and password. Client ID for the connection. Typically JMS providers have a provider-specific format for client IDs. See your JMS provider’s documentation for more information about client IDs. If specified, the client ID must be unique within the scope of connections within the server.
The default name is HTTP Server Shared Resource. SSL Configuration The SSL server shared resource used for the connection. The field label is a link to the resource. Click Browse from the drop-down list to select a SSL configuration resource. The minimum number of threads available for incoming HTTP requests. The HTTP server creates the number of threads specified by this parameter when it starts up. Maximum Threads The maximum number of threads available for incoming HTTP requests. The HTTP server will not create more than the number of threads specified by this parameter.When a client sends a request that cannot be processed because no threads are available, the ActiveMatrix node returns the ConnectionRefused exception to the client.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |