This chapter describes installation of AM Communicator and includes the following information:
Separate configuration stages are required for DIVArchive, AMC, and Avid Archive Manager servers to configure interaction between DIVArchive and Avid Archive Manager using the AM Communicator. See Appendix A for Oracle DIVArchive options and licensing information.
You can install AMC on any computer, provided the computer is accessible through the network from the DIVArchive Actor, DIVArchive Manager, and Avid Archive Manager servers. This option enables installation of AMC on its own computer, separate from any specific server, if desired.
The following definitions apply when the term or acronym is used within this chapter:
$DLL_HOMEThis variable identifies the folder on target Avid server where the DET2.DLL is installed.
$AMC_HOSTThis variable identifies the DNS (Domain Name Service) name or IP address of the computer where AM Communicator is installed.
$DIVA_HOMEThis variable identifies the DIVArchive folder created on the target computer during the installation.
$AMC_HOMEThis variable identifies the AM Communicator folder on the target computer.
$AMC_INSTALLATIONThis variable identifies the AM Communicator folder created during DIVArchive installation as follows:
$DIVA_HOME/AMCommunicator for earlier Interplay releases.
$DIVA_HOME/AMCommunicatorI22 for Interplay 2.2 and later.
You use the following procedure to install AM Communicator:
Copy all files from the $AMC_INSTALLATION/bin folder to the $AMC_HOME folder on the destination computer.
The default configuration file is located in the $DIVA_HOME/conf/amc folder. Rename the file named amc.conf.ini to amc.conf.
If you require multiple AMC instances to run on the target computer, add the corresponding service name to the file name. The service name must match the SERVICE_NAME parameter value from the AMC configuration; that is, rename the file to amc_$SERVICE_NAME.conf.
Edit the AMC configuration file using a plan text editor (for example, Notepad or Notepad++) to modify any required parameter values. See Appendix C for detailed parameter descriptions.
AM Communicator can be started either as a Windows system service, or as a console application. Oracle recommends running AMC as a system service in production environments. However, console mode is useful when performing troubleshooting activities.
If you must run two AMC instances on a single computer, you must specify the fully qualified configuration file path in the command-line using the -conf (or -f) option described in the following list.
The general syntax to start AMC is as follows:
AMCService {options_from_the_following_list}
For example, the following command starts an AMC instance using parameters from the configuration file named amc_example.conf, and runs in console mode (the -d option). You must set the SERVICE_NAME parameter value to example for this sample. See Appendix B for all AMC parameters.
AMCService -d -conf ../conf/amc/amc_example.conf
AM Communicator supports the following command-line options:
install or -iThis option installs AMC as a Windows service using the provided command-line options as the default parameters. This option will not start the service, it only installs the service.
uninstall or -uThis option removes AMC from the Windows services. This option will stop the service automatically if it is running.
debug or -dThis option starts the AMC service in console mode. The console mode provides additional information as standard output.
version or -vThis option displays the AMC release level, and then exits.
help or -hThis option displays use information, and then exits.
conf or -fThis option specifies a fully qualified configuration file path for AMC to use instead of the default configuration file. You use this option when running multiple instances of AMC on a single computer (as shown in the previous example).