Migrating a Java EE Application to Oracle Java Cloud Service

To copy files to your Oracle Database Cloud - Database as a Service instance:

1. Click the Start button, search for WinSCP, then click it.



2. On the WinSCP Login page, click Session and enter the following details:

   • File protocol: SCP

   • Host name: 111.111.111.111 (Public IP address of your Oracle Database Cloud - Database as a Service instance)

   • Username: oracle

   • Password: Leave blank

   • Private key file: Use the private key (ppk) file that you created using PuTTYgen. The corresponding public key was used when the Oracle Database Cloud - Database as a Service instance was created.

3. Click Login.



4. A dialog box is displayed. Click Continue.

5. Enter the passphrase that you provided while generating the ppk file and click OK.



6. After logging in, drag and drop the Medrec.sql file from your local machine to the /tmp directory of your Oracle Database Cloud - Database as a Service instance.

7. Close WinSCP after the file transfer is complete.

To connect to the machine:

1. Open PuTTY and navigate to SSH > Auth.

2. Click Browse and specify the location of the ppk file you created using the private key with PuTTYgen.

3. Navigate to Session.

4. Enter the Public IP of y/our Oracle Database Cloud - Database as a Service instance and click Open.

5. Enter oracle as the user name and click Enter.

You are now logged in to the machine.

In this step, you will create a user in the Oracle PDB database and run SQL queries to create the table in the database.

Enter commands such as the ones given below, with information you can find in the instance shown.

Note: You obtain the DBConnectString from the Connect Descriptor as shown in the image. For example: Medrec:1111/PDB1.environment.oraclecloud.

cd /tmp
sqlplus DBuser/DBPassword@DBConnectString
create user medrec identified by medrec;
grant DBA to medrec;
connect medrec/medrec@DBConnectString
@Medrec.sql
exit;

Close PuTTY.

Now, you have populated the database with the required data. This completes the database migration.

Your WebLogic Server is running on your local machine.

1. Launch the WebLogic Server Administration Console on your local machine by entering the following URL in your browser:

   http://localhost:7001/console

   When prompted, enter your username and your password, and click Login.

   In the Administration Console, you can view the environment for the application.

2. Close the Administration Console on your local machine.

   You will replicate the environment onto a Java Cloud Service instance.

3. Navigate to the Oracle Java Cloud Service Console and make a note of the data highlighted below.



Note: This is an example only. The name of the service instance here is "Medrec," but unless you named your service instance "Medrec," your service instance name will be different. The information you need to note will be the same.

4. From the menu, click Open WebLogic Server Console.



5. You will receive a message about an untrusted site. Allow the exception.

6. When the WebLogic Server Administration Console Welcome screen is displayed, enter your username and password, and click Login

Now that the Administration Console is displayed, you create a data source in your Oracle Java Cloud Service instance.

1. In the Change Center of the Administration Console, click Lock & Edit.

   Note: You must click Activate Changes after each modification.

   

2. Click Services > Data Sources. Then, click New > Generic Data Source.



3. Enter the following information and click Next:

   Name: MedRecGlobalDataSourceXA

   JNDI Name: jdbc/MedRecGlobalDataSourceXA

   Database Type: Oracle



4. Select Oracle's Driver (Thin XA) for Service connections; Versions: Any from the Database Driver drop down menu and click Next.



5. Leave the default values as-is and click Next.



6. Enter the following details and click Next.

   Database Name: Name of your database.

   Host Name: Name of your Oracle Database Cloud - Database as a Service instance, in this example, Medrec)

   Database User Name: medrec

   Port: 1521

   Password: medrec

   Note: See the Prerequisites section of this document if you need help finding the database and host name for the database.



7. Click Test Configuration. If you see the message, Connection test succeeded, click Next.



8. Select the cluster as the data source target and click Finish.



9. Click Activate Changes.



10. Click Lock & Edit.

In this section, you create a work manager in the cloud.

1. In the Domain Structure, click Environment > Work Managers and click New.



2. Select Work Manager and click Next.



3. In the Name field, enter weblogic.wsee.mdb.DispatchPolicy and click Next.



4. Select the cluster as the deployment target and click Finish.

You have created a work manager.

In this section you create messaging resources in the cloud.

