Starting the Oracle Fusion Middleware and Oracle SOA Suite Domains on the Target Database
To start the domains on the target container database (CDB), complete the following steps:
Start the Oracle Fusion Middleware Domain
After updating the Oracle Fusion Middleware domain configuration files to point to the new target database, you can shut down the source database, then start the Oracle Fusion Middleware domain on the target database and check the JDBC connections:
-
To start the Oracle Fusion Middleware domain, start the Administration Server and the Managed Servers. For example:
cd /u01/oracle/middleware/domains/fmw_domain ./startWebLogic.sh cd /u01/oracle/middleware/domains/fmw_domain/bin ./startManagedWebLogic.sh infra_server1 http://192.168.56.92:7001
-
In the WebLogic Server Administration Console, check the server status:
-
Check the connection status:
Start the Oracle SOA Suite Domain
After updating the Oracle SOA Suite domain configuration files to point to the new target database, you can shut down the source database, then start the Oracle SOA Suite domain on the target database and check the JDBC connections:
-
To start the Oracle SOA Suite domain, start the Administration Server and the Managed Servers. For example:
cd /u01/oracle/middleware/domains/soa_domain ./startWebLogic.sh cd /u01/oracle/middleware/domains/soa_domain/bin ./startManagedWebLogic.sh soa_server1 http://192.168.56.92:7010
-
In the WebLogic Server Administration Console, check the server status:
-
Check the connection status:
-
Check the Oracle SOA Suite Managed Server log file. For example:
… <Aug 20, 2020 3:23:43,616 PM CEST> <Warning> <oracle.soa.scheduler> <BEA-000000> <No row exists in table soaqtz_JOB_DETAILS for lock named: VerificationSessionPurgeJob-QLCKSEP-DEFAULT> [EL Info]: 2020-08-20 15:23:44.079--ServerSession(1948318745)--EclipseLink, version: Eclipse Persistence Services - 2.6.5.v20170607-b3d05bd [EL Info]: 2020-08-20 15:23:44.08--ServerSession(1948318745)--Server: 12.2.1.3.0 [EL Info]: 2020-08-20 15:23:44.157--ServerSession(1948318745)--/file:/u01/oracle/middleware/soa12213/soa/soa/modules/oracle.soa.fabric_11.1.1/tracking-fabric.jar_soa_local_resiliency_persistence_unit login successful SOA Platform is running and accepting requests. Start up took 17561 ms, partition=DOMAIN <Aug 20, 2020 3:23:47,156 PM CEST> <Warning> <oracle.soa.healthcheck> <BEA-000000> <On startup, health check id 293 failed for category 'Startup'. Ran 6 checks. Number of failures=1, errors=1, warnings=0.>
-
Check Oracle SOA Suite URLs. For example:
-
http://192.168.56.92:7013/wsm-pm/
-
http://192.168.56.92:7013/soa-infra/
-
http://192.168.56.92:7013/integration/worklistapp
-
http://192.168.56.92:7013/sdpmessaging/userprefs-ui
-
http://192.168.56.92:7013/soa/composer
-
http://192.168.56.92:7013/integration/services/IdentityService/identity?WSDL
-
-
Perform an Oracle SOA Suite health check:
- Sign in to the source environment. For example,
soa-host01.example.com
. - Change to the
oracle
user:sudo su - oracle
- Create a directory to store the healthcheck files. For
example:
mkdir -p /u01/db_exp/soa_healthcheck
- Start WLST and connect to the SOA Server. For
example:
/u01/oracle/middleware/soa12213/oracle_common/common/bin/wlst.sh connect('weblogic','manager1','t3://192.168.56.92:7013') // soa1_server1
- Sign in to the source environment. For example,
- Enter the following commands and review the output in the generated
SOA Health Checks
Reports:
executeHealthCheckAndGenerateReport('DatasourceCheck','/u01/oracle/soa_healthcheck/DatasourceCheck.html') executeHealthCheckAndGenerateReport('ServiceCheck','/u01/oracle/soa_healthcheck/ServiceCheck.html') executeHealthCheckAndGenerateReport('SOAAppCheck','/u01/oracle/soa_healthcheck/SOAAppCheck.html') executeHealthCheckAndGenerateReport('JDBCPoolsCheck','/u01/oracle/soa_healthcheck/JDBCPoolsCheck.html') executeHealthCheckAndGenerateReport('SOALibraryCheck','/u01/oracle/soa_healthcheck/SOALibraryCheck.html') executeHealthCheckAndGenerateReport('MemoryCheck','/u01/oracle/soa_healthcheck/MemoryCheck.html')