7 Customizing RDC on the Application Server

This chapter describes ways to customize RDC by editing files available on the RDC application server.

This chapter includes the following topics:

Section 7.1, "Modifying Files on the Application Server"
Section 7.2, "Creating a Launch Page, Button, or Link for RDC"
Section 7.3, "Customizing the Reset Password Link"
Section 7.4, "Customizing Branding Images in RDC"
Section 7.5, "Customizing the Contact Us Link"
Section 7.6, "Customizing the Change Password Link"
Section 7.7, "Customizing the Electronic Signature (Approval) Warning Message"
Section 7.8, "Customizing the Logout Message"
Section 7.9, "Setting the User Session Timeout Value"
Section 7.10, "Setting the Maximum Number of Rows Fetched"
Section 7.11, "Storing Custom Web Pages"
Section 7.12, "Storing the DCIF Images"
Section 7.13, "Customizing the Single View of the Patient Casebooks Page"
Section 7.14, "Hiding Unplanned Visit Buttons in RDC Onsite"

7.1 Modifying Files on the Application Server

You can use several system files on the application server to customize settings for RDC. Some of the system files that you can modify include:

In the RdcLogos.properties file, you can define a custom URL for the Reset Password link and the Contact Us link in the RDC application. You can also specify a co-branding logo.

The RdcLogos.properties file is located in OPA_CONFIG_FOLDER path. This path comes from registry entry opa52 under HKEY_LOCAL_MACHINE > Software > Oracle.
In the RdcTexts.properties file, you can customize the Change Password link, customize the logout message, and modify the text of approval warning messages.

The RdcTexts.properties file is located in OPA_CONFIG_FOLDER path. This path comes from registry entry opa52 under HKEY_LOCAL_MACHINE > Software > Oracle.
In the rdcConfig.properties file, you can set the session timeout value, specify the maximum number of rows (data records) to retrieve, and enable server profiling.

The rdcConfig.properties file is located in the OPA_CONFIG_FOLDER path. This path comes from the registry entry opa52 under HKEY_LOCAL_MACHINE > Software > Oracle.

For more information on modifying the system files, see Chapter 15, "Collecting Debug Data."

Before modifying a system file, you must stop WebLogic Admin Server. See Section 1.5, "Stop the WebLogic Admin Server" for more information.

7.2 Creating a Launch Page, Button, or Link for RDC

This section provides instructions for customizations such as:

Section 7.2.1, "Creating or Customizing a Launch Page to Use Provided Scripts"
Section 7.2.2, "Customizing the Remote Data Capture URL"
Section 7.2.3, "Adding Custom Text to the RDC Onsite Login Page"

7.2.1 Creating or Customizing a Launch Page to Use Provided Scripts

Oracle recommends using the scripts provided here to control when and how the RDC Login page opens, to prevent users from having problems in the RDC application resulting from:

Using the browser's Back button—Sample Java Script for Launching in a New Window without Tool or Menu Bar suppresses the browser toolbar, making the Back button unavailable.
Turning on Internet Explorer's Compatibility View—Sample JavaScript for Checking if Compatibility View Is On detects if Compatibility View is turned on and if it is, does not open the application and displays a message telling the user to turn it off.
Opening more than one RDC session to the same application server or from the same parent window—the scripts prevent this.

To use these scripts in your launch page:

Place the script from Section 7.2.1.1, "Sample Java Script for Launching in a New Window without Tool or Menu Bar" in a file called Launch.js.
Place the script from Section 7.2.1.2, "Sample JavaScript for Checking if Compatibility View Is On" in a file called IeCompatCheck.js.
Place the scripts at the same location as the Launch page or in a folder (called JS in the example code below) in the same location as Launch page. The shipped Oracle Clinical Launch page, launch.htm, is located in opa_home/html.

Create an HTML page that contains a button or link to RDC that invokes the functions in the JavaScript files or add code to the shipped Launch page or an existing website to do the same.

