Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Post-Installation Configuration : Configuration Procedure

Configuration Procedure
After you have successfully performed a new installation of ActiveMatrix Decisions, you MUST MANUALLY CONFIGURE the decision product applications using ActiveMatrix Administrator.
There are separate steps to configure the two possible components that can be installed:
After you have completed the necessary configuration as described in this chapter (for one or both of the components, depending on what you have installed), you are ready to deploy customer applications (DAAs) that use decisions. This can be done from either TIBCO Business Studio or from TIBCO ActiveMatrix Administrator — for information, see the documentation for those products.
Configuring the ActiveMatrix Decisions IT
1.
This is required so that the application template for ActiveMatrix Decisions IT will show up in ActiveMatrix Administrator.
The procedure for this differs somewhat between a Windows and UNIX systems, as described in the two sets of substeps below.
To stop and restart the SystemNode on Windows:
a.
b.
Navigate to the directory that contains tibcohost.exe. For example:
      C:\ProgramData\amx-bpm\tibco\data\tibcohost\
      Admin-AMX BPM-AMX BPM Server\host\bin\
c.
      tibcohost stopNodes -nodeNames SystemNode
d.
      tibcohost startNodes -nodeNames SystemNode
Note that you need to give the SystemNode a few minutes to restart. You can monitor the tibamx_SystemNode.exe process in Task Manager to determine if it has fully restarted.
e.
To stop and restart the SystemNode on a UNIX system:
a.
b.
      /opt/config/bpm400/tibco/data/tibcohost/
      Admin-AMX BPM-AMX BPM Server/host/bin
c.
      ./tibcohost stopNodes -nodeNames SystemNode
d.
      ./tibcohost startNodes -nodeNames SystemNode
Note that you need to give the SystemNode a few minutes to restart.
e.
2.
3.
a.
Select the Applications tab, then click the New button.
b.
Choose the Select an existing application template option, then click Show system application templates.
c.
The default name for the application is "com.tibco.adec.service.daa". This can be changed in the Application Name field, if desired.
Note that if you change the application name AND you plan to deploy decisions service applications directly from TIBCO Business Studio, you will need to set the "Product Application Name" value in TIBCO Business Studio (found on the Window > Preferences > Decisions dialog). For more information, see the TIBCO ActiveMatrix Decisions User’s Guide.
d.
Click Next.
e.
f.
g.
4.
On the Administrator Applications tab, refresh the list of applications (using the button) until you see "Running" in the Runtime State column for the decisions application.
Configuring the ActiveMatrix Decisions Task Extension Activity
To configure the ActiveMatrix Decisions Task Extension Activity:
1.
2.
a.
Select Applications, then click the New button.
b.
Choose the Select an existing application template option, then click Show system application templates.
c.
d.
e.
f.
If there is not an HTTP client resource instance defined on the node, proceed to step g. The wizard will step you through creating the HTTP Client in later steps.
If there is an HTTP Client resource instance defined on the node, click the eye-dropper icon to the right of the "HttpClient_DecisionService_EP" entry in the Property Value column, select "BPMNode" in the Host list, select the instance from the Instances list, then click Save.
g.
The next dialog should tell you that the validation was successful. Note, however, that the message will also state that there were a few issues if you had not selected an HTTP Client resource instance in the previous step (this will be resolved after you click Deploy).
h.
Click Deploy.
i.
If you had selected an HTTP Client resource instance in step f, proceed to step 3, otherwise continue with the rest of these sub-steps.
j.
Click the Resolve link in the upper right part of the dialog.
k.
Click the new resource template link in the upper right part of the dialog.
l.
In the Type field list, choose "Http Client".
m.
Change the name in the Name field to "decHTTPClient".
n.
o.
Change the number in the Port field to the port number used by the HTTP Connector on the node to which you are deploying (the default is 8080, but may have been changed), then click Save.
p.
q.
r.
s.
3.
On the Administrator Applications tab, refresh the list of applications (using the button) until you see "Running" in the Runtime State column for the decisions application.
 
 

Copyright © TIBCO Software Inc. All Rights Reserved