This chapter provides checklists and procedures for verifying that Argus Safety is installed correctly.
the correct modules are installed as follows:
Go to Add/Remove Programs and select Argus Safety Web.
Click Modify and click Next.
Verify that the applications that you have installed are checked.
the Argus.XML file has the same data across all the Web Servers.
a single domain user account <Domain User> is running the Argus Web application on all web servers.
the login page appears when the server name is entered in your browser.
you can log in successfully.
system performance satisfies the requirement
Identify the physical folders where the Intake XMLs will be dropped in. There could be one folder for all the available sites, or one folder each for each site. These folders can be on the same machine, or on different machines. Create shares for the folders.
Log in to the Argus Console and open the Sites UI under Access Management menu.
Configure the UNC paths of the identified physical folders for the required Sites.
On the server where Integrations component has been installed, navigate to the path where the Argus Safety Windows Service is running.
<InterfaceSchemas> <add InputXSD="..\..\Integrations\XSD\v1.0\Base.xsd" /> <add InputXSD="..\..\Integrations\XSD\v1.0\DataOperation.xsd" /> <add InputXSD="..\..\Integrations\XSD\v1.0\Dictionary.xsd" /> <add InputXSD="..\..\Integrations\XSD\v1.0\Case_Intake.xsd" OutputXSLT="..\..\Integrations\XSLT\v1.0\CaseIntake_Transform.xsl"/> </InterfaceSchemas>
In the above tag, mention full Argus Install Path. Typically, the Argus Install Path is, <Argus Install Path>\Argus Safety. For example:
<InterfaceSchemas><add InputXSD="<Argus Install Path>\Argus Safety\Integrations\XSD\v1.0\Base.xsd" /><add InputXSD="<Argus Install Path>\Argus Safety\Integrations\XSD\v1.0\DataOperation.xsd" /><add InputXSD="<Argus Install Path>\Argus Safety\Integrations\XSD\v1.0\Dictionary.xsd" /><add InputXSD="<Argus Install Path>\Argus Safety\Integrations\XSD\v1.0\Case_Intake.xsd" OutputXSLT="<Argus Install Path>\Argus Safety\Integrations\XSLT\v1.0\CaseIntake_Transform.xsl"/></InterfaceSchemas>
Edit the following files:
Uncomment the following entries under the <RelsysConfigFilesSection>/<RelsysConfigFiles>
Relsys.InterfaceComponents.ProcessorsConfiguration
Relsys.CaseIntake.FolderConfiguration
Make sure that the DatabaseConfiguration section is configured for the following attributes:
| Attribute | Description |
|---|---|
| DBName
(Mandatory) |
TNS of the database to which the RelsysWindowsService should connect to.
Example: DBName="GOLDDEMO" |
| DBUser | AGService Username.
The RelsysWindowsService logs into the database using this login name. This has to be a user of type AGSERVICE. Example: DBUser="agservice_user1" |
| DBPassword | Generate new encrypted string, refer to Section 19.2.4, "Generate Encrypted String". |
| GeneralEmailTo | The e-mail address to which the e-mails will be sent by the Intake Service, using the General Email feature of Argus.
Example: GeneralEmailTo ="rrecepient@oracle.net" |
| GeneralEmailFrom | The email address from which the e-mails will be sent by the Intake Service, using the General Email feature of Argus.
Example: GeneralEmailFrom ="admin@oracle.net" |
| GeneralEmailCc | This email address will be added to the Cc line when e-mails are sent by the Intake Service, using the General E-mail feature of Argus.
Example: GeneralEmailCc ="recepient@oracle.net" |
| GeneralEmailBcc | The email address will be added to the Bcc line when e-mails are sent by the Intake Service, using the General E-mail feature of Argus.
Example: GeneralEmailBcc ="recepient@oracle.net" |
Uncomment the entries for "Case Intake" and "Case Intake Ack" in the <ServiceConfiguration>/<ServiceComponents> section
The following configuration changes are optional:
"Recurrence": The value for this attribute specifies the frequency of instantiation of the associated Service Component. The value is specified in seconds. For example:
<add Name="Case Intake Ack" Assembly="CaseIntakeServiceComponent" Type="Relsys.CaseIntakeServiceComponent.IntakeAckGenerator" Recurrence="600" Metadata="InvokeDirect=true" />
The value of 600 for Recurrence above means, the "Case Intake Ack" service is instantiated every 600 seconds (10 minutes) to perform the job.
The following configuration changes are optional:
<FolderConfiguration><MonitorFolders MonitorAllConfiguredFolders="true"><add FolderPath="\\172.16.38.154\Intake\US" Monitor="true" AlternatePath="C:\Intake\US"/></MonitorFolders></FolderConfiguration>
The FolderConfiguration enables you to have more granular control over what folders are monitored on what machines. This is particularly useful when the Intake folders are distributed across multiple machines and in many cases if these machines are not accessible from one server.
If the server machine on which Integrations component has been installed, has to monitor only a subset of the configured folders (configured in Argus Console), then set the attribute MonitorAllConfiguredFolders = "false"
When the value is set to false, each folder in the subset of folders that need to be monitored should be added as shown in the example above, using multiple <add /> entries. More info on each of the attributes:
FolderPath: The configured folder path, as specified in Sites UI in Argus Console
Monitor: true means this folder should be monitored, false means this folder should not be monitored.
AlternatePath: Alternate way of accessing the same folder path.
Verify the value of PROXY_AUTO_DETECT:
Log into SQL session on the database <database_name> and set up the enterprise context.
To verify that the value of PROXY_AUTO_DETECT, execute:
select value from CMN_PROFILE_ENTERPRISE where key = 'PROXY_AUTO_DETECT'
If this value is set to a character value, True or False, then update this value to a numeric value, 1 or 0.
To update the Network Proxy settings:
Log in to Argus Console.
From the System Configuration menu, select System Management.
Expand the Network Settings folder and click Proxy folder.
Check or uncheck the Auto Detect Proxy?, click Save.
Verify the Network Proxy settings again as mentioned in step 1. The value should be set to 1 or 0.
Verify the files installed on the server have not been modified or deleted from original installation.
Log in to the server as an Admin user.
Select Start > Control Panel.
Click Programs and Features.
Hover Argus Safety and right-click.
From the drop-down menu, click Change.
The Preparing Setup dialog box appears.
Click Modify and click Next.
Select Verify the current installation and click Next.
In the File Verification dialog box, click Next.