Put the code referencing the scripts near the top of the HTML page; for example:

 <title> Launch RDC </title>
  <script type="text/javascript" src="JS/IeCompatCheck.js"></script>
  <script type="text/javascript" src="JS/LaunchJS.js"></script>
 
 </head>
<body>

Add button code or link code as follows, and see Section 7.2.2, "Customizing the Remote Data Capture URL."

<script language="JavaScript">
document.write('<FORM>');
document.write('<input type="button" value="RDC" onclick="return launch(event,\'../rdcadfsrnd/faces/Login\',\'RDC\')" class="loginButton"/>');
document.write("</FORM>");
</script>  

<noscript>
<a onclick="return launch(event,'../rdcadfsrnd/faces/Login',\'RDC\')" href="#">Launch RDC</a>
</noscript>

7.2.1.1 Sample Java Script for Launching in a New Window without Tool or Menu Bar

function launch(event,url,windowname){
            if(detectIECompatibility(event)){
                cancelEvent(event);
                return false;
            }
            if(!!!windowname){
                windowname="_blank";
            }
            window.open(url,windowname,'location=0,resizable=1,toolbar=0,titlebar=1,status=1,scrollbars=1,menubar=0','true');
}

7.2.1.2 Sample JavaScript for Checking if Compatibility View Is On

The following script checks if compatibility view is on and if so, displays a message asking the user to turn it off.

function IECompatDetect(){       
        this.isCompatOn = function(){
                    var ua = navigator.userAgent;
                    var on = false;
                    for(var index=0; index< this.ieUAProps.length; index++){
                        var ieProp = this.ieUAProps[index];
                        if(ua.search(ieProp.layoutEngine) == -1){
                            continue;
                        }
                        if(ua.search(ieProp.browser) == -1){
                            on = true;
                            break;
                        }                   
                    }
                    return (on);
                };       
        this.ieUAProps= [
                        {
                            browser: 'MSIE 10',
                            layoutEngine: 'Trident/6'
                        },
                        {
                            browser: 'MSIE 9',
                            layoutEngine: 'Trident/5'
                        },
                        {
                            browser: 'MSIE 8',
                            layoutEngine: 'Trident/4'
                        }
                    ]
 
    }
function cancelEvent(e){
    var event = e || window.event;
    if(event == null){
        return;
    }
    if(event.preventDefault){
        event.preventDefault();
    }else{
        event.returnValue=false;
        event.cancelBubble=true;
    }
}
 
function compatCheck(event,isCompatRequiredToBeOn){
    var compatOn=(new IECompatDetect()).isCompatOn();
    if(compatOn && !isCompatRequiredToBeOn){
        cancelEvent(event);
        alert("Please turn off IE's Compatibility View. Go to Tools->Compatibility View/Compatibility View Settings to do so.");   
    }
    if(!compatOn && isCompatRequiredToBeOn){
        cancelEvent(event);       
        alert("Please turn on IE's Compatibility View. Go to Tools->Compatibility View/Compatibility View Settings to do so.");   
    }
    return compatOn;
}
function detectIECompatibility(e){   
    return compatCheck(event,false);   
}
 
//Call on load
(function(){
    compatCheck(null,false);
})();

7.2.2 Customizing the Remote Data Capture URL

You can add optional parameters to the RDC URL to change the behavior at run time. The format of the URL is as follows:

https://server.domain/rdcadfsrnd/faces/Login?setUpDone=Y &parameter1=value1&parameter2=value2

Table 7-1 describes the parameters that you can use in the URL.

Table 7-1 RDC URL Parameters

