This chapter includes:
You can install Forms Servers and Reports Servers to suit your needs. If you choose to have Reports Servers on computers that do not have a Forms Server installation, you must configure both computers to share a directory on the Forms Server computer.
Note:
To ensure high availability of the Reports Server, you can set up and use more than one Reports Server on a subnet and they can access each other. For more information see the Oracle Clinical Administrator's Guide.The Oracle Application Server technology stack and Oracle Clinical Front End must be installed before you install the Oracle Clinical Reports Server. See Chapter 8, "Install and Configure the Oracle Application Tier" for installation instructions.
You must have the following information ready to enter in the Installer screens:
Home Details: Enter the following:
Name: OPA_HOME
Path: c:\opapps52
Your Oracle Fusion Middleware home directory; for example:
C:\Oracle\Middleware\Oracle_Home
Your OPA home directory; for example:
C:\opapps52
WebLogic username and password
Report Server name
Report Server output directory
Adobe Reader location; for example:
C:\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.exe
If you select to store the DCIF images locally, you need the local DCIF images directory. Else, you need the location of the shared directory.
Restart the computer.
The WebLogic FRDomain Admin Server must be running when you install the Reports Server.
At the DOS command prompt, do one of the following:
Go to ORACLE_HOME\user_projects\domains\FRDomain\bin and run the startWebLogic.cmd.
Go to C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Oracle FMW 12c Domain-FRDomain - 12.2.1.2.0 and run Start Weblogic Admin Server.
Go to ORACLE_HOME\user_projects\domains\FRDomain\bin and run startNodeManager.cmd.
Follow these instructions to deploy the Oracle Clinical Reports Server onto the application tier installation.
Note:
If you run Patient Data Reports from a Reports Server, install Acrobat Reader before installing the Oracle Clinical Reports Server. The Installer detects the Reader's location and automatically configures the registry.To install the Oracle Clinical Reports Server components:
Log in as a user with system administrator privileges.
Navigate to the location where you downloaded and extracted the software in Section 1.7, "Download the Software".
Run the following file as an administrator:
Disk1\install\setup.exe
The Installer opens to the Welcome screen.
Note:
See "Use the Silent Installer (Optional)" for instructions for running the Installer as a file with pre-entered parameter values.Note:
Although there is a button for deinstalling products on the Welcome screen, Oracle does not support using the Installer to deinstall Oracle Clinical or Oracle Clinical Remote Data Capture (RDC) Onsite.Select a Product to Install: Select Oracle Clinical Report Server 5.2.0.0.x.
Follow the instructions on the installation screens.
Follow instructions on screen, entering the information you have gathered; see Section 10.1, "Gather Required Information".
Summary: The Summary screen provides information about the global settings, languages, space requirements, and products for this installation.
Review the installation details to verify that they are correct. To revisit earlier installation screens and make changes, click Back.
When you are ready to continue, click Install.
Install: The Installer copies the files onto the server, completes the setup and configuration tasks, and generates a log file of this installation.
In addition, the Install screen displays the location of the log file that records the results of the installation activities for this session. Make a note of this information so you can view the log file after the installation.
End of Installation: The End of Installation screen reports whether the installation was successful. Please check the install logs if any errors are displayed.
When you have finished reviewing the installation information, click Exit.
Review the generated installation log file, installActionstimestamp.log, for errors.
This is the name of the most current log file. Earlier files have a timestamp appended to the name.
Location: \Oracle\Inventory\logs
For example:
C:\Program Files\Oracle\Inventory\logs
Work with Oracle Support, if necessary, to resolve any errors.
Note:
If you have already installed the Oracle Reports Developer Patch 22334822, ignore instructions in this section.Download the patch from My Oracle Support.
To apply the patch, follow instructions in the patch release notes.
To ensure that all configuration changes are initialized:
Restart the computer before you continue with the next task in the installation process.
Perform these Reports Server file viewing tasks once for each Oracle Clinical location.
If your Oracle Clinical environment includes any standalone Reports Servers and/or File Servers, select the single computer where you will locate your Reports Server root directory. The directory can reside on the Forms Server, on any of the Reports Serves, or any other computer. Otherwise, you will locate the Reports Server root directory on the single computer comprising your entire Oracle Clinical installation.
Create the Reports Server Root directory, making sure it is accessible by the user that started up the auto process; see Section 9.9, "Set Up Automatic Startup".
This step is not required if you are installing the application tier on a single computer.
Make the Reports Server UNC sharable, and grant the administrator account read and write access to this directory.
To share the Reports Server root directory on Windows with the administrator account:
Use Windows Explorer to select the Reports Server root directory.
Right-click on the folder and select Properties.
Click the Sharing tab.
Select Shared This Folder, and then enter a value in the Share Name field.
Click OK to save your changes.
Tip:
The Microsoft Windows Universal Naming Convention (UNC) for any Reports Server log directory cannot exceed 35 characters.The UNC syntax is:
\\computer\sharename\subdirectory
For example, if the computer name is oclfsrv1, and the share name is opareportout, and the report log is stored in a subdirectory user under this shared directory, then the UNC is:
\\oclfsrv1\opareportout\user
This works as long as user does not exceed eight characters. To have longer names for user, shorten the share name.
Both the Reports Server and the Oracle Clinical application server must have read/write access to the directory (\rdc\temp) on the application server used to write temporary files during the DCI form generation process.
If you have any standalone Reports Servers, they must also have access to this directory.
On the Oracle Clinical (Forms) Server:
Confirm that the OUI has the specified values for the registry settings OPA_XMLTEMP_UNC and OPA_XMLTEMP_HTTP. During the installation, if you correctly indicated that there is a standalone report server, the value of the key(s) is set to:
OPA_XMLTEMP_UNC:
C:\opapps52\html\rdc\temp
OPA_XMLTEMP_HTTP:
https://<serverName>:port/opa52/rdc/temp
To provide access to the remote Report Server, share the directory with the share name "RDC", providing read/write privileges to the domain/account on the report server.
On the Reports Server used in DCI Form Generation
By default, OUI will have updated RWSERVER.conf, specifying a value of %OPA_HOME%\oc;%OPA_HOME%\*;%REPORTS_LOG_DIR%\* under folder access.
For example:
<folderAccess> <read>%OPA_HOME%\oc;%OPA_HOME%\*;%REPORTS_LOG_DIR%\*</read> <write>%OPA_HOME%\oc;%OPA_HOME%\*;%REPORTS_LOG_DIR%\*</write> </folderAccess>
Map a drive to the RDC share on the application server.
Update the registry values. For example:
OPA_XMLTEMP_UNC:
z:\rdc\temp
The Z drive is mapped to \\SharedAPPSERVERNAME\OPA_HOME\html.
OPA_XMLTEMP_HTTP:
https://servername(same as Z drive):port/opa52/rdc/temp
If the only report server that you use to generate DCI forms co-exists on the same computer with the application server, there is no need to share the xmltemp directory and the path specification can be a simple local directory name, such as,
C:\opa_home\html\rdc\temp
If you run the PDR, and you send the output directly to a printer:
Set value for the RDC_PDF_PRINT_TOOL key.
The value assigned to the RDC_PDF_PRINT_TOOL key determines the location of the Adobe Acrobat or Reader executable, which allows users to run PDF patient data reports with "PRINTER" specified as the output type. This value must be in the form:
"<acrobat-reader_path>" /t
Note that the double-quotation marks around the path and the "/t" switch are required. A typical example of a value is:
"C:\Program Files\Adobe\Acrobat 6.0\Acrobat\Acrobat.exe" /t
In addition to setting this key correctly, ensure that the Adobe Acrobat or Reader application is running on the Reports Server prior to users initiating this type of report job, that is, a job that specifies the output type as "PRINTER".
For each Reports Server that you install, you must edit reference codelists in Oracle Clinical to specify the values for the Reports Server.
To set the Reports Server values:
Start Oracle Clinical.
Navigate to Admin, Reference Codelist, and then Local Codelist to open the Maintain Reference Codelists form.
Query for REPORT_SERVER in the Name field.
Complete the Short Value and Long Value fields as follows:
For each Short Value listed in Table 10-1, enter in the Long Value field the connection string of the Reports Server that you want to use as the default for the specified function.
For each additional, non-default Reports Servers, add a row to the reference codelist. Specify a unique name in the Short Value field and the connection string in the Long Value field.
Table 10-1 REPORT_SERVER Local Reference Codelist Values
| Short Value | Enter in Long Value Field |
|---|---|
|
REPORT_SERVER |
The connection string for the Reports Server you want to use as the default for Oracle Reports. |
|
JOB_SET_SERVER |
The connection string for the Reports Server you want to use as the default for job sets. |
|
PSUB_SCHEDULER |
The connection string for the Reports Server you want to use as the default for PSUB jobs. |
Click Save.
To test that the Reports Server can create printouts and files:
Start Oracle Clinical.
Navigate to Admin, Admin Reports, and then Reference Codelist. The Report Reference Codelist submission screen opens.
Click the Reference Codelist Name field, and enter OCL_STATE.
Print the report:
Click the Job Details button.
Change the Output Type to PRINTER.
Examine the printer's path to see if it is correct.
Click Submit Job. You receive a status prompt. Close the prompt to return to the Submission screen.
Click Job Status to check the progress of your print job. Look for the printout from your printer.
Print the report to file:
Return to the Report Reference Codelist submission screen.
Click the Reference Codelist Name field, and enter OCL_STATE.
Click Job Details.
Change the Output Type to FILE.
Click Submit Job. The system displays a status prompt. Close the prompt to return to the Submission screen.
Click Job Status.
Check its status in the Execution Status field.
Click View Output. The system displays a path location prompt.
Click OK. The Report Server processes the file and converts it to the selected format. If successful, the file then opens in a separate window.
Oracle recommends setting up the server so that the Node Manager automatically restarts services when necessary. If you are installing this on a machine with the Oracle Clinical Front End, you will have done this as part of executing Section 9.9, "Set Up Automatic Startup".
If this is a standalone reports server, follow the same instructions except, in script autostartfrdomainscript.py located in opa_home\config, comment out the following line:
start ('WLS_FORMS')
If you are not installing TMS, also comment out the following line in script autostartopadomainscript.py located in opa_home\config:
domainName='OPADomain' domainDir='your_middleware_home/USER_P~1/domains/OPADomain' nmConnect(userConfigFile=configfile, userKeyFile=keyfile, nmPort=port, domainName=domainName,domainDir=domainDir,nmType='ssl') nmStart('Admin Server') connect(userConfigFile=configfile, userKeyFile=keyfile) nmStart('Server.Domain_OPA_1')