1. Click Lock and Edit.

2. Under Domain Structure, click Services > Messaging < JMS Servers and click New.



3. In the Name field, enter MedRecJMSServer and click Next.



4. Select the managed server as the target and click Finish.



5. Click Services > Messaging > Store-and-Forward Agents and click New.



6. Enter the following details and click Next.

   Name: WsrmAgent

   Agent Type: Both



7. Select the managed server as the target and click Finish.



8. Click Services > Messaging > JMS Modules and click New.



9. In the Name field, enter MedRec-jms, leave the values for the remaining fields as-is, and click Next.



10. Select the cluster as the Target and click Next.



11. Select the Would you like to add resources to this JMS module? option and click Finish.



12. In the Summary of Resources section, click New. On the Create a New JMS System Module Resource page, select Queue and click Next.



13. Enter the following details and click Next.

    Name: com.oracle.medrec.jms.PatientNotificationQueue

    JNDI Name: com.oracle.medrec.jms.PatientNotificationQueue



14. Click Create a New Subdeployment.

    You will use the subdeployment for the next two queues you will create.



15. Enter MedRecJMSServer as the Subdeployment Name and click OK.



16. Select MedRecJMSServer as the Subdeployment and as the target JMS target server and click Finish.



17. Use the same procedure for the following two queues: com.oracle.medrec.jms.RecordToCreateQueue and weblogic.wsee.DefaultQueue. Their JNDI names are same as their names. Use the following illustrations as a reference:










18. Click Activate Changes.

You have created messaging resources.

1. Click Lock and Edit.

2. Click Services > Mail Session and click New.



3. Enter the following details and click Next.

   Name: mail/MedRecMailSession

   JNDI Name: mail/MedRecMailSession

   Java Mail Properties:

   mail.host=mail.mycompany.com

   mail.user=joe



4. Select the cluster as the Target and click Finish.



5. Click Activate Changes.

You have created a mail session.

1. Click Lock & Edit.

2. Navigate to Environment > Clusters and click the cluster name, MedrecDo_cluster.



3. Enter localhost as the cluster address and click Save.



Note: The cluster address has changed, so you must restart the managed server.

4. To shut down the server:

1. Navigate to Environment > Servers. On the Summary page, click the Control tab. Select the check box for the managed server MedrecDo_server_1. Select Force Shutdown Now from the Shutdown drop-down menu.



2. Click Yes on the Server Life Cycle Assistant page.

5. After the managed server shuts down, restart it. For instructions, see Configuring the Cluster.

1. On the Servers list, select the managed server.



2. On the Server Life Cycle Assistant dialog, click Yes.



6. Click Activate Changes.

7. Important: Restart the Managed Server. For instructions, see Configuring the Cluster.

You have successfully configured the environment.

The MedRec source code is located at <WLS_HOME>\user_projects\applications\medrec, where WLS_HOME is the WebLogic Server home directory you specified when you installed WebLogic Server.

You only need to copy the .ear directories:

• <WLS_HOME>\user_projects\applications\medrec\modules\medrec\assembly\target\medrec.ear

• <WLS_HOME>\user_projects\applications\medrec\modules\physician\assembly\target\physician.ear

1. Copy the .ear directories to a different location, for example, D:\.

   Example used here:

   D:\medrec\modules\medrec\assembly\target\medrec.ear

   D:\medrec\modules\medrec\assembly\target\physician.ear

   Note: You can choose any location for your working directory. The D: directory is an example in this tutorial.

1. Navigate to D:\medrec\modules\medrec\assembly\target.

2. Rename medrec.ear to medrec1.ear.

3. Use 7zip (or equivalent software) to extract medrec1.ear to D:\medrec.ear.

4. Navigate to D:\medrec\modules\physician\assembly\target.

5. Rename physician.ear to physician1.ear.

6. Use 7zip (or equivalent software) to extract physician1.ear to D:\physician.ear.

You have now converted the application to an exploded format.

In this section, you modify the weblogic-application.xml file to use the filtering classloader.

Note: Use any XML editor or Notepad. Do not use WordPad.

Replace the content in the following two files:

• D:\medrec\modules\medrec\assembly\target\medrec.ear\META-INF\weblogic-application.xml