Parameter	Description	Example
`setUpDone`	To display the Middle Tier server name in the lower left corner of the RDC Surround (all user interface pages except the Data Entry window) and in the RDC Launch page, set this parameter to Y. If you don't want to show the Middle Tier server name, remove this parameter or set its value to `N`.	`setUpDone=Y`
`db`	Specifies the database to connect to for RDC. If not specified, the application connects to the default database. Use this parameter to connect to a database that is not set up as the default. See Appendix A, "Setting Up Database Connections" for information about specifying the default database and ensuring that your application server can access any database you specify with this parameter.	`db=mydb`
`debug`	Specifies whether to enable debugging and logging. all — Debugs all modules. surround — Debugs only the RDC application pages. de — Debugs only the Data Entry window. Oracle Support may ask you to use this parameter to diagnose issues. See Chapter 15, "Collecting Debug Data" for more information.	`debug=all`
`deparams`	Oracle Support may ask you to use this parameter to diagnose possible performance issues by profiling HTML requests and responses using a value of profile. The value xhrd is reserved for possible tuning purposes.	To be provided by Oracle Support
`display_descpId`	Specifies whether RDC displays the discrepancy identifier in an additional column on the Review Discrepancies page and in the Discrepancy Details window. See Chapter 15, "Collecting Debug Data" for more information.	`display_descpId=Y`
`display_docnum`	Specifies whether RDC displays the document (CRF) number in an additional column: On the Review CRFs page On the Review Discrepancies page In the Discrepancy Details window On the Review Investigator comments page See Chapter 15, "Collecting Debug Data" for more information.	`display_docnum=Y`
`mode`	Specifies the mode in which the RDC application runs. T — Runs in test mode. P — Runs in production mode. Production mode is the default, if not specified.	`mode=T`
`sqlTrace`	Specifies whether to enable SQL tracing. 1 — Enables SQL tracing. Any other value — Disables SQL tracing. Oracle Support may ask you to use this parameter to diagnose possible SQL issues. See Chapter 15, "Collecting Debug Data" for more information.	`sqlTrace=1`
`showMachineName`	Indicates how to display the Middle Tier server name. You set this parameter along with `setUpDone`, in the rdcconfig.properties file. You can specify values as follows: Y: Display the complete name of the Middle Tier server. n, where n is a number: Display the first n characters of the Middle Tier server name. Anything else: Displays the first four characters of the Middle Tier server name if `setUpDone=Y`.	`showMachineName=15`

7.2.3 Adding Custom Text to the RDC Onsite Login Page

You can show a disclaimer of informative text on the RDC Onsite login page.

To add custom text to the RDC Onsite login page:

Open the file RDCText.properties in a text editor.
Look for the prompt.login.disclaimer parameter and add your text as the value for this parameter. You can add up to 300 characters.
Save your changes and close the file.
Open the file RDCLogos.properties in a text editor.
Look for the show.Disclaimer parameter and set its value to true.
Save your changes and close the file.
For these changes to take effect, restart the application server.

7.3 Customizing the Reset Password Link

By default, the Login page for the RDC application does not include the Reset Password link.

You can:

Choose to show the Reset Password link on the Login page
Specify a URL for your own reset password page or use the RDC Onsite Reset Password utility

7.3.1 Requirements for Using the RDC Onsite Reset Password Utility

The RDC Onsite Reset Password utility uses functionality in the Oracle Thesaurus Management System (TMS). Therefore, to make use of the reset password utility:

TMS must be installed, either on the RDC application server or on another accessible server.
The TMS user IDs must match the RDC user IDs.
Email addresses for all RDC users must be specified in TMS using the TMS user interface. If users click the Reset Password link and their user IDs and e-mail addresses are not specified in TMS, the process fails and RDC displays an error message.

For more information on creating user IDs and specifying e-mail addresses in TMS, see the Oracle Thesaurus Management System User's Guide.

7.3.2 Resetting versus Changing Passwords

If a user attempts to log in to RDC with a valid but expired password, RDC redirects the user to the Change Password page. The password can be changed strictly through the user interface, without e-mail or involvement of TMS.

See Section 7.6.1, "Changing the URL and the Name for the Change Password Link" for more information.

7.3.3 Configuring the Reset Password Link

