| Oracle® Study, Subject, and Visit Synchronization Integration Pack for Siebel Clinical and Oracle Clinical Installation Guide Release 11.1 E36139-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Study, Subject, and Visit Synchronization Integration Pack for Siebel Clinical and Oracle Clinical Installation Guide Release 11.1 E36139-01 |
|
|
PDF · Mobi · ePub |
This chapter describes the steps for upgrading the Study, Subject, and Visit Synch: Siebel Clinical - Oracle Clinical from version 3.1 to version 11.1.
Perform the following tasks to upgrade the integration from 3.1 to 11.1:
Section 11.2, "Upgrading the Oracle WebLogic Server From 10.3.4 to 10.3.5"
Section 11.3, "Upgrading the Service-Oriented Architecture Suite From 11.1.1.4.0 to 11.1.1.5.0"
Section 11.5, "Upgrading the Foundation Pack From 11.1.1.4 to 11.1.1.5"
Section 11.7, "Upgrading the Process Integration Pack From 3.1 to 11.1"
See Also:
For more information, refer to the following documents:
Weblogic and SOA Upgrade: http://docs.oracle.com/cd/E21764_01/doc.1111/e16793/patch_set_installer.htm#CHDCCEAC
Foundation Pack Upgrade: http://docs.oracle.com/cd/E21764_01/doc.1111/e17949/upgrade.htm#CIACFGIJJ
The section describes the pre-patch tasks for upgrading the PIP and contains the following topics:
You must stop the Siebel Life Sciences (LS) Clinical Rollup Workflow Monitor Agent for Siebel Clinical to ensure that the messages generated by Siebel Clinical are not lost when the PIP is undergoing an upgrade, and the messages are piled up in Siebel Clinical. After the upgrade is complete, restart the LS Clinical Rollup Workflow Monitor Agent to ensure that the messages are delivered to the target application.
Note:
Clinical data rollup functionality does not get synchronized until you restart the Workflow Monitor Agent; all pending Siebel Clinical - Oracle Clinical requests and data rollup requests are completed when you restart the Workflow Monitor Agent.To stop the LS Clinical Rollup Workflow Monitor Agent for Siebel Clinical:
Log in to Siebel Clinical application as an administrator, navigate to Administration, then navigate to the Server Management, and then navigate to Tasks.
Query for the Workflow Monitor Agent component.
Select the Parameters tab and query for a parameter with the value LS Clinical Rollup.
Click Stop at the top to stop the Workflow Monitor Agent for LS Clinical Rollup.
If there are more than one Workflow Monitor Agents, select all the agents for parameter LS Clinical Rollup. Stop only the agents that contain LS Clinical Rollup parameter.
You must stop the dequeuing of messages from Oracle Clinical AQ by AIA AQ Consumer to avoid losing any message from Oracle Clinical when the integration is undergoing upgrade process. When the PIP upgrade is complete, enable the dequeue to let messages to be processed by AIA.
Perform the following steps to stop the dequeue messages:
Connect to the Oracle Clinical database as user rxc.
Execute the following command:
execute DBMS_AQADM.STOP_QUEUE(queue_name => 'CLINICAL_STUDY_QUEUE' ,enqueue => FALSE, dequeue => TRUE, wait => TRUE);commit;
Stop all server processes on the AIA server. For example, soa_server, admin server, node manager, DB listener, and so on. Execute this command from the command prompt to list process IDs (PIDs) of all the processes:
ps -ef | grep java | grep <username>
For example, ps -ef | grep java | grep ora<slot#>
The output should only display the grep java process.
Sometimes even after shutting down all the processes, additional processes might run in the background. In this case, you have to manually kill these processes using the following command:
kill -9 <PID>
Important:
Before you start taking backup of the Middleware Home and other components, ensure that you have enough disk space (about 30 GB to 50 GB approximately).Back up the contents of <Oracle_home>/Middleware to the directory Middleware_bak.
Perform the following steps to take a backup of the database schema to MDS.
Start the Oracle database and DB listener.
Create a directory.
<user_home>/dbbackup/<directory_name>
For example,
/slot/prod/oracle/dbbackup/mds
Execute these commands from a UNIX command line session:
source <oracle_home>/db11g/product/11.2.0/dbhome_1/<DB ENV File Name>.env
sqlplus sys as sysdba
You will be prompted for the sys password.
CREATE OR REPLACE DIRECTORY <dir_name> AS <user_home>/dbbackup/mds;
For example,
CREATE OR REPLACE DIRECTORY db_dir as '/slot/prod/oracle/dbbackup/mds';
GRANT READ, WRITE ON DIRECTORY db_dir TO system
Exit SQL prompt. Execute the following command at the UNIX prompt:
expdp '"/as sysdba"' directory=db_dir schemas=<schema name> dumpfile=<Dump File Name>.dmp logfile=<Log file name>.log rows=y consistent=y feedback=1000
For example,
expdp system/manager owner=DEV_MDS directory=db_dir dumpfile=Sampledump.dmp logfile=SampleLog.log rows=y consistent=y feedback=1000
Create a directory DB_DIR_SOA_INFRA and repeat steps 3 and 4 to take a back up of the DEV_SOAINFRA schema.
Perform the following steps to check the aq_tm_processes value for Oracle Portal:
Connect to the AIA Database through SQL*Plus as a sys manager and execute the following commands:
create spfile from pfile;shutdown immediatestartupshow parameter spfile;show parameter aq_tm_processes;
If the value returned after executing the commands in step 1 is 0, execute the following command to change the value to 1:
Alter system set aq_tm_processes=1 scope=both;
This section describes the steps to upgrade the Oracle WebLogic Server from version 10.3.4 to 10.3.5. This section contains the following topics:
From the following location download the patch installer for Oracle WebLogic version 10.3.5 to any suitable location on the server:
https://updates.oracle.com/download/12395517.html
Note:
In this guide, we have referred to the path of the installer as <WeblogicInstallerPath>.Perform the following tasks to update registry.xml. You need not install Oracle Enterprise Repository (OER) on the server system.
Navigate to the Middleware home and backup registry.xml.
Add the following section to the registry.xml just before Oracle Enterprise Repository 11.1.1.4 entry and save the file.
Important:
Ensure that you change the path names in the following code to those corresponding to the server on which the upgrade is being performed.<product format="1.0" name="Oracle Enterprise Repository"><release level="11.1" ServicePackLevel="1" PatchLevel="3" Status="installed" InstallDir="/slot/prod/oracle/Middleware"><component name="Oracle Enterprise Repository" version="11.1.1.3" InstallDir="/slot/prod/oracle/Middleware/repository111"><component name="Core Repository with Examples"/></component><component name="Common Infrastructure Engineering" version="6.8.0.0" InstallDir=""><component name="Uninstall"/><component name="Clone Facility"/></component></release></product>
If you have an existing WebLogic Server 10.3.0, 10.3.1, 10.3.2, 10.3.3, or 10.3.4 installation that includes Workshop for WebLogic, and you want to use an upgrade installer to upgrade that installation to WebLogic Server 10.3.5, you must uninstall Workshop for WebLogic before running the upgrade installer.
To check whether Workshop for WebLogic is installed or not and to uninstall Workshop for WebLogic, perform the following steps:
Navigate to the following directory from VNC server:
cd/<Middleware_home>/utils/uninstall
Enter ./uninstall.sh at the prompt.
Click Next on the Welcome screen.
If Workshop for WebLogic is installed, the Workshop for WebLogic component is displayed. If Workshop is installed, select the workshop component and clear selection for all other components and uninstall it. Else, exit installation.
Run the upgrade installer in graphical mode to patch your WebLogic Server.
Unzip the upgrade installer p12395517_1035_LINUX.zip that you downloaded as per the steps in the Section 11.2.1, Downloading Patch Installer.
Launch the installation by entering these commands:
chmod 777 wls1035_upgrade_linux32.bin
Run the installer file in VNC server by executing the following command:
./wls1035_upgrade_linux32.bin
The Welcome screen is displayed.
In the Welcome screen, click Next.
The Choose Middleware Home Directory screen is displayed.
Select an existing Middleware Home (<Oracle_Home>/Middleware).
The Choose Middleware Home Directory screen is displayed with the selected options.
Click Next.
The Register for Security Updates screen is displayed.
Provide the details of registration for security updates or bypass the registration.
The Register for Security Updates screen is displayed.
Click Next.
In the Choose Products and Components screen, deselect the Oracle Enterprise Pack for Eclipse option.
Click Next.
The Choose Product Installation Directories screen is displayed.
Select the product installation directories.
Click Next to begin the installation.
Note:
The Installation Complete screen is displayed when the installation is complete.If you do not want the Oracle WebLogic console to be displayed, deselect the Run Quickstart check box.
Click Done.
This section describes the steps for upgrading Service-Oriented Architecture (SOA) Suite from version 11.1.1.4.0 to version 11.1.1.5.0.
This section contains the following topics:
Download Patch Installer for SOA 11g Release 1 (11.1.1.5.0) from this location:
Unzip the upgrade installer for SOA suite to a suitable location on the server. Ensure that both part 1 and 2 of the installation are unzipped to the same local folder such that the final contents of this folder are Disks 1 to 5.
cd Disk1
For Linux: enter./runInstaller
For Windows: double-click setup.exe.
Navigate to the location where the SOA suite patch is unzipped and execute the following command in VNC server:
cd Disk1
For Linux: enter./runInstaller
For Windows: double-click setup.exe.
Specify the JRE/JDK path that comes as a part of installation.
For example,
/slot/prod/oracle/Middleware/jdk160_24/jre
The Installation screen is displayed.
In the Specify Inventory Directory screen, click Browse, and select the location for Inventory Directory.
The Specify Inventory Directory screen is displayed with the selected location.
Click OK.
The Inventory Location Confirmation screen is displayed.
Select Continue installation with local inventory.
Click OK.
The Welcome screen is displayed.
In the Welcome screen, click Next.
In the Install Software Updates screen, click Select Skip Software Updates.
The Skip Software Updates screen is displayed with the selected option.
Click Next.
The Prerequisite Checks screen is displayed.
After the prerequisite checks are complete, click Next.
The Specify Installation Location screen is displayed.
Select the existing Middleware Home for installation.
The Specify Installation Location screen is displayed with the selected location.
Click Next.
A warning message is displayed.
Click Yes.
The Select Application Server screen is displayed.
Select WebLogic Server.
The Select Application Server screen is displayed with the selected option.
Click Next.
The Installation Summary screen is displayed.
Review the Installation Summary and click Install.
The Installation Progress screen is displayed.
When the installation is complete, click Next.
The Installation Complete screen is displayed when the installation is complete.
Click Finish.
When the Administration Server is started, the contents of the config/soa-infra directory in your DOMAIN_HOME are overwritten by the Administration Server. However, SOA configuration parameters are updated only on Managed Servers and on a per-server basis, all updates to the SOA configuration are lost when the Managed Servers are restarted; if the system hosting the Administration Server does not have an updated copy.
The ant-soa-util.xml script in your SOA_ORACLE_HOME/bin directory can be used to resolve this issue. The script does the following:
Note:
The script must be run before you try to start the Administration Server or any of the Managed Servers.Moves the config/soa-infra (on UNIX operating systems) or config\soa-infra (on Windows operating systems) to the DOMAIN_HOME/soa_backup/config/soa-infra (on UNIX operating systems) or DOMAIN_HOME\soa_backup\config\soa-infra (on Windows operating systems) directory.
Replaces the startManagedWebLogic.sh (on UNIX operating systems) or startManagedWebLogic.cmd (on Windows operating systems) scripts with versions that prevent the Managed Servers from starting.
To run the ant-soa-util.xml, execute the following commands at command prompt:
source <MIDDLEWARE_HOME>/wlserver_10.3/server/bin/setWLSEnv.sh
For example,
source /slot/prod/oracle/Middleware/wlserver_10.3/server/bin/setWLSEnv.sh
cd <SOA_ORACLE_HOME>/bin
For example,
cd /slot/prod/oracle/Middleware/Oracle_SOA1/bin
ant -f ant-soa-util.xml
Build successful message is displayed.
To get your deployments up and running, you must start the Administration Server and various Managed Servers. You can either start the servers using WebLogic Scripting Tool (WLST) and Node manager or perform the following steps:
To start the Administration Server, run the following script as per your platform in the directory where you created your new domain.
On UNIX operating systems:
DOMAIN_HOME/startWebLogic.sh
On Windows operating systems:
DOMAIN_HOME\startWebLogic.cmd
Note that the domain name and location are the values you entered for these in the Specify Domain Name and Location screen of the Configuration Wizard when you installed Foundation Pack version 11.1.1.14.
To start the Managed Servers, run the following commands as per your platform.
On UNIX operating systems: startManagedWebLogic.sh
On Windows operating systems: startManagedWebLogic.cmd
Run the script in the bin directory inside the directory, where you created your domain.
Start these managed servers from the command line.
Specify a server name. The servers that need to be started are:
soa_server1 (Oracle SOA Server)
bam_server1 (Oracle BAM Server)
For example, to start Oracle SOA Server on a UNIX operating system:
DOMAIN_HOME/bin/startManagedWebLogic.sh soa_server1
On Windows operating system:
DOMAIN_HOME\bin\startManagedWebLogic.cmd soa_server1
Before you start the managed server, enter the WebLogic Server user name and password.
To verify the installation, start your browser and enter the following URLs:
To access the Administration Server console:
http://administration_server_host:administration_server_port/console
Enter the user name and password credentials that you specified in the Configure Administrator User name and Password screen of the Configuration Wizard.
After you login to the console, click Servers in the Environment area in the Domain Configuration section. In the table on the Summary of Servers page, verify that the AdminServer and soa_server1 all have the status RUNNING in the State column.
To access Enterprise Manager:
http://administration_server_host:administration_server_port/em
This section contains the following topic:
Remember the following points when running the Patch Set Assistant.
For upgrading SOA Suite from version 11.1.1.4.0 to version 11.1.1.5.0, upgrade of MDS and ODS Schemas is required.
If you are running the Patch Set Assistant for the Oracle Portal schema on an Oracle database, ensure that the aq_tm_processes value in your database is greater than 0. To check, use the following command after connecting to the database:
show parameter aq_tm_processes;
If the value returned is 0, use the following command to change the value to 1:
alter system set aq_tm_processes=1 scope=both;
Navigate to <Oracle_SOA_home>/bin.
For example,
cd /slot/prod/oracle/Middleware/Oracle_SOA1/bin
Run the following command to upgrade the MDS schema:
./psa -dbConnectString //<DB_host_name>:<DB_port>/<Db_sid> -dbaUserName <DB user ’sys' username> -schemaUserName DEV_MDS -logLevel TRACE -invPtrLoc <ORACLE_SOA_HOME> /oraInst.loc
For example,
./psa -dbConnectString //server.domain.com:1592/oraclini -dbaUserName sys -schemaUserName DEV_MDS -logLevel TRACE -invPtrLoc /prod/oracle/Middleware/Oracle_SOA1/oraInst.loc
The script prompts for passwords for sys and <MDS user>.
A success message is displayed when the upgrade is complete.
To verify the upgrade, run the following commands after connecting to the database as sys.
SQL> SELECT VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY WHERE OWNER='DEV_MDS';
VERSION STATUS U
------------------------------ ----------- -
11.1.1.5.0 VALID Y
Similarly, use this command to upgrade SOAINFRA:
./psa -dbConnectString //server.domain.com:1592/oraclini -dbaUserName sys -schemaUserName DEV_SOAINFRA -logLevel TRACE -invPtrLoc /slot/prod/oracle/Middleware/Oracle_SOA1/oraInst.loc
To verify SOAINFRA upgrade, use the following command:
SQL> SELECT VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY WHERE OWNER='DEV_SOAINFRA';
VERSION STATUS U
------------------------------ ----------- -
11.1.1.5.0 VALID Y
To upgrade the foundation pack, refer to the following link for more information:
http://docs.oracle.com/cd/E21764_01/doc.1111/e17949/upgrade.htm#CIACFGIJ
This section contains the following topics:
At the command prompt, run the following command:
chmod -R 777 <AIA_HOME>
Download aiafp.zip for Foundation Pack version 11.1.1.5 RTM from the edelivery page or an appropriate location.
Unzip the aiafp.zip file to the appropriate location on the server, and then navigate to aiafp/Disk1 directory in this location:
cd <fp unzip location>/aiafp/Disk1
For example,
cd /prod/oracle/aiafp/Disk1/
Run the following command from VNC Server.
./runInstaller -invPtrLoc <Oracle_Home>/Middleware/Oracle_SOA1/oraInst.loc -jreloc <location of jre>
For example,
./runInstaller -invPtrLoc /slot/prod/oracle/Middleware/Oracle_SOA1/oraInst.loc -jreloc /slot/prod/oracle/Middleware/jdk160_24/jre
The Welcome screen is displayed.
Click Next.
The Prerequisite Checks screen is displayed.
After the prerequisite checks are complete, click Next.
The Installation Location screen is displayed.
Select the existing AIA Home. AIA Instance for upgrade is automatically selected.
The Installation Location screen is displayed with the selected option:
Click Next.
A warning message is displayed.
Click Yes in the warning message.
The Installation Summary screen is displayed.
Review the installation summary and click Install.
The Installation Progress screen is displayed.
Click Next.
The Configuration Progress screen is displayed.
Click Next.
The Installation Complete screen is displayed.
Click Finish when the installation is complete.
The Enterprise Object Library (EOL) Upgrade Utility upgrades the latest EOL with customizations made to the previous EOL.
After running the EOL Upgrade Utility, it generates the following reports:
EOLMergeUtility_AutoLog_<TimeStamp>.log
Captures all automated (trivial) merges.
EOLMergeUtility_ManualActionLog_<TimeStamp>.log
Captures all conflicts and the manual actions the user must perform.
EOLMergeUtility_DetailedLog_<TimeStamp>.log
Captures a detailed merge report, including post-merge validations.
The reports are generated in the following default location:
${AIA_INSTANCE}/logs/EOLUpgrade
Foundation Pack recommends running the EOL utility using the following two-step process:
Run the EOL Upgrade Utility in Report mode.
In Report mode, reports are generated and the utility does not perform the merge. Refer to these reports to preview the changes that are made when you run the utility in Upgrade mode to perform the actual merge.
Once you have run the utility in Report mode, perform all of the changes suggested in the generated EOLMergeUtility_ManualActionLog_<TimeStamp>.log before running the utility in Upgrade mode.
For information about how to address manual changes suggested in the EOLMergeUtility_ManualActionLog_<TimeStamp>.log, see Oracle Fusion Middleware Migration Guide for Oracle Application Integration Architecture (Step 5: Review the Output File).
Source aiaenv.sh from the <AIA_HOME>/aia_instances/<aia_instance>/bin.
Navigate to the <AIA_HOME>/AIAFPUpdates/Update_AIAFP111150/config folder.
Execute the following script:
ant -f EOLUpgradeUtility.xml
Run the utility in upgrade mode to perform the actual merge process.
If you have already addressed the manual changes suggested in the EOLMergeUtility_ManualActionLog_<TimeStamp>.log report generated in step 1, the report should not contain any issues after running the utility in upgrade mode. This indicates that the merge is successfully complete.
Access the <AIA_HOME>/AIAFPUpdates/Update_AIAFP111150/config folder.
Open the EOLUpgradeUtility.xml file in edit mode.
To run the utility in Upgrade mode, modify the <arg value="report"/> argument of the Java task report as follows:
<arg value="upgrade"/>
Save the file.
Access the <AIA_HOME>/AIAFPUpdates/Update_AIAFP111150/config folder.
Execute the following script:
ant -f EOLUpgradeUtility.xml
Perform the following steps to upgrade to Foundation Pack 11g Release 1 (11.1.1.5.0).
To run the upgrade script delivered with Foundation Pack 11g Release 1 (11.1.1.5.0):
Ensure that the SOA server is running.
To start the SOA server, access the Oracle WebLogic Server Administration Console:
http://<admin server hostname>:<admin server port>/console.
Navigate to Environment, and then to Servers screen. Select the Control tab and start <soa_server>.
Navigate to $AIA_INSTANCE/AIAMetaData/config.
Open the AIAConfigurationProperties.xml file in edit mode.
Search for ModuleConfiguration with the name ErrorHandler and add the following property in the ErrorHandlerModuleConfiguration.
<Property name="EH.AIACOM_OFM_EXT.IMPL">oracle.apps.aia.industry.comms.eh.AIAOrderFalloutErrorHandlerExtension</Property>
Save the file.
Navigate to <AIA_HOME>/aia_instances/<aia_instance>/bin and run the following command as per your platform to configure the installation environment:
On Linux: source aiaenv.sh
On Windows: aiaenv.bat
Navigate to the <AIA_HOME>/AIAFPUpdates/Update_AIAFP111150/config folder.
Execute the following script:
ant -f UpdateAIAFP111150.xml -DfromVersion=11.1.1.4.0
Validate the upgrade.
Access the Oracle Enterprise Manager (http://<admin server hostname>:<admin port>/em /) and log in using the valid credentials.
Navigate to Farm.
Expand Farm_soa_domain, SOA, soa infra, and default in the left panel.
Navigate to Deployed Composites in the main panel and verify that you can view the following composites:
AIAB2BErrorHandlerInterface
AIAB2BInterface
ReloadProcess
AIAAsyncErrorHandlingBPELProcess
AIAReadJMSNotificationProcess
AIAErrorTaskAdministrationProcess
Navigate to the AIA Home Page (http://<managed server hostname>:<managed server port number>/AIA/) and log in using valid credentials.
Navigate to the Composite Application Validation System, Project Lifecycle Workbench, and the AIA setup pages.
Verify that the UI tabs for each application are accessible.
Apply the Foundation Pack Rollup patch (RUP) after the Foundation Pack upgrade is performed.
Download the RUP 13247584 from MOS.
For more information on installing the RUP, refer to the readme.txt that is present inside the downloaded RUP zip file.
This section summarizes the Study, Subject, and Visit Synch: Siebel Clinical - Oracle Clinical upgrade installation instructions and contains the following topics:
Perform the following steps to upgrade the PIP installation from version 3.1 to 11.1:
Download Oracle® Study, Subject, and Visit Synchronization Integration Pack for Siebel Clinical and Oracle Clinical Release 11.1 from the edelivery page or appropriate location.
Unzip aia-sc_oc-pip.zip to any location on the server.
Navigate to sc_oc-pip > Disk1.
Follow the launch instructions for your platform. Table 11-1 lists the commands that you must use based on your platform. Installer launches the Welcome screen.
Table 11-1 Launching the PIP Installer
| Platform | To launch the Oracle AIA Installer: |
|---|---|
|
Linux x86 Linux x86 (64-bit) Solaris SPARC (64-bit) |
At the command line prompt, enter: ./runInstaller -invPtrLoc <SOA_HOME>/oraInst.loc -jreloc <location of the jre specific to your operating system. This directory should have /bin/java> |
|
Microsoft Windows 2008 (32-bit or 64-bit) |
Double-click setup.exe. |
Click Next.
Select AIA Home where Foundation Pack is installed.
Click Next.
Review the installation summary. To save the Response file, click Save.
The Response file stores the values that you previously entered and are on the summary page. If you want to do the install again, you can run a command and the installer performs a silent install with inputs from Response file instead of using the wizard.
This is an example of the command. Observe the -silent and -response arguments.
./runInstaller -invPtrLoc <SOA_Home>/oraInst.loc -jreLoc <location of the jre specific to your operating system> -silent -response <full path to response file>
Click Install. A warning message is displayed.
The warning message: This installation will overwrite your AIAHOME with new content. Should your AIAHOME have customizations that you wish to preserve, please make a backup before you proceed. Are you sure you are ready to continue with the current installation? is displayed.
Click Yes to proceed with the installation.
Or
Click No to go back to the previous screen. For backing up the AIAHOME and preserving customizations, see Section 5.1.
Click Next.
Click Finish.
Run the PIP Configuration Wizard, only when there is a change in the configuration of the installed PIP that requires a change. Else, skip this step. Note that this also imports the new seed data. Refer to the section Section 11.10 for details.
To run the PIP Upgrade Deployment Plan, execute the following commands:
On Linux: source aiaenv.sh
On Windows: aiaenv.bat
Table 11-2 Deployment commands
| Platform | Deployment Command |
|---|---|
|
Linux x86 Linux x86 (64-bit) Solaris SPARC (64-bit) |
ant -f <AIA_HOME>/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>/pips/StudySubjectVisitSyncSCandOC/DeploymentPlans/ StudySubjectVisitSyncSCandOCUpgradeDP.xml -DPropertiesFile=<AIA_HOME>/aia_instances/<aia_instance>/config/AIAInstallProperties.xml -l <location and name for log file to be created> |
|
Microsoft Windows 2008 (32-bit or 64-bit) |
ant -f <AIA_HOME>\Infrastructure\Install\AID\AIAInstallDriver.xml -DDeploymentPlan=<AIA_HOME>\pips\StudySubjectVisitSyncSCandOC\DeploymentPlans\StudySubjectVisitSyncSCandOCUpgradeDP.xml -DPropertiesFile=<AIA_HOME>\aia_instances\<aia_instance>\config\AIAInstallProperties.xml -l <location and name for log file to be created> |
You will be prompted to enter the admin user name and password. Enter the admin user name and password.
This section contains the following topics:
If you have not redeployed the OracleClinical.ear file while installing OC 4.6.5, you must undeploy the existing OracleClinical.ear file and redeploy the file that is shipped with OC 4.6.5. For more information, see Oracle Clinical Application Programming Interface Guide.
Start the Siebel Workflow Monitor agent using the following steps:
Navigate to Site Map > Administration - Server Configuration > Enterprises > Component Definitions and query for Workflow Monitor Agent.
Under Component Parameters, query for Group Name and change the group name to LS Clinical Rollup in the Component Parameter applet.
Change the action interval to 5.
Click Advanced.
Change the sleep time to 15.
Change the default task to 1.
Synchronize the components.
Navigate to Site Map > Administration - Server Management > Servers > Component Groups and query for Workflow Management.
Under Component, query for Workflow Monitor Agent.
Click Startup.
Perform the following steps to enable Oracle Clinical AQ Dequeue:
Connect to Oracle Clinical Database as an rxc user.
Execute the following command:
execute DBMS_AQADM.START_QUEUE(queue_name => 'CLINICAL_STUDY_QUEUE' , dequeue => true, enqueue => true);
commit;
This section describes the steps for importing the seed data. This is an optional step, and is necessary only when the generation of BOM or deployment plan is required after the upgrade is done.
If you are upgrading the PIP, this import will create an additional project in the AIA PLW. It will not modify the existing project in PLW. The existing project in PLW will not work for BOM and DP generation with the FP 11.1.1.5.0. If the BOM and DP generation is required, you must execute the below steps and make sure to delete the old project. Any customizations made to the old project must be done again for the new project.
Run the following commands in the command prompt to import updated seed data for PIP 3.1:
| Platform | Deployment Command |
|---|---|
|
Linux x86 Linux x86 (64-bit) Solaris SPARC (64-bit) |
cd $AIA_HOME/Infrastructure/LifeCycle/PLWImExport/ ./PLWImport.sh -f $AIA_HOME/data/StudySubjectVisitSyncSCandOC/ PLWSeedData/StudySubjectVisitSyncSCandOCSeed.xml |
|
Microsoft Windows 2008 (32-bit or 64-bit) |
cd %AIA_HOME%\Infrastructure\LifeCycle\PLWImExport\ .\PLWImport.sh -f %AIA_HOME%\data\StudySubjectVisitSyncSCandOC\ PLWSeedData\StudySubjectVisitSyncSCandOCSeed.xml |
Verify in the PLW screen that project StudySubjectVisitSyncSCandOC with Version 11.1 and project Industry as blank is present.
|
 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