• D:\medrec\modules\physician\assembly\target\physician.ear\META-INF\weblogic-application.xml

...with the modified weblogic-application.xml content.

Original weblogic-application.xml:

 <wls:weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:wls="http://www.bea.com/ns/weblogic/weblogic-application"
      xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-application
      http://www.bea.com/ns/weblogic/weblogic-application.xsd
      http://java.sun.com/xml/ns/j2ee
      http://java.sun.com/xml/ns/j2ee/j2ee_1_4.xsd">
  <wls:application-param>
    <wls:param-name>webapp.encoding.default</wls:param-name>
    <wls:param-value>UTF-8</wls:param-value>
  <wls:application-param>
</wls:weblogic-application> 

Modified weblogic-application.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-application"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
     http://java.sun.com/xml/ns/javaee/javaee_5.xsd
     http://xmlns.oracle.com/weblogic/weblogic-application
     http://xmlns.oracle.com/weblogic/weblogic-application/1.5/weblogic-application.xsd">
  <wls:application-param>
    <wls:param-name>webapp.encoding.default</wls:param-name>
    <wls:param-value>UTF-8</wls:param-value>
  </wls:application-param>
  <prefer-application-packages>
    <package-name>org.apache.commons.*</package-name>
  </prefer-application-packages>
</wls:weblogic-application> 

The schema location now uses the filtering classloader.

In this section, you use WinSCP to copy the medrec.ear and physician.ear directories from the current location to the /tmp folder in the Oracle Java Cloud Service instance.

To connect to the Oracle Java Cloud Service instance:

1. On the WinSCP Login page, click Session and enter the following details:

   File protocol: SCP

   Host name: Enter the Public IP of your Oracle Java Cloud Service instance

   Username: opc

   Password: Leave blank

   Private key: Use the ppk file that you created using PuTTYgen

2. Click Login.

3. Copy the two .ear files to the /tmp folder of the Oracle Java Cloud Service instance.

4. After the file transfer is complete, close WinSCP.

You have now copied the application files from your local installation to the Oracle Java Cloud Service.

Use PuTTY to change permissions to 777 for the .ear files.

1. Log in as opc and specify your passphrase when prompted.

2. Execute the following commands:

   sudo su
   chmod -Rf 777 /tmp/medrec.ear
   chmod -Rf 777 /tmp/physician.ear
   

You have now changed file permissions.

1. Install the jsf-1.2.war file as a shared library.

   1. Click Lock & Edit.

   2. Select Deployments and click Install.

   

   3. Specify the path as /u01/app/oracle/middleware/wlserver/common/deployable-libraries/jsf-1.2.war and click Next.

   

   4. Select Install the deployment as a library and click Next.

   

   5. Select the managed server as the target.

   

   6. Click Finish.

   7. Click Activate Changes.

      A message is displayed, directing you to restart the server.

   

   8. Restart the Managed Server. See the instructions in Configuring the Cluster.

2. Deploy the medrec.ear file as an application.

   1. Click Lock & Edit.

   2. On the Deployments table, click Install.

   

   3. Specify the path as /tmp/medrec.ear.

   

   4. Select Install this deployment as an application.

   

   5. Select the managed server as the target.

   

   6. Click Finish.

   

   7. Click Activate Changes.

      A message stating the servers need to restarted is displayed.

   

   8. Restart the Managed Server. For instructions, see Configuring the Cluster.

3. Click the Next button on the Deployments table until the MedRec application is displayed. Select the check box for the medrec application and click Start > Servicing all requests.



4. Click Yes on the Start Application Assistant page.

5. Repeat the preceding steps to deploy the physician.ear application.

You have now deployed the MedRec application.

1. Navigate to https://IP_of_the_Load_Balancer_Instance:443/medrec and click Start using MedRec.

2. Accept the security exception.



3. Test the application to validate that the migration was successful.

   Note: You can find the credentials on the home page.

   1. Click Start.

   2. Click Register to register a patient.

   3. Click Login to log in as Administrator and approve the patient registration.

   4. Log in as the patient and edit the profile information.

   5. Log in as the physician, search for the patient, and prescribe medication.

You have now accessed and tested the MedRec application.