You use the RdcLogos.properties file to change the default settings for the Reset Password link.

To configure the Reset Password link:

Navigate to the OPA_CONFIG_FOLDER. The folder path is determined by the registry entry opa52, found under HKEY_LOCAL_MACHINE > Software > Oracle, for example:

C:\opapps52\config
Open the RdcLogos.properties file with a text editor.
Find the following line in the file and set the value to true to display the Reset Password link on the Login page:

image.ResetPasswordUrlRendered=true
Specify the Reset Password page that displays when the user clicks the Reset Password link. You can specify your custom Reset Password page or you can use the RDC Onsite Reset Password page.
- To specify your custom page, find the following line in the file and set the value to the URL for your Reset Password page:
  
  image.ResetPasswordUrl=Custom_URL
- The RDC Onsite Reset Password page requests the username and then sends a new password by email to their registered email address. By default, the link for this page is not enabled. You can enable the link to this page and configure the email functionality. To use the RDC Onsite Reset Password page:
  1. Make sure the following line is not set to a value:
    
    image.ResetPasswordUrl=
  2. Verify that the following value is set as indicated below:
    
    image.ResetPasswordUrlRendered=true
  3. Adjust for an SSL or non-SSL authentication:
    
    If the email server uses SSL authentication, set values as follows:
    
    resetPassword.email.smtp.auth=true
    
    resetPassword.email.smtp.socketFactory.class=javax.net.ssl.SSLSocketFactory
    
    If the email server does not use SSL authentication, set values as below:
    
    resetPassword.email.smtp.auth=false
    
    resetPassword.email.smtp.socketFactory.class=
  4. Set the values for the below parameters:
    
    resetPassword.email.smtp.host: Set to the name of the SMTP host that is set up to send emails.
    
    resetPassword.email.from: Set to the sender name to be displayed on sent emails.
    
    resetPassword.email.username: Set to the email account on the SMTP host that is used to send the email.
    
    resetPassword.email.password: Set to the password for the email account that is sending the email messages. Leave this parameter blank if the password is not required by the server.
    
    resetPassword.email.smtp.port: Set to the port used by the SMTP server. Common values are 465 for SSL-enabled servers, or 25 for non-SSL servers.
  5. You can customize the messages of the SMTP host for password changes. The message parameter and default values are listed below.
    
    resetPassword.email.message.subject: The default text is Reset Password Request for {0}, where {0} is replaced by the username for which the password is reset.
    
    resetPassword.email.message.body: The default text is This message confirms that your password has been reset. The new password for user {0}, database {1} is: {2}, where {0} is replaced by the username for which the password is reset, {1} is replaced by the name of the database, and {2} is replaced by the new password.
    
    resetPassword.error.failed.text: The default text is Failed to reset password. Please contact your help desk.
    
    resetPassword.error.nousername.text: The default text is Please provide a valid username.
    
    resetPassword.error.failedemail.text: The default text is Your Password has been reset, however the e-mail notification failed to launch. Please contact your system administrator.
    
    resetPassword.confirm.text: The default text is Your Password has been reset. Please check your e-mail for the new password.
Save your changes.
Restart the OPA server.

For details, see Section D.5, "Restarting the OPA Server".

7.4 Customizing Branding Images in RDC

In RDC, the page header displays the Oracle logo as the product logo in the top-left corner by default and also allows for adding a co-brand logo in the top-right corner. You can customize the application to add your own product image and a co-brand logo.

Description of the illustration ''custom_brand_logo.gif''

To customize the product and co-brand images:

