Deploying an ADF Java EE Application 8-7
8.3 Preparing the Application
Before you deploy an ADF application to an application server, you must perform prerequisite tasks within JDeveloper to prepare the application for deployment.
The prerequisite tasks are:
■
Creating a connection to the target application server
■
Creating deployment profiles
■
Creating deployment descriptors
■
Migrating applicable security, credentials, identities, and policies
■
Replicating memory scopes in a clustered environment
■
Enabling the application for ADF MBeans optional
8.3.1 How to Create a Connection to the Target Application Server
You can deploy applications to the application server via JDeveloper application server connections.
If your application involves customization using MDS, you should register your MDS repository with the application server:
■
WebLogic: register the MDS into the WebLogic Domain For more information about registering MDS in WebSphere, see the Oracle Fusion
Middleware Administrators Guide.
■
WebSphere: register the MDS into the WebSphere Cell For more information about registering MDS in WebSphere, see the Oracle Fusion
Middleware Third-Party Application Server Guide.
To create a connection to an application server: 1.
Launch the Application Server Connection wizard. You can:
■
In the Application Server Navigator, right-click Application Servers and choose New Application Server Connection.
■
In the New Gallery, expand General, select Connections and then Application Server Connection
, and click OK.
■
In the Resource Palette, choose New New Connections Application Server
.
2. In the Create AppServer Connection dialog Usage page, select Standalone Server.
3.
In the Name and Type page, enter a connection name.
4. In the Connection Type dropdown list, choose:
■
WebLogic 10.3 to create a connection to Oracle WebLogic Server
■
WebSphere Server 7.x to create a connection to IBM WebSphere Server
5. Click Next.
6.
On the Authentication page, enter a user name and password for the administrative user authorized to access the application server.
7. Click Next.
8-8 Java EE Developers Guide for Oracle Application Development Framework
8.
On the Configuration page, enter the information for your server: For WebLogic:
■
The Oracle WebLogic host name is the name of the WebLogic Server instance containing the TCPIP DNS where your application .jar,.war,.ear will
be deployed.
■
In the Port field, enter a port number for the Oracle WebLogic Server instance on which your application .jar,.war,.ear will be deployed.
If you don’t specify a port, the port number defaults to 7001.
■
In the SSL Port field, enter an SSL port number for the Oracle WebLogic Server instance on which your application .jar,.war,.ear will be
deployed.
Specifying an SSL port is optional. It is required only if you want to ensure a secure connection for deployment.
If you don’t specify an SSL port, the port number defaults to 7002.
■
Select Always Use SSL to connect to the Oracle WebLogic Server instance using the SSL port.
■
Optionally enter a WebLogic Domain only if Oracle WebLogic Server is configured to distinguish nonadministrative server nodes by name.
For WebSphere:
■
In the Host Name field, enter the name of the WebSphere server containing the TCPIP DNS where your Java EE applications .jar, .war, .ear are
deployed. If no name is entered, the name defaults to localhost.
■
In the SOAP Connector Port field, enter the port number. The host name and port are used to connect to the server for deployment. The default SOAP
connector port is 8879.
■
In the Server Name field, enter the name assigned to the target application server for this connection.
■
In the Target Node field, enter the name of the target node for this connection. A node is a grouping of Managed Servers. The default is machineNode01,
where machine is the name of the machine the node resides on
■
In the Target Cell field, enter the name of the target cell for this connection. A cell is a group of processes that host runtime components. The default is
machineNode01 ,Cell where machine is the name of the machine the node
resides on.
■
In the Wsadmin script location field, enter, or browse to, the location of the wsadmin script file to be used to define the system login configuration for
your IBM WebSphere application server connection. The default location is websphere-homebinwsadmin.sh
for UnixLinux and websphere-homebinwsadmin.bat
for Windows.
9. Click Next.
