4 Deploy Oracle DMW on the WebLogic Server

By default Oracle DMW supports and requires HTTPS. If you prefer to use HTTP, you can follow instructions in Section 4.2 instead of Section 4.1 to enable the use of HTTP.

Follow instructions in one of the following sections:

Section 4.1, "Deploy with Default Support for HTTPS"
Section 4.2, "Alternative Oracle DMW Deployment Disabling HTTPS Support"

4.1 Deploy with Default Support for HTTPS

Deploy the Oracle DMW application tier on the WebLogic Server.

Copy patch 16691856 from the media pack or your staging area to your local computer so that you can select it from the WebLogic Administration Console.
Unzip the patch and locate the dmwapp.ear file in the software directory.
Log in as the admin user to the WebLogic Administration Console. The URL is:

http(s)://host_name.company_domain.com:port/console/

for example:

http(s)://machine.example.com:1234/console
In the Weblogic Administration Console, select Deployments from Domain Structure. A list of all deployed applications appears.

If dmwapp is included in the list, select its check box and:
1. Stop it by selecting Force Stop Now from the Stop drop-down list.
2. Delete it by clicking Delete. dmwapp disappears from the list.
Click Install. The Install Application Assistant is displayed.
In the paragraph beginning Locate deployment to install and prepare for deployment, click the link upload your file(s).
In the Deployment Archive line, click Browse and select dmwapp.ear from your local computer and click Open. The system returns you to the Install Application Assistant.
In the Install Application Assistant click Next. This uploads dmwapp.ear to a server directory. This may take some time.

When the process is complete, the system displays the path to the server directory.
In the Install Application Assistant click Next.
Select Install this deployment as an application and click Next. The system displays a list of servers.
Select the managed server to which you are installing the application— DMWServer—and click Next. Optional settings appear.
Under General, in the Name field, enter: dmwapp and click Finish. The system displays a summary of your selections.
Click Finish. The system deploys the Oracle DMW middle tier on the managed server. After a successful deployment ta new page called Settings for dmwapp appears with the Overview tab dispayed.
Click Deployments under Domain Structure to verify that dmwapp is included in the Deployments list and its state is Active.
Go to the login screen to check that the application is running. The URL is:

http://host_name.company_domain.com:port/lsw/dme/faces/DmeLogin.jsf

For example:

http://srv123.example.com:1234/lsw/dme/faces/DmeLogin.jsf

4.2 Alternative Oracle DMW Deployment Disabling HTTPS Support

By default Oracle DMW requires HTTPS. If you prefer to use HTTP, you can do the following to enable the use of HTTP.

For further information, see the Oracle® Fusion Middleware Deploying Applications to Oracle WebLogic Server11g Release 1 (10.3.6) at:

HTML: http://docs.oracle.com/cd/E23943_01/web.1111/e13702/intro.htm
PDF: You can download a PDF version of the same document in the same location by right-clicking the PDF link and selecting Save Target As.

Log in to the WebLogic Server and create a tmp directory.
Copy Oracle DMW patch 16691856 from the media pack or your staging area to the WebLogic Server computer. Unzip the patch to the tmp directory, creating the software directory containing the dmwapp.ear and plan.xml files.
Open the software directory.
Copy the dmwapp.ear file and the plan.xml file to the tmp directory and delete the software directory. The tmp directory now contains only the dmwapp.ear and plan.xml files.
Open a shell window and set up the environment:

source WL_HOME/server/bin/setWLSEnv.sh

for example:
```
source /app/oracle/product/middleware/wlserver_10.3/server/bin/setWLSEnv.sh
```
Change directory to the tmp directory.
Deploy Oracle DMW using the deployment plan (Plan.xml) that disables HTTPS for Oracle DMW. The basic command required is the following, but it is not secure due to the presence of the password passed as a parameter:
```
java weblogic.Deployer -adminurl t3://host_name.your_company_domain.com:port_number -username WLS_USER -password WLS_PASSWORD -targets DMWServer -deploy dmwapp.ear -name dmwapp -upload -plan Plan.xml
```
To avoid passing in the username and password for a more secure installation, store the encrypted username and password in a configuration file using the WebLogic Scripting Tool (WLST) storeUserConfig command as described in the WebLogic Scripting Tool Command-Line Reference in the Oracle® Fusion Middleware Deploying Applications to Oracle WebLogic Server 11g Release 1 (10.3.6) at http://docs.oracle.com/cd/E23943_01/web.1111/e13702/wldeployer.htm#DEPGD318.
1. Enter java weblogic.WLST to start the WebLogic Scripting Tool (WLST).
2. Enter storeUserConfig.
Omit both the -username and -password options in the basic command to weblogic.Deployer to use the values stored in the default configuration file. If you want to use a specific configuration file and key file, rather than the default files, use the -userconfigfile and -userkeyfile options to weblogic.Deployer.

You can then use the command:
```
java weblogic.Deployer -adminurl t3://host_name.your_company_domain.com:port_number -targets DMWServer -deploy dmwapp.ear -name dmwapp -upload -plan Plan.xml
```
Enter exit() to exist the Weblogic Scripting Tool, then exit to exit the shell.
Go to the login screen to check that the application is running. The URL is:

http://host_name.company_domain.com:port/lsw/dme/faces/DmeLogin.jsf

For example:

http://srv123.example.com:1234/lsw/dme/faces/DmeLogin.jsf