This chapter provides checklists and procedures for verifying that Argus Safety is installed correctly.
Oracle 12c is installed.
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
Select Control Panel > Administrative Tools > Services.
Double-click Argus Safety Windows Service.
The Argus Safety Windows Service Properties (Local Computer) dialog box appears.
Click the Log On tab.
Click This Account.
Enter the credentials.
Click OK.
Right-click the Argus Safety Windows Service and select Restart.
Run the Argus Installer and select the option Integrations. Complete the setup.
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, C:\Program Files (x86)\Oracle\Argus\Argus Safety. For example:
<InterfaceSchemas><add InputXSD="C:\Program Files (x86)\Oracle\Argus\Argus Safety\Integrations\XSD\v1.0\Base.xsd" /><add InputXSD="C:\Program Files (x86)\Oracle\Argus\Argus Safety\Integrations\XSD\v1.0\DataOperation.xsd" /><add InputXSD="C:\Program Files (x86)\Oracle\Argus\Argus Safety\Integrations\XSD\v1.0\Dictionary.xsd" /><add InputXSD="C:\Program Files (x86)\Oracle\Argus\Argus Safety\Integrations\XSD\v1.0\Case_Intake.xsd" OutputXSLT="C:\Program Files(x86)\Oracle\Argus\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 21.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 ="recepient@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.
the properties in the IIS PDFReports virtual directory are correct.
for Load Balanced Environments only
the path under the Virtual Directory is set to Share Path.
the correct <Domain User> is in the Connect As option.
the Read and Write options are checked.
there is no Red X on the PDFReports folder.
you can right-click PDFReports and click Browse.
you can create a temp file and delete it after browsing.
for PDFReports:
Enable Content Expiration in HTTP Headers is unchecked
Custom HTTP Headers in HTTP Headers does not have a value of Cache-Control
the properties in the IIS UploadedLetters virtual directory are correct.
for UploadedLetters: Enable Content Expiration under HTTP Headers is unchecked.
Enable Content Expiration under HTTP Headers is unchecked
Custom HTTP Headers under HTTP Headers does not have a value of Cache-Control
the values on the Directory Security tab under the Argus Safety Website Properties are correct.
Click Edit and verify that:
the correct <Domain User> and password are used for Anonymous Access.
Note:
If you have IIS 7.0, you need to manually add Office 2007 MIME Types on the Web Server. IIS 7.0 has these MIME types by default. Refer to the following Microsoft links for required steps:Register the 2007 Office system file format MIME types on servers:
http://technet.microsoft.com/en-us/library/ee309278.aspx
Configure MIME Types on IIS 7.0:
Open Internet Information Services (IIS) manager from Control Panel > Administrator Tools.
Browse to the Argus Safety Web website.
Select the PDFReports Folder.
Double-click HTTP Response Headers.
Make sure that there is no value Cache Control header.
Click Set Common Headers.
Make sure that Expire Web Content is unchecked.
Verify the same settings for the UploadedLetters folder.
Click Argus Safety Web.
Under Actions, click Basic Settings.
Make sure that the website is configured to run under a domain account.
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 >.
Log in to Console and verify Documentum is configured in Argus Safety.
Refer to the Oracle Argus Safety Administrator Guide to set up Documentum.
Log in to SQL Session on the database <database_name>.
To verify that the value to enable the Periodic Report Documentum interface is set to 1, execute:
select * from cmn_profile where key ='ENABLE_DOCUMENTUM_PERIODIC'
To verify that the correct user has been configured in Documentum, execute:
select * from cmn_profile where key = 'DOCUMENTUM_LOGIN'
This value is case sensitive and must match the Documentum login.
To verify that the password value will be encrypted, execute:
select * from cmn_profile where key = 'DOCUMENTUM_PASSWORD'
Set this password again from the Case Form Configuration in Argus C/S. Make sure the password matches the password for the user identified in Step 4. The password is case sensitive.
To verify that the following information is correct, execute:
select * from DOCUMENTUM_PUSH_INFO
Note:
Rows will only exist if custom attributes are inserted as required by the customer.TYPE_NAME (<DocumentumType>) is the correct name as specified in Documentum. (This is the table name in Documentum.)
All the Attribute names specified here exist in the Documentum table.
The SQL_CONTENT SQLs are correct and run without any error when the parameters are filled in. (No Syntax errors.)
The ATTRIBUTE_TYPE matches with the one defined in the Documentum table.
Log in to the following servers to verify that the Documentum DFC Runtime Environment is installed on the server. This can be verified through Add/Remove Programs.
AG Service machine - <ServerName>
Argus Web Server - <ServerName>
Interchange Service Server - <ServerName>
Open Documentum.
Create the following types in Documentum:
Attachments
Reports
Make sure the type names are the same as those in the TYPE_NAME column in the DOCUMENTUM_DISPLAY_INFO table in Argus Safety.
Create case_num and user_fullname as Attributes for both Types.
Create submission_succeed as Attribute in the Type being used for reports.
Create all values in the ATTRIBUTE_NAME column in DOCUMENTUM_DISPLAY_INFO table in Argus Safety as corresponding Attributes of the Types through Documentum Administrator.
Note:
IUSR_<Machine> accounts must be given full access to the shared folder in the DFC install path where DFC.dll resides.Documentum can be implemented on an Argus Safety system in the following ways:
Documentum can be successfully run on an Argus Safety system if the entire environment comprises machines with fully qualified domain names for that environment.
If the actual domains are not present, you can still run Documentum even with minimal security configuration by implementing a workaround, as follows:
Go to the DFC.config file on the Web Server and change its dfc.registry.mode setting.
The default setting is: dfc.registry.mode=windows
Change this setting to: dfc.registry.mode=file
This change ensures that Documentum can run even with minimal security configuration.