Create one or both image files in any format (for example JPG, GIF), as follows:
- Product branding image: width of 155 pixels and height of 20 pixels.
- Co-brand logo image: width of 100 pixels and height of 20 pixels.
Copy the image files to the OPA_HOME\html\images folder. For example, C:\opapps52\html\images.
Navigate to the middleware_home\asinst_1\config\OHS\ohs1\moduleconf folder.
Open the file opa52_httpd.conf in a text editor and, if not already set, add an alias for opa52, pointing to the html folder:
```
alias /opa52/ "C:\opapps52/html/"
```
Save your changes and close the opa52_httpd.conf file.
Open the RdcLogos.properties file in a text editor. This file is in the OPA_CONFIG_FOLDER. The folder path is determined by the registry entry opa52, found under HKEY_LOCAL_MACHINE > Software > Oracle.
To replace the product brand image that appears in the top-left corner of the RDC pages:
1. Find the string image.ProductBranding=images/FNDSSCORP.gif, where images is the folder where you placed the image. This folder may have a different name in your environment.
2. Replace the text FNDSSCORP.gif with the name of the product brand image you created for step 1.
To place a co-brand in the top-right corner of the RDC pages:
1. Find the string image.CoBranding=images/co_brand.jpg.
2. Replace co_brand.jpg with the name of the file containing the co-brand image you placed in the images folder at step 1.
3. Find the string image.CoBrandingRendered=false and replace the value with true.
Save your changes and close the RdcLogos.properties file.
Restart the OpaServer1 from the WebLogic Admin Console for the changes to take effect.

7.5 Customizing the Contact Us Link

By default, the RDC application does not include the Contact Us link with the other global links that display in the page header and the page footer.

You can indicate whether you want the Contact Us icon to appear, and if so, its target URL.

To customize the Contact Us link:

Stop the WebLogic Admin Server.
Log in to the RDC application server.
Navigate to the OPA_CONFIG_FOLDER. The folder path is determined by the registry entry opa52, found under HKEY_LOCAL_MACHINE > Software > Oracle.
Open the RdcLogos.properties file with a text editor.
Find the following two lines in the file:

image.ContactUsUrl=https://support.oracle.com/ image.ContactUsUrlRendered=false
Make the following changes:
1. Replace the support.oracle.com Web address with the URL of the Web page that you want users to access when they click the Contact Us link.
2. Set image.ContactUsUrlRendered=true to display the Contact Us link in the RDC application.
Save your changes.
Restart the WebLogic Admin Server instance.

7.6 Customizing the Change Password Link

By default, the Change Password link appears in the page header and the page footer of the RDC application pages, along with the other global links. You can customize this link to point to your own change password page by editing the RdcTexts.properties file.

The RdcTexts.properties file is located in OPA_CONFIG_FOLDER. This path comes from the registry entry opa52 under HKEY_LOCAL_MACHINE > Software > Oracle.

In addition, using SQL commands, you can customize password profiles that affect whether the Change Password page is invoked automatically during the grace period or after the password has already expired.

Your options for customizing the Change Password link include:

Changing the URL and the Name for the Change Password Link
Enforcing Profile Limits for the Change Password Page

7.6.1 Changing the URL and the Name for the Change Password Link

By changing the URL, you can customize the page that your users see when they click the Change Password link.

You can also change the name of the Change Password link. You cannot, however, hide the link. The Change Password link always displays in the RDC application.

To customize the URL and name for the Change Password link:

Stop the WebLogic Admin Server.
Log in to the RDC application server.
Navigate to OPA_CONFIG_FOLDER. Its path comes from the registry entry opa52 under HKEY_LOCAL_MACHINE > Software > Oracle.
Open the RdcTexts.properties file with a text editor.
Find the following text string and specify your custom URL:

url.ChangePassword=rdcUserPreferences.do?pagetype=
Find the following text string and enter the text for the name of the Change Password link:

button.ChangePassword=
Save your changes.
Restart the WebLogic Admin Server.

7.6.2 Enforcing Profile Limits for the Change Password Page

Passwords have a lifetime and a grace period defined by database profiles. You can set an expiration date for passwords. Accordingly, RDC prompts users to change their password as the expiration date approaches.

