![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
1. In the TIBCO Silver Fabric Administrator GUI, select Stacks > Components.
2. On the Components page, select Create New TIBCO ActiveMatrix® Administrator Component shown in the Global Actions list depicted here in Figure 1.
To use TIBCO Hawk ActiveMatrix Plug-in, you need to select the TIBCO_ActiveMatrix_SERVICE_GRID_DISTRIBUTION as 3.3.0.0.2.Figure 3 Choose TIBCO ActiveMatrix® Product Plug-ins
− TIBCO ActiveMatrix® Binding Type for EJB
− TIBCO ActiveMatrix® Binding Type for Adapters
− TIBCO ActiveMatrix® Implementation Type for Microsoft CLR
Figure 4 Optional Distribution
8. Figure 5Selecting the Hawk version
Figure 7 EMS SSL Configuration
• Use an Admin Enterprise Name that is as short as possible, for example, "N1" or "N2" etc.… instead of "testDevNode"
• Use an Admin Instance Name that is as short as possible, for example, "i1" instead of "instanceOne"
• Use a Deployment Directory with as few characters as possible: "C:\AMX" instead of "C:\ActiveMatrix."When you select this check box and publish a dependent component using the TIBCO Silver® Fabric Enabler for TIBCO EMS Server (SFEM), the connection and configuration settings are set automatically. The "TIBCO EMS Connection Configuration" page is not displayed unless you select the EMS Connection Factory check box to input connect configurations for a TIBCO EMS instance that was not created as a component dependency with the application stack.If the TIBCO EMS instance will be independent of the ActiveMatrix Administrator Stack, then check this box and later enter the EMS Connection Factory name on the Enterprise Message Service Connection Factory component wizard page.Enter a directory path to where your ActiveMatrix® Administrator should deploy on the target TIBCO Silver Fabric Engine. If that directory is not present then it will be created during the deployment initialization.Deployment persistence ensures that restart of an ActiveMatrix Component will maintain deployment configuration continuity for the TIBCO ActiveMatrix Administrator Component and the runtime component instances of TIBCO ActiveMatrix Service Grid. Deployment persistence preserves the tibcoHome directory, files, and the configuration for tibcoHome so that restart re-establishes the same connections.
EXCEPTION: When Deployment Persistence is enabled the following settings can be changed and published to existing published Components:When Deployment Persistence is not checked then an orderly shutdown of the Component will cleanup and remove the tibcoHome directory and the associated database tables.Simply unchecking the Deployment Persistence checkbox and saving the component setting will not change a persistent component that was already deployed.When you no longer want a persistent deployment, the published instance and the associated database must be cleaned manually according to the uninstallation procedure described in the TIBCO ActiveMatrix Service Grid Installation Guide.The Default Admin Database is used for the Component data unless this check box is deselected. The Component Wizard will display the External Database Configuration page (refer to the section on External Database Configuration (optional)) for you to change the settings if you have deselected this checkbox and proceed through the Next screens.For more information on using MCR, refer to the chapter on Governance in the TIBCO ActiveMatrix Service Grid Administration Guide.The port settings initially point to the default values. Normally the port settings should be left as it is, unless your implementation environment has port conflicts that require changes. For descriptions of these and other settings refer to the TIBCO Silver Fabric Users Guide and TIBCO ActiveMatrix Service Grid Administration Guide.Checking this box enables the TIBCO ActiveMatrix Service Grid Mediation Component as part of a Service Oriented Architecture (SOA) for applications. Refer to the TIBCO ActiveMatrix Service Grid Mediation Component Development guide for more information on what enabling this will provide.For information on the systems impacted by changing the default ports for any of the various communication channels, please refer to the TIBCO ActiveMatrix Service Grid documentation.Figure 9 Setting EMS ConfigurationEMS URL - EMS uses TCP and the default port used for messaging is 7222. The actual port value used is implementation dependent. EMS can be hosted locally by the same machine hosting the TIBCO Silver Fabric Server or it may be hosted by an external installation.TIBCO EMS server must be running before the TIBCO ActiveMatrix Administrator Component is started. To ensure that happens Add Allocation Rules with a Component Dependency for the TIBCO ActiveMatrix Administrator Component so the EMS Component is running before the ActiveMatrix Administrator component is started.
Using EMS with Deployment Persistence - When Deployment Persistence is enabled on the TIBCO ActiveMatrix Administrator component, then the EMS Component must also have an allocation rule specifying that EMS must be run on the same Silver Fabric Engine. This ensures that a restart of the Administrator will make the proper connections with the EMS Component.When the ActiveMatrix® Administrator instance must have access to a third party database you must upload the appropriate drivers so they may be instantiated on the Engine.Figure 10 Upload Third Party DriversIf you deselected the "Use Default Admin Database" check box on the Basic Configuration page then this page will appear in the Component Wizard configuration workflow.Database Type - The TIBCO Silver Fabric Enabler for ActiveMatrix Service Grid ReadMe lists those data sources and JDBC drivers that are supported for this release.Database Max Connections - Set the number of database connection threads according to the expected need of the Component.If you select the check box to "Use different database for logging", a page named "Database Logging Configuration" appears next to allow specification of database URLs and logins for Monitoring, Logging, and Payload databases. Refer to the TIBCO ActiveMatrix Service Grid Installation and Configuration document for more information on preparing external databases for use with TIBCO ActiveMatrix Service Grid.Figure 12 Setting the SSL ConfigurationFor more information on using SSL with TIBCO ActiveMatrix Service Grid refer to the Security chapter of the TIBCO ActiveMatrix Service Grid Administration Guide.
Figure 13 Add or Remove Log File PatternsRefer to the Silver Fabric Help or the Silver Fabric User’s Guide for more information on controlling the Component behavior.Figure 15 Default Engine Allocation SettingsRefer to TIBCO Silver Fabric User’s Guide and Administration Guide for additional information on these configurations.Figure 16 Configure Component OptionsAfter you click the Finish button, the Component is created.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |