Navigate to the Argus Safety Report Server.
Go to C:\Windows and open the argus.ini file.
Delete references to the ReportServerUser, ReportServerPassword and ReportServerPriority.
Update the entry for ReportServer to HTTP://Localhost
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>. |
| <LICENSE_KEY> | Contains the License Key value for the Argus application.
Do not update this key unless Oracle Customer Support instructs you to do so. |
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 10.3.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 Table 13-2 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
Timeout
DB Connection
Pooling parameters.
Parameters specific to the Transaction (AG) Server are:
PrintRunTime
The Argus.ini File Parameters are described in the following table:
| Section | Parameter | Sample Value | Description |
|---|---|---|---|
| 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. |
| Workstation | AcrobatReaderPath | C:\Program Files\Adobe\Acrobat 7.0\Acrobat\Acrobat.exe | Path to the Acrobat Reader exe file. |
| Workstation | HELP | C:\App\Oracle\Documentation\ | Base folder where all the files related to various modules of Argus are placed. |
| Workstation | ArgusInstallPath | C:\Program Files\Oracle\ArgusWeb\ASP\ | Path of the location where the ASP files are placed.
For use with Web Server. |
| Workstation | SCANNED_IMAGES | C:\Temp\Scanned_Images | Location of files that are used by the "New Case from Image" functionality. |
| PDFReports | TempFileDeleteInterval | 1 | Specifies how often the Argus Report Service should run to check for files to delete.
By default, this service will delete files from paths specified for "Cache" and "Upload" parameters described above. The unit is in hours. The default value is 1. |
| PDFReports | HoursBeforeDelete | 24 | This key is used by the Argus Report Service. This key specifies in hours, how old the file must be before it gets deleted. By default, this service will delete files from paths specified for "Cache" and "Upload" parameters described above. The default value is 1. |
| 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_Time_Out | 120 | Refers to the time-out time in seconds. The connection times out if it is idle for the given time.
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. |
| Argus Server | PeriodicRptMaxRunTime | 60000 | Refers to the setting in the Argus.ini file that allows you to override the default Argusvr2a EXE timeout setting to approximately 16 hours (60000). |
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.Prerequisites:
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.
To install SSO on the OAM:
Navigate to the System Configuration tab of OAM and select the New OAM 10g Webgate link.
The Create OAM 10g Webgate screen appears.
Enter the following parameters and click Apply.
Name— Name of the WebGate
Access Client Password—Password of the WebGate
Note:
Refresh the Host Identifier list to view the newly created Webgate within the Policy Configuration tab.Enter the following parameters and click Apply.
Primary Cookie Domain—FQDN of the machine where you will install WebGate, prefixed by a period.
For example, .idc.<example.com>. Note the . (dot) before the FQDN.
Preferred Host—IP Address of the Argus Web Server where you will install WebGate
Expand the list of Application Domains and under this, expand the newly created WebGate.
Double-click Resources.
To create the resource type with the correct host identifier, click Create icon.
(The Create icon is displayed in the Search Results section, with the + symbol in red).
Expand the Authentication Policies under the newly created WebGate and double-click the Protected Resource Policy.
Select the Responses tab and click the + button to add the Name, Type, and Value for the responses.
Select the Constraints tab and click the + button to add the Name, Type, and Class for the constraints.
The possible values for Constraint Type to access the Argus Safety Services where WebGate is installed are:
- Allow
- Deny
Note:
If no constraint is added, all the users configured on the LDAP Server will have access to the Argus Safety Services where WebGate is installed.You may need to perform certain installation maintenance tasks on the installed Argus Safety Solution components.
Select Start > Control Panel.
Click Add or Remove Programs/Uninstall or change a program.
Right-click Argus Safety and from the drop-down menu, click Change.
The Argus Safety InstallShield Wizard opens the Preparing Setup dialog box.
Select Modify and click Next >.
Select Update installed Argus Components and click Next >.
In the Customer Information dialog box, enter following parameters 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 Safety Setup- Maintenance Complete dialog appears.
Click Finish.
Select Start > Control Panel.
Click Add or Remove Programs.
Right-click Argus Safety and from the drop-down menu, click Change/Remove.
The Argus Safety InstallShield Wizard opens the Preparing Setup dialog box.
Select Modify and click Next >.
In the Customer Information dialog box, enter the parameters 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.
Note:
If a Locked File Detected dialog box appears, select Don't display this message again and click Reboot.Select Start > Control Panel.
Click Add or Remove Programs.
Right-click Argus Safety and from the drop-down menu, click Change/Remove.
The Argus Safety 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 screen instructions to uninstall the components.
Note:
If a Locked File Detected dialog appears, select Don't display this message again and click Reboot.
If a Shared File Detected dialog appears, select Don't display this message again and click Yes.
If a ReadOnly File Detected dialog appears, select Don't display this message again and click Yes.
The easyPDF component is required for printing PDF reports and for use by Interchange features such as transmitting E2B attachments.
The domain account created during the installation of either Argus Web Server, Argus Safety Services or Interchange Services, will be required to continue with the following steps.
Prerequisites:
The domain account created is part of the local Administrator Group on the server being setup.
You must Log in to the server being setup with the domain account at least once to initialize the account, including the printer driver setting, or Argus Safety will not be able to function correctly.
To configure the Windows service settings:
Log in to the computer as the defined domain account.
Select Start > Control Panel > Administrative Tools > Services.
In the Services dialog box:
Double-click the BCL easyPDF SDK 7 (or 6) Loader.
Click the Log On tab.
Enter the parameters.
Click the General tab.
From the Startup type drop-down list, select Automatic and click OK.
From the Services window, start the BCL easyPDF SDK 7 (or 6) Loader.
Close the Services window.
If you are working on a client machine, you must make sure that you enable or check the Display PDF in Browser setting in Adobe Acrobat Reader.
If this setting is not enabled, PDF documents will not appear in the Argus Safety user interface. This might cause some information status pop-ups to hang on the client machine.
When printing the Argus Safety reports with Adobe Acrobat, make sure the Page Scaling option in the Print dialog box (File > Print) is set to Shrink to Printable Area.
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