38 Testing and Deploying Your WebCenter Application

38.3.1.1.1 Packaging the Database Connections

If your custom WebCenter application contains JDBC database connections, you'll need to choose how JDeveloper will migrate those database connections to the Oracle WebLogic Managed Server. You can choose from:

• Global data source:

  Oracle recommends that you choose this type of data source if you plan to deploy an application EAR file to a Managed Server running in production mode using Fusion Middleware Control, the Oracle WebLogic Administration Console, or using a WLST (wldeployer) command.

  To choose a global data source, deselect the Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment checkbox when you create the EAR file so that JDeveloper does not create an application-level data source with password indirection. Instead, create the global data source using Oracle WebLogic Administration Console after deploying an application to a Managed Server in production mode. For more information on creating global data sources, see the section "Creating a JDBC Data Source" in Oracle Fusion Middleware Configuring and Managing JDBC for Oracle WebLogic Server.

• Application-level data source with password indirection:

  JDeveloper generates an application-level data source with password indirection by default when you run an application on the Integrated WLS. That is, the Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment checkbox is selected by default in the Application Properties dialog, as shown in Figure 38-3.

  Figure 38-3 Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment Checkbox

  
  Description of "Figure 38-3 Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment Checkbox"
  
  

  To generate an application-level indirection data source, JDeveloper does the following:

  • Generates a <connection>-jdbc.xml file (such as WC-jdbc.xml) for each connection in the Application Resource.

  • Sets the indirect password attribute in the <connection>-jdbc.xml file:

    <jdbc-driver-params>
    <use-password-indirection>true</use-password-indirection>
    </jdbc-driver-params>
    

  • Updates weblogic-application.xml to add each <connection>-jdbc.xml file as a module. For example:

    <module>
    <name>WC</name>
    <type>JDBC</type>
    <path>META-INF/WC-jdbc.xml</path>
    </module>
    

  • Adds a resource reference to each JDBC JNDI name in the web.xml file, if this file exists. For example:

    <resource-ref>
    <description>WC-Connection</description>
    <res-ref-name>jdbc/WCDS</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref> 
    

  If you choose to generate an application data source with password indirection, then you must add credential mappings using the Oracle WebLogic Administration Console to be able to activate the application. For more information on adding credential mappings, see the section "Creating a JDBC Data Source" in Oracle Fusion Middleware Configuring and Managing JDBC for Oracle WebLogic Server.

  Note:

  Do not use WLST commands to deploy applications that use application-level data sources with password indirection, as WLST cannot set password indirection credential mappings on the server.

38.3.1.1.2 Packaging Application Security Data

The following is applicable if you have configured security in your application using the Configure ADF Security wizard, or the application contains connections with secure attributes such as a database connection password or external applications with shared or public credentials:

• Packaging Credentials

• Packaging Identity Data

• Packaging Application Policies

Packaging Credentials

If you do not intend to migrate credentials, then deselect the Credentials checkbox in the Security Deployment Options section in the Application Properties dialog (see Figure 38-4).

Figure 38-4 Security Deployment Options

Description of "Figure 38-4 Security Deployment Options"

If you retain the default selection in the Security Deployment Options section, then the credential migration will behave as follows, depending on whether the WebLogic domain is in development or production mode:

• When you deploy a custom WebCenter application to a Managed Serverrunning in production mode, secure attributes of the connections packaged within your application and any shared or public credentials specified for external applications are not migrated to the domain-level credential store. This is because secure properties are likely to be different between development and production environments. Therefore, you must reconfigure secure attributes of connections and shared or public credentials for external applications using WLST commands or Fusion Middleware Control, as described in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

  For more information on credential migration behavior, see the section "Configuring the Credential Store" in Oracle Fusion Middleware Security Guide.

• When you deploy a custom WebCenter application in development mode, you must first enable credential migration. To enable credential migration for an application to be deployed in development mode, start the Managed Server with -Djps.app.credential.overwrite.allowed=true, by adding the following option to the setDomainEnv.cmd or setDomainEnv.sh file located in domain\bin:

  set EXTRA_JAVA_PROPERTIES=-Djps.app.credential.overwrite.allowed=true %EXTRA_JAVA_PROPERTIES%
  

Packaging Identity Data

In Figure 38-4, in the Security Deployment Options section, the Users and Groups checkbox is selected by default. This indicates that the users and groups defined in the application's jazn-data.xml file will be migrated to the identity store configured for the WebLogic Managed Server, if the authenticator configured in the domain allows creation of users and groups. When migrating the identify store, you should deselect this option as users and groups defined in the identity store configured for the Managed Server should be used to access the application.

Packaging Application Policies

When the Application Policies checkbox is selected, then the jps.policystore.migration parameter in the weblogic-application.xml file is set to OVERWRITE. This means that during application deployment and redeployment, the application policies packaged with the application will be overwritten on the domain-level policy store for the domain to which the application is being deployed.If the Application Policies checkbox is not selected, then the jps.policystore.migration parameter is set to MERGE. This means that the application policies will be migrated during application deployment but not during redeployment, and the existing application policies will not be overwritten.

38.3.1.2.1 Creating the WAR Deployment Profile

To create a project-level WAR deployment profile:

1. In JDeveloper, in the Application Navigator, right-click ViewController and select New.

2. In the New Gallery, expand General, select Deployment Profiles, then WAR File, and then click OK.

3. In the Create Deployment Profile -- WAR File dialog, enter a name for your deployment profile and click OK.

4. In the WAR Deployment Profile Properties dialog, select the Specify Java EE Web Context Root option, enter a meaningful context root, and then click OK.

   The "context root" is the part of the Web application's URL that is appended to the server ID and port number, and to which the servlet name is in turn appended. For example, in the URL http://www.hostname.example.com/myWebsite/HelloWorld, /myWebsite is the context root (or virtual path), and HelloWorld is the name of the servlet the user is accessing.

5. In the Project Properties dialog, click OK.

38.3.1.2.2 Creating the EAR Deployment Profile

To create an application-level EAR deployment profile:

1. In JDeveloper, in the Application Navigator, right-click the application and select New.

2. In the New Gallery, expand General, select Deployment Profile, then EAR File, and then click OK.

3. In the Create Deployment Profile – EAR File dialog, enter a name for your deployment profile and click OK.

4. In the Edit EAR Deployment Profile Properties dialog, select Application Assembly, then select the project WAR you want to make available in the project file and and click OK.

5. In the Application Properties dialog, select the deployment options to use and click OK.

   For a description of the Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment option, see Section 38.3.1.1.1, "Packaging the Database Connections." For a description of the Deployment Security Options, see Section 38.3.1.1.2, "Packaging Application Security Data."

6. In the Application Navigator, right-click the application name, choose Deploy, deployment profile name, to, and then choose to EAR file. This creates the EAR file in the deploy folder located in JDEV_HOME\mywork\application_name\deploy\, as shown in Figure 38-5.

   Figure 38-5 EAR Status in Deployment - Log

   
   Description of "Figure 38-5 EAR Status in Deployment - Log"