Installing Apama using Command Central
You can provision new and update existing Apama environments using Software AG Command Central. You can do this on any machine on which the Platform Manager is running. You can then invoke the Software AG Installer or Software AG Update Manager directly from Command Central and do silent installations and uninstallations of the Apama product and its product fixes.
This topic just provides a brief overview of how to install Apama using
Command Central. For detailed information, see the
Command Central documentation at
http://documentation.softwareag.com/ (Empower login required). You can find it under
Guides for Tools Shared by Software AG Products.
If you want to install Apama using Command Central, proceed as follows:
1. Install a Command Central server.
Tip: | The default credentials for a new installation are "Administrator" for the user name and "manage" for the password. |
2. Install the Platform Manager on any machine on which you want to install Apama.
3. Ensure that the Command Central service has been started.
4. Configure a repository for the Apama product (using either the web user interface or the sagcc command line interface). To do so, you can either use your Empower credentials or a locally generated image.
5. Install Apama using one of the following options:
Using the
Command Central web user interface. See
Software AG Command Central Help for information on how to install products.
Using the
Command Central command line interface, with a command line such as the following:
sagcc exec provisioning products nodeAlias repoName install
artifacts=productId
where:
nodeAlias is the alias of the target node on which you want to install Apama, for example, "local".
repoName is the name of the product repository from which to install Apama, for example, "webMethods-X.Y".
artifacts=productId specifies the parts of the Apama product that you want to install. Available product IDs for Apama are (you separate them using commas):
This product ID | installs the following |
PAMServer | Apama Server |
PAMDashboardViewer | Dashboard Viewer |
PAMDesigner | Software AG Designer with the Apama Development Environment |
PAMspm | Platform Manager Plug-in. This Apama plug-in for Command Central's Platform Manager is required if you want to use Command Central to start, stop and configure Apama components on the current machine. |
You can use the sagcc list jobmanager jobs command to monitor the progress of the provisioning job.
Note: | The Command Central installation uses the default location of the Apama work directory. On Windows, this is in the all-users %PUBLIC% directory (for example, C:\Users\Public\SoftwareAG\ApamaWork_n.n) and on UNIX this is ~/softwareag/apamawork_n.n. Command Central does not copy an Apama license file into the installation. You must provide a license file after installing Apama, by manually copying the file to APAMA_WORK/license/, using Command Central composite templates to copy the file into APAMA_HOME/etc/, or by uploading a license file individually to the configuration of each correlator instance added to Command Central. |
6. Install all available Apama fixes in the repository by using one of the following:
The
Command Central web user interface.
The
Command Central command line interface, by using the following command:
sagcc exec provisioning fixes nodeAlias Empower install
products=PAMServer,PAMDashboardViewer,PAMDesigner,PAMspm
where "Empower" is a fix repository name, and products= specifies the list of products to be updated (these are the same product IDs as for the other sagcc command that is described above).
