Oracle® Clinical Remote Data Capture Onsite Administrator's Guide Release 5.1 E53568-01 |
|
|
PDF · Mobi · ePub |
This chapter describes how you can deploy customizations you perform on any file.
After you customize a file, you may need to redeploy the .ear file by following the next steps:
Note:
Please note that these steps cause downtime of application.Log into the admin server console for OPADomain using a URL of the form http://machinename:port/console.
For example, http://pharma.oracle.com:7101/console.
Click on Deployments and select the checkbox for olsardc.
Make a copy of olsardc.ear from the upload folder or equivalent path: middleware_home\user_projects\domains\OPADomain\servers\AdminServer\upload\olsardc.ear.
Note:
To find the upload path, go to the admin server console for OPADomain. Click on Deployments, then select the checkbox for olsardc and click Update. The Source path will display the current upload location.Log into the admin server console for OPADomain using a URL of the form http://machinename:port/console.
For example, http://phrama.oracle.com:7101/console
Click on Deployments.
Select the checkbox for olsardc, select it and click Stop > Force Stop Now.
Select the checkbox for olsardc one more time and click Delete.
If you are prompted to proceed with the deletion, click OK to confirm.
Note:
This removes olsardc.ear from the application server.Log into the admin server console for OPADomain using a URL of the form http://machinename:port/console.
For example, http://pharma.oracle.com:7101/console.
Click on Deployments and select the checkbox for olsardc.
Click Update and then click Next.
Click Finish to complete the deployment.
Upon redeployment, you need to restart the OpaServer.
Log into the admin server console for OPADomain using a URL of the form http://machinename:port/console.
Click on Environments and then Servers.
Select the Control tab.
Select the checkbox for OpaServer1.
Click on Shutdown and then Force Shutdown Now.
Refresh the screen by clicking on the auto refresh icon.
Once the status of OpaServer1 changes to SHUTDOWN, click on the auto refresh icon again to turn it off.
Select the checkbox for OpaServer1 and click Start.
Turn auto refresh on again to verify that the server status changes to RUNNING.
Once the OpaServer is restarted, you can verify your customizations.
If you do not have an unzip utility installed, you can manually extract and then repack the .ear file by following the steps below.
To extract the olsardc.ear file:
Open a DOS Command window and navigate to the upload directory.
See Section D.1, "Locating the olsardc.ear File" for information on how to find the upload directory.
Back up the olsardc.ear file.
Create a new temporary directory called mycustomloc and then copy the olsardc.ear file to that directory as shown in the below example:
C:\mycustomloc>copy C:\app\oracle\middleware\user_projects\domains\OPADomain\servers\AdminServer\upload\olsardc.ear
Extract olsardc.ear using the jar utility command:
middleware_home\Oracle_FRHome1\jdk\bin\jar -xvf olsardc.ear
For example:
C:\mycustomloc>C:\app\oracle\middleware\Oracle_FRHome1\jdk\bin\jar -xvf olsardc.ear
The file RdcSurroundAdfWebUIWebApp.war is in the extracted directory.
Create another temporary directory called RdcSurroundAdfWebUIWebApp and move the RdcSurroundAdfWebUIWebApp.war to this new directory.
Extract the RdcSurroundAdfWebUIWebApp.war file using the jar utility command
middleware_home\Oracle_FRHome1\jdk\bin\jar -xvf RdcSurroundAdfWebUIWebApp.war
For example: C:\mycustomloc\RdcSurroundAdfWebUIWebApp>C:\app\oracle\middleware\Oracle_FRHome1\jdk\bin\jar -xvf RdcSurroundAdfWebUIWebApp.war
After extracting the file, you can access the RDC application WEB-INF directory and all files under it from within the newly extracted directory.
Make changes to the files as necessary.
Save your changes.
To repack the olsardc.ear file:
Open a DOS Command window and navigate to the temporary directory RdcSurroundAdfWebUIWebApp.
If present, remove the RdcSurroundAdfWebUIWebApp.war file from this directory.
Rebuild the RdcSurroundAdfWebUIWebApp.war file using the jar command
middleware_home\Oracle_FRHome1\jdk\bin\jar -cvf RdcSurroundAdfWebUIWebApp.war *
For example: C:\mycustomloc\RdcSurroundAdfWebUIWebApp>C:\app\oracle\middleware\Oracle_FRHome1\jdk\bin\jar -cvf RdcSurroundAdfWebUIWebApp.war *
The process created the RdcSurroundAdfWebUIWebApp.war file.
Move RdcSurroundAdfWebUIWebApp.war to the temporary directory mycustomloc.
Navigate to the temporary directory mycustomloc.
Delete the RdcSurroundAdfWebUIWebApp directory using the command:
rd /S /Q RdcSurroundAdfWebUIWebApp
If present, remove the olsardc.ear file from the mycustomloc directory.
Rebuild the olsardc.ear using the jar command:
middleware_home\Oracle_FRHome1\jdk\bin\jar -cvf olsardc.ear *
For example:
C:\mycustomloc>C:\app\oracle\middleware\Oracle_FRHome1\jdk\bin\jar -cvf olsardc.ear *
Copy the new olsardc.ear file to the upload directory middleware_home\user_projects\domains\OPADomain\servers\AdminServer\upload.
For example:
C:\mycustomloc>copy /Y olsardc.ear C:\app\oracle\middleware\user_projects\domains\OPADomain\servers\AdminServer\upload
Note:
The new olsardc.ear file should be copied to the same location as the one entered in the Source path field.To find the source path, go to the admin server console for the OPADomain. Click on Deployments. Select the checkbox for olsardc and then click Update. After confirming the source path, click Cancel to exit the Update Application Assistant screen.