Users have a grace period in which to change their password. If they log in during the grace period, RDC displays a warning message that their password will expire soon and automatically redirects them to the Change Password page. Users can choose to change their password now or wait until later. RDC lets users log in.

If users do not change their password during the grace period, the password will expire. However, the opportunity to change the password still exists. If users attempt to log in with an expired password, RDC automatically redirects them to the Reset Expired Password page. In this case, users cannot continue until they successfully change their password. Users must then log in with their new password.

To ensure that the profile limits are enforced, use the following SQL command to assign a profile to a user:

ALTER USER user-name PROFILE profile-name

7.7 Customizing the Electronic Signature (Approval) Warning Message

Whenever a user approves a CRF or a group of CRFs in RDC, the approval represents an electronic signature provided in accordance with FDA 21 CFR Part 11.

Every time the user approves a CRF or undoes the approval for a CRF, RDC issues a standard warning message that appears in the same window as the approval. You can customize this message.

Users can select options in the Data Entry window or options on the application pages to approval CRFs. Therefore, if you decide to customize the approval warning message, make sure you change the message for both locations in the user interface.

7.7.1 Customizing the Approval Warning Messages for the Data Entry Window

To customize the approval warning messages for the Data Entry window:

Make a copy of olsardc.ear from the upload folder or equivalent pat: middleware_home\user_projects\domains\OPADomain\servers\AdminServer\upload\olsardc.ear
Open olsardc.ear using any utility to unzip.
From there traverse to the location of de_external.properties in the following path:

middleware_home\user_projects\domains\OPADomain\servers\AdminServer\upload\olsardc.ear\RdcSurroundAdfWebUIWebApp.war\WEB-INF\lib\rdcdataentry.jar\oracle\pharma\rdc\de\resource\properties\de_external.properties
Open the de_external.properties file with a text editor.
Modify the Approval warning message:
1. Find the following text string:
  
  de.dcs.approve.signoff=
2. Change the text following the equal symbol (=) to the message that displays when the user approves a CRF from the Data Entry window. The default text is:
  
  de.dcs.approve.signoff=IMPORTANT By approving this CRF page, you confirm that all data on the page is complete and correct. This approval is equivalent to an electronic signature.
Modify the Undo Approval warning message:
1. Find the following text string:
  
  de.dcs.unapprove.signoff=
2. Change the text following the equal symbol (=) to the message that displays when the user undoes the approval from the Data Entry window. The default text is:
  
  de.dcs.unapprove.signoff=IMPORTANT By undoing approval, you are rescinding the electronic signature on this page.
Save your changes.
Click Ok when prompted to replace the modified files in the war and ear.
Close the unzip utility.

You now need to deploy the customization. See Appendix D for instructions.

7.7.2 Customizing the Approval Warning Messages for the Application Pages

To customize the approval warning messages for the application pages:

Stop the WebLogic Admin Server.
Log in to the RDC application server.
Navigate to OPA_CONFIG_FOLDER. The folder path is determined by the registry entry opa52 under HKEY_LOCAL_MACHINE > Software > Oracle.
Modify the Approval warning message:
1. Find the following text string:
  
  prompt.ApproveCrfWarning2=
2. Change the text following the equal sign (=) to the message that displays when the user approves a CRF from an application page. The default text is:
  
  prompt.ApproveCrfWarning2=By approving this group of CRFs, you confirm that all data are complete and correct. Each approval is equivalent to an electronic signature.
Modify the Undo Approval warning message:
1. Find the following text string:
  
  prompt.UnApproveCrfWarning2=
2. Change the text following the equal sign (=) to the message that displays when the user undoes the approval from an application page. The default text is:
  
  prompt.UnApproveCrfWarning2=By undoing the approval of this group of CRFs, you revoke prior certification that the data was complete and correct. Each un-approval is equivalent to removal of an electronic signature.
Save your changes.
Restart the WebLogic Admin Server instance.

7.7.3 Other Options for Customizing Approvals

