The Argus.xml file is generated during installation on the Argus Safety Web, but you can update this file after installation to add, update, or delete database entries. The file resides in the following directory:
<Argus Install Path>/ArgusWeb/ASP
The Argus.xml file contains the following type of xml tags:
XML Tag | Description |
---|---|
<ARGUS_DB> | Contains all databases supported by the Argus Web application.
Each database is specified as a separate XML tag - <DBNAME> with <ARGUS_DB> as parent tag. For example, for a database that is recognized as "Testing Database" in the Argus Web Login screen and whose alias in the Oracle TNSNAMES.ORA file is "TESTDB", the entry will be <DBNAME id="TESTDB">Testing Database</DBNAME>. |
If you update the Argus.xml file, you must restart the Internet Information Services (IIS) on the server for the changes to take effect.
The Argus.ini file is generated during installation on Argus Web and Transaction (AG) Server, but the user can update this file after installation.
To configure Argus.ini:
Select Start > Run.
In the Open field, enter argus.ini, and click OK.
Set the entries in the file as described in the Section 9.2.1, "Argus.ini Parameters".
Save the file.
Restart the Internet Information Services (IIS) on the server to reflect the changes.
With some exceptions, the parameters listed in the table are used by Argus Web as well as Argus Safety Service (AG Service or Transaction Server).
Parameters specific to the Web Server are:
MessageCachePath
Upload
Template
ArgusInstallPath
Pooling parameters
The Argus.ini File Parameters are described in the following table:
Section | Parameter | Sample Value | Description |
---|---|---|---|
Workstation | ArgusInstallPath | C:\Program Files\Oracle\ArgusWeb\ASP\ | Path of the location where the ASP files are placed.
For use with Web Server. |
Workstation | ArgusLogPath* | C:\Temp\ArgusLogs\ | Path of the root folder for ArgusLogs. |
Workstation | Cache* | C:\ArgusReports\PDFReports\ | Path for PDF Reports (Expedited/Periodic/Screen Prints etc.).
In case of multiple Web Servers, this is a shared path on the network. |
Workstation | MessageCachePath* | C:\ArgusReports\MessageCache\ | Shared path to save the system level cache such as data for LM tables, CMN Fields, etc.
In case of multiple Web Servers, this is a shared path on the network. For use with Web Server. |
Workstation | Upload* | C:\ArgusReports\UploadedLetters\ | Shared path for uploaded letters.
In case of multiple Web Servers, this is a shared path on the network. For use with Web Server. |
Workstation | Template | C:\Program Files\Oracle\E2BViewer\Templates\ | Location that stores the template and report files used to display CIOMS and MedWatch views.
For use with Web Server. |
Argus Server | SQLTimes | 1 | Enables the Argus Web application to start creating log files for all the SQLs that are fired. These log files are created in C:\Temp folder and can be used for debugging. |
Argus Server | Pool_Initial_Size | 3 | Refers to the DB Connection Pool Initial Size.
For use with Web Server. |
Argus Server | Pool_Maximum_Size | 120 | Refers to the DB Connection Pool Maximum Size.
For use with Web Server. |
Argus Server | Connection_Wait_Time | 3 | Refers to the connection wait time in seconds. An exception occurs if the system cannot obtain a DB connection in the given time.
For use with Web Server. |
Note:
* If any anti-virus software is running on Argus Web or Transaction (AG) server(s), it must be configured not to scan these Argus temp folders. Otherwise, it can lead to slower performance or unexpected errors on screens under heavy user load due to file locks by the anti-virus software.The system should have an OAM installation (Identity server, Access server, WebPass, Policy Manager).
User profiles should exist in the LDAP server as well as in Argus with the same credentials.
LDAP should be configured in the Argus Console.
The LDAP flag should be set to ON for the users in Argus Safety.
In OAM, navigate to Access Manager section > SSO Agents and click Create 11g Webgate.
Enter the following parameters and click Apply.
Name— Name of the WebGate
Access Client Password—Password of the WebGate
Host Identifier—Similar to name of the WebGate
In Security field, select Open.
Select Auto Create Policies.
In the Access Manager section, navigate to the Host identifiers.
From the Host Identifiers, select the newly created WebGate.
Enter Web Server Name, IP Address, and Load Balancer URL for:
- Argus Safety and Argus Insight with ports
- Argus Safety and Argus Insight without ports.
Click Apply.
Expand the list of Application Domains, and search the newly created WebGate.
Click the Resources tab, and add the following resource types.
Resource URL—/…/*
Type—HTTP
Host Identifier—The newly created WebGate
Protection Level—Protected
Authentication Policy—Protected Resource Policy
Authorization Policy—Protected Resource Policy
Resource URL—/
Type—HTTP
Host Identifier—The newly created WebGate
Protection Level—Protected
Authentication Policy—Protected Resource Policy
Authorization Policy—Protected Resource Policy
Click Apply.
Expand Authentication Policies and click Protected Resource Policy.
Click Add and search the newly created WebGate.
In the Resource URL field, add / and /…/* individually.
Click Apply.
Click the Responses tab and click the + button to add.
Enter the following parameters and click Apply.
Name
Type—Header
Value—$user.userid
Expand Authentication Policies and navigate to the newly created WebGate.
Click Protected Resource Policy.
Click Add and search the newly created Host Identifier.
In the Resource URL field, add / and /…/* individually.
Click Apply.
Click the Responses tab and click the + button to add.
Enter the parameters and click Apply.
You may need to perform certain installation maintenance tasks on the installed Argus Suite Solution Components.
Select Start > Control Panel.
Click Add or Remove Programs/Uninstall or change a program.
Right-click Argus Suite and from the drop-down menu, click Change.
The Argus Suite Solutions InstallShield Wizard opens the Preparing Setup dialog box.
Select Modify and click Next.
Select Update installed Argus Components and click Next.
In the Select Features dialog box, check the components to install and click Next.
Note:
Make sure the checkboxes for components that are already installed contain a checkmark. If the checkmark is cleared from the checkbox for an existing component, the component will be uninstalled.Refer to the relevant chapters in this Installation Guide for instructions for installing individual components.
When the installation process is complete, the Argus Suite Setup- Maintenance Complete dialog appears.
Click Finish.
Select Start > Control Panel.
Click Add or Remove Programs.
Right-click Argus Suite and from the drop-down menu, click Change/Remove.
The Argus Suite Solutions InstallShield Wizard opens the Preparing Setup dialog box.
Select Modify and click Next.
In the Select Features dialog box, uncheck the components to uninstall and click Next.
The Argus Safety Components Installer will uninstall the selected components.
Follow the on-screen instructions to uninstall the components.
Select Start > Control Panel.
Click Add or Remove Programs.
Right-click Argus Suite and from the drop-down menu, click Change/Remove.
The Argus Suite Solutions InstallShield Wizard opens the Preparing Setup dialog box.
Select Remove and click Next.
In the Confirm Uninstall dialog box, click OK.
The Argus Safety Components Installer uninstalls the required component(s).
Follow the on-screen instructions to uninstall the components.
By default, the Argus Safety logs files are placed in the ”C:\temp” folder (default temp directory of Argus Safety). You must make sure that the user under which the Argus Safety applications are running has access to this directory.
If you have a different ”Temp” directory, change the temp directory path in the following files:
Background Processes (AG Server)
<Argus Install Path>/Argus Safety/AGProc.config
<Argus Install Path>/Argus Safety/Service.config
<Argus Install Path>/Argus Safety/RelsysWindowsService.exe.config
<Argus Install Path>/ArgusWeb/ASP/Web.config
<Argus Install Path>/ArgusWeb/Bin/Argussvr2.config
<Argus Install Path>/ArgusWeb/ASP/Argus.Net/Web.config
<Argus Install Path>/ArgusWeb/ASP/Argus.Net/Bin/RelsysWindowsService.exe.config
<Argus Install Path>/ArgusWeb/ASP/ Argus.Net/Bin /Service.config
<Argus Install Path>/ArgusWeb/ASP/Integrations/Web.config
Note:
It is recommended that you use the local server path rather than the network share path.You must back up the following configuration files before proceeding with the application upgrade. All system configuration (.config) files will be overwritten by this upgrade and your manual configuration changes will be lost. These files may be stored on multiple servers, depending on components selected at the time of the Argus installation (Web Server, integration server, transaction server, and so on). The directory structure of the file, however, remains constant.
Commonly modified configuration files are:
.\ArgusWeb\ASP\Argus.NET\bin\Intake.config
.\ArgusWeb\ASP\Argus.NET\bin\RelsysWindowsService.exe.config
.\ArgusWeb\ASP\Argus.NET\bin\Service.config
.\ArgusWeb\ASP\Argus.NET\web.config
.\ArgusWeb\ASP\ArgusConsole\web.config
.\ArgusWeb\ASP\Integrations\Service.config
.\ArgusWeb\ASP\Integrations\Web.config
.\ArgusWeb\ASP\web.config
.\ArgusWeb\Bin\Argusvr2.config
.\ArgusWeb\Bin\Argusvr2a.config
.\Argus Safety\AGProc.config
.\Argus Safety\Intake.config
.\Argus Safety\RelsysWindowsService.exe.config
.\ArgusSafety\Service.config
.\DBInstaller\ArgusDBInstall.exe.config
.\ESMMapping\ESMapping.exe.config