In addition to customizing the approval warning messages, you can:

Disable approval from RDC. See Section 3.3.4, "Allowing CRF Group Actions" for more information.
Set a timeout value for pre-population of user name for approvals. See Section 8.2, "Configuring a Timer Period for Subsequent Electronic Signatures" for more information.

7.8 Customizing the Logout Message

By default, RDC displays the following message when you log out of the application:

You can customize this message by editing the RdcTexts.properties file. You may want to provide additional information or hints — such as exit from Internet Explorer or delete the browsing history — that users should do after logging out.

To customize the logout message for the RDC application:

Stop the WebLogic Admin Server.
Log in to the RDC application server.
Navigate to the OPA_CONFIG_FOLDER. The folder path is determined by the registry entry opa52, found under HKEY_LOCAL_MACHINE > Software > Oracle.
Open the RdcTexts.properties file in a text editor.

Find the following parameters and update their values to customize the logout message:

logout.msg.normal.1=You are successfully logged out. Click
logout.msg.normal.2= to log in again.
logout.msg.timedout.1=Your session timed out. Click
logout.msg.timedout.2= to log in again.
logout.msg.changepassword.1=Your Password has been changed successfully. Click
logout.msg.changepassword.2= to log in with new credentials.

Save your changes and close the file.
Restart the WebLogic Admin Server instance.

7.9 Setting the User Session Timeout Value

A session begins when a user successfully logs in to RDC. The session ends either when the user logs out or when RDC times out due to inactivity.

By default, RDC times out after 30 minutes of inactivity. However, you can change the timeout interval to another value. If a user remains inactive in a session for the specified period of time, RDC automatically times out and logs the user out of the application.

The automatic timeout provides added security to unauthorized use of the application. If a timeout occurs, RDC prompts the user to log in again.

7.9.1 Recommendations for Setting the Session Timeout Value

When determining whether to increase the session timeout to more than 40 minutes, you must consider the following issues:

High timeout values may negatively affect performance and scalability because memory usage increases as the timeout value increases. Specifically, when a session times out, the system cleans out all resources assigned to the user. Increasing the timeout value means the system continues to use resources for a longer time. However, if the number of concurrent users accessing the system is low (that is, 25–50), you may not notice that resources are used for a longer time, and therefore, you may not experience any resource problems. Furthermore, if you have correctly configured your server for the number of users accessing the system, you should not experience any problems with memory or CPU resources.
The value for the jbo.ampool.maxinactiveage setting in the bc4j.xcfg file must be set higher than the session timeout. The default value for this setting is 60 minutes. Therefore, you must also edit the jbo.ampool.maxinactiveage setting if you set the session timeout to 120 minutes (1200000).

For additional information about the various configuration settings you can use to improve the performance of RDC, consult the following white paper on My Oracle Support:

Document Name: Oracle Clinical Remote Data Capture Onsite and Thesaurus Management System Browser Infrastructure Tuning Tips for Releases 5.0.1 and 5.1

Document ID: 1965232.1

Also see the page Oracle Clinical and Oracle Clinical Remote Data Capture 5.2 Documentation on the Oracle Help Center (http://docs.oracle.com) for the most recent product documentation.

7.9.2 Changing the Session Timeout Value

To change the timeout interval for an RDC session:

Stop the WebLogic Admin Server instance.
Log in to the RDC application server.
Navigate to the OPA_CONFIG_FOLDER. The folder path is determined by the registry entry opa52, found under HKEY_LOCAL_MACHINE > Software > Oracle.
Open the RdcConfig.properties file with a text editor.
Find the following line and edit the value (number of minutes) to change the session timeout limit:

rdc_session_timeout=30

Note:
If you set the session timeout to more than 59 minutes, you must also change the value for the jbo.ampool.maxinactiveage setting in the bc4j.xcfg file to be greater than the value of the session timeout.
Save your changes.
Restart the WebLogic Admin Server instance.

7.10 Setting the Maximum Number of Rows Fetched

By default, RDC retrieves a maximum of 1000 rows of data (records) whenever you open the Home page or execute a search.

You can change the default value by adding the max_row_fetched parameter to the RdcConfig.properties file. You specify the maximum number of rows that RDC can retrieve from the database at a time. When you execute a search, RDC issues a warning message to adjust the search criteria if your query would retrieve more rows than the maximum number allowed.

Note:

Increasing the value is likely to degrade performance. Reducing the value may improve performance for any given search, but may require more searches to be executed by the user.

To change the maximum number of rows fetched:

Log in to the RDC application server.
Navigate to the OPA_CONFIG_FOLDER. The path is determined by the registry entry opa52 under HKEY_LOCAL_MACHINE > Software > Oracle.
Open the rdcConfig.properties file with a text editor.
Update the value for max_row_fetched in the file. The default value is 1000.
Save your changes.

7.11 Storing Custom Web Pages

Custom pages can be kept in the following folder:

middleware_home\user_projects\domains\OPADomain\servers\HOST_NAME_OPA_INSTANCE_NO\tmp\_WL_user\olsardc_release-build\deployment-specific_folder\war\

For example, the location for a test.pdf file would be:

middleware_home\user_projects\domains\OPADomain\servers\blr2211071_OPA_1\tmp\_WL_user\olsardc_5.2.0.0.20-b00\pqp2wi\war\test.pdf

The URL corresponding to the same test.pdf file used as example is:

<a target="_blank" href="https://XXXXX/rdcadfsrnd/test.pdf">https://XXXXX/rdcadfsrnd/test.pdf</a>

Use this directory to save the custom Web pages that you create for CRF online help and for the Links section on the Home page.

For information on creating and maintaining links, see Chapter 11, "Configuring Links."

7.12 Storing the DCIF Images

Form designers can embed logos or other images in their forms.

To enable image viewing on CRFs during data entry in RDC, you can choose either to set up a central repository or to copy images to all RDC installations. For information on enabling image viewing, see the Oracle Clinical Administrator's Guide.

7.13 Customizing the Single View of the Patient Casebooks Page

You can choose to activate or deactivate single view for the Patient Casebooks page (Single Patient Casebooks). If it is active, you can configure RDC so that patient numbers on the Home page are links that navigate to the single view Patient Casebooks page.

7.13.1 Activating One-Click Navigation to the Single View of Patient Casebooks Page

With this feature activated, patient numbers on the RDC Home page are links that navigate to the single view of the Patient Casebooks page for that patient.

To activate this feature:

Open the RdcLogos.properties file in a text editor.
Find the feature.Enable_PtID_SPC_Links parameter and change its value from 0 to 1.
Save your changes and close the file.
For the change to take effect, restart the application server.

7.13.2 Deactivating the Single View for the Patient Casebooks Page

To deactivate single view for the Patient Casebooks page:

Open the RdcLogos.properties file in a text editor.
Find the feature.EnableSPCB parameter and change its value from 1 to 0.
Save your changes and close the file.
For the change to take effect, restart the application server.

7.14 Hiding Unplanned Visit Buttons in RDC Onsite

If you don't want to allow RDC Onsite users to add unplanned visit pages using the Add Visit Page button or to add additional pages to visits using the Add Other Page button, you can hide one or both of these buttons from the Patient Casebooks page. For details about these buttons, see the section "Adding Pages" in the Oracle Clinical Remote Data Capture User's Guide.

To hide the buttons:

Open the RdcLogos.properties file in a text editor. or . Change the default value for the parameter from 1 to 0. Restart the OpaServer1 for the changes to take effect.
Find the parameter corresponding to the buttons you want to hide: feature.EnableAddVisitPage and feature.EnableAddOtherPage.
Change the value for a parameter from 1 to 0 to hide the corresponding button.
Save your changes and close the file.
For the changes to take effect, restart application server.