../E63259-01.epub /> ../E63259-01.mobi />

7 Deploying and Testing Your Portal Framework Application

This chapter describes how to run, deploy, and test Portal Framework applications using the Integrated WebLogic Server (IntegratedWebLogicServer), and how to deploy your applications from JDeveloper to a WebLogic Managed Server.

This chapter includes the following topics:

Note:

For information about deploying Oracle WebCenter Portal Personalization files, see Section 66.3, "Deploying Personalization Files." For information about deploying Portal Framework applications through other mechanisms, such as Oracle Enterprise Manager Fusion Middleware Control, Oracle WebLogic Administration Console, and WebLogic Scripting Tool (WLST) commands, see the "Deploying Portal Framework Applications" chapter in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

7.1 Introduction to Oracle WebLogic Servers

This section provides an overview of the Integrated WebLogic Server and Oracle WebLogic Managed Servers. Using Oracle JDeveloper, you can test and deploy your applications on the Integrated WebLogic Server, and deploy applications to an Oracle WebLogic Managed Server that resides outside Oracle JDeveloper for staging and further testing or, if you have the required permissions, to an actual production environment.

Integrated WebLogic Server

The Integrated WebLogic Server comes packaged with Oracle JDeveloper. The Integrated WebLogic Server connection appears as IntegratedWebLogicServer in the Resource Palette under IDE Connections > Application Server. With the Integrated WebLogic Server, you can quickly and easily test your application at design time without needing to package the application and create and configure a WebLogic Managed Server.

When you run an application, an Integrated WebLogic Server instance for that application automatically starts. You can also start the instance manually by choosing the Run > Start Server Instance (IntegratedWebLogicServer) menu option in JDeveloper. Doing so creates a single server instance for all applications; any applications you run will then use this server instance.

Testing Portal Framework applications on the Integrated WebLogic Server helps to improve design-time tasks by:

  • Optimizing deployment: the requirement to archive and copy files to a separate server for design time testing is eliminated.

  • Instantly refreshing changes to the application: you can directly run most files from project directories, which enables you to make selected changes and refresh these changes while the application is running. For example, you can modify a task flow on a JSPX page, then refresh the page in the browser to view your changes without redeploying the application.

  • Removing the requirement to undeploy applications after testing and debugging. If you stop the Integrated WebLogic Server, however, applications running on it are automatically undeployed.

To learn more about testing a Portal Framework application on the Integrated WebLogic Server, refer to Section 7.2, "Deploying a Portal Framework Application to the Integrated WebLogic Server."

WebLogic Managed Server

An Oracle WebLogic Managed Server resides outside of Oracle JDeveloper as part of a domain, and is managed by an Administration server within that domain. A WebLogic Managed Server hosts applications, along with the libraries and other resources needed by those applications. A domain, which is a logically related group of Oracle WebLogic Server resources, can have any number of Managed Servers. Managed Servers can be configured to run applications in a test environment, a production environment, or both.

To learn more about deploying a Portal Framework application to an Oracle WebLogic Managed Server, see Section 7.3, "Deploying a Portal Framework Application to a WebLogic Managed Server."

7.2 Deploying a Portal Framework Application to the Integrated WebLogic Server

The Integrated WebLogic Server is preconfigured so that you can run applications within Oracle JDeveloper without needing to create deployment profiles. However, when the Integrated WebLogic Server instance stops, the application is undeployed and therefore becomes unavailable. For a more persistent testing scenario, you can also deploy your application to the Integrated WebLogic Server. These two options are described in the following subsections:

7.2.1 Running a Portal Framework Application in the Integrated WebLogic Server

To run a Portal Framework application, you can right-click the Portal project in the Projects section in the Application Navigator and choose Run, or select Run from the Run menu or click the Run icon from the toolbar to run the current project.

When you run an application in JDeveloper, a server instance named after the application is automatically created. While the application is running, you can switch back and forth between JDeveloper and your browser to make changes at design time in your application, save the changes and then refresh your JSPX page in your browser to view those changes. While in JDeveloper, you can also watch the progress of your applications, as well as stop the server instance (and thus stop the application).

When you run the application page or project, it triggers the packaging and deployment of your Portal Framework application on an Integrated WebLogic Server instance named after the application. You can stop instances of the Integrated WebLogic Server by using the Run Manager panel (shown in Figure 7-1). You can access the Run Manager panel by selecting Run Manager from the View menu. To stop the Integrated WebLogic Server instance, just select IntegratedWebLogicServer and click the red Terminate icon on the Run Manager tab. You can also stop the instance using the red Terminate icon on the toolbar or the one in the Log window, or by selecting the Terminate option from the Run menu.

Use the IntegratedWebLogicServer Log window (shown in Figure 7-2) to view how the activity is progressing.

Figure 7-2 DefaultServer Log Window

Description of Figure 7-2 follows
Description of "Figure 7-2 DefaultServer Log Window"

Note:

Secure attributes and credentials are migrated by default when running a Portal Framework application on the Integrated WebLogic Server.

7.2.2 Deploying a Portal Framework Application to the Integrated WebLogic Server

When you run your Portal Framework application as described in Section 7.2.1, "Running a Portal Framework Application in the Integrated WebLogic Server", the application is undeployed and becomes unavailable if the Integrated WebLogic Server instance stops. Even if you start IntegratedWebLogicServer again, the application remains unavailable. For a more persistent testing scenario, you can deploy your application to the Integrated WebLogic Server by using the Deploy option. This deployed application will always be available while the Integrated WebLogic Server is running.

For more information about deploying applications, see the "Deploying Fusion Web Applications" chapter in Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

Note:

Before deploying your Portal Framework application if you need to create local data sources for Oracle WebCenter Portal and for Activities used by the Analytics task flow, see Section 4.2.2, "Setting Up a Database Connection."

To deploy your application to the Integrated WebLogic Server:

  1. Open your application in JDeveloper.

  2. From the Run menu, select Start Server Instance (IntegratedWebLogicServer) to start the server instance.

  3. From the Application menu, select Deploy, then select the default deployment profile, which is displayed in the format application name_application1 (Figure 7-3)

    Figure 7-3 Deploy Option on the Application Menu

    Description of Figure 7-3 follows
    Description of "Figure 7-3 Deploy Option on the Application Menu"

  4. In the Deploy dialog, ensure Deploy to Application Server is selected, then click Next.

  5. Select IntegratedWebLogicServer, and click Next.

  6. On the Weblogic Options screen, to accept default selections click Next.

  7. On the Summary screen, verify the deployment details, and click Finish.

  8. In the Deployment Configuration dialog, click Deploy.

    The Deployment Configuration dialog allows you to choose the target metadata repository or shared metadata repositories. The file system MDS repository, pre-created by JDeveloper, displays in the Repository Name field (Figure 7-4).

    Figure 7-4 Deployment Configuration Dialog

    Description of Figure 7-4 follows
    Description of "Figure 7-4 Deployment Configuration Dialog"

    Note that when you try to redeploy this application, the Application > Deploy menu provides the option to select the previous deployment target for your application, as shown in Figure 7-5. This is useful to skip the Deploy dialog screens and directly go to the Deployment Configuration dialog for redeploying to the previous target.

    Figure 7-5 Application Menu Showing Deploy Options

    Description of Figure 7-5 follows
    Description of "Figure 7-5 Application Menu Showing Deploy Options"

7.3 Deploying a Portal Framework Application to a WebLogic Managed Server

When you are ready to test your Portal Framework application using an external test or staging site, you can deploy your applications directly from JDeveloper to an Oracle WebLogic Managed Server.

For information about deploying Portal Framework applications using Fusion Middleware Control, Oracle WebLogic Administration Console, and WLST commands, see the "Deploying Portal Framework Applications" chapter in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

This section includes the following subsections:

7.3.1 Deployment Roadmap

The flow chart and table in this section provide an overview of the prerequisites and tasks required to deploy a Portal Framework application to an Oracle WebLogic Managed Server. Figure 7-6 shows the steps to deploy a Portal Framework application, and the roles that will carry them out.

Figure 7-6 Deploying a Framework Application to a Managed Server

Description of Figure 7-6 follows Step 1 - Package the application Step 1a - Select the data source type Package application security data Create deployment profiles Prepare the target environment Create and provision the Managed Server Create and register the MDS repository Configure the target environment Create the server connection Deploy the application to the Managed Server from JDeveloper
Description of "Figure 7-6 Deploying a Framework Application to a Managed Server"

Table 7-1 shows the tasks, sub-tasks and who will need to carry them out to deploy a Portal Framework application from JDeveloper.

Table 7-1 Deploying a Framework Application to a Managed Server

Actor Task Sub-task Notes

Developer

1. Package the Application

1.a Select the data source type (package database connections)

You can use either a global data source or an application-level data source.

If using a global data source, then you need to create the data source in the WLS Administration Console before deploying.

If using an application-level data source, then you may need to add credential mappings using the WLS Administration Console after deploying (see the note below).

Note: There are two options for deploying from JDeveloper.

You can deploy directly to the Managed Server, or you can deploy to an EAR file and then deploy the EAR file using either Fusion Middleware Control, WLST or the WLS Admin Console.

If you deploy directly from JDeveloper, the credential mapping step is not required as JDeveloper automatically handles the credential mapping. However, if you deploy the EAR file outside of JDeveloper, then this step is required.
   

1.b Package application security data

This sub-task consists of packaging the credentials, identity data, and application policies.
   

1.c Create deployment profiles

This sub-task consists of creating the WAR and EAR files.

Out-of-the-box, there are default deployment profiles available. However, you may want to create your own deployment profile to specify the context root and application name as per your requirements.

Administrator

2. Prepare the Target Environment

2.a Create and provision the Managed Server

  
   

2.b Create and register the MDS repository

  
   

2.c Configure the target environment

  
   

2.d Create the server connection

  

Developer

3. Deploy the Application to a Managed Server from JDeveloper

  

The final step is to deploy the application to the Managed Server from JDeveloper.

7.3.2 Packaging a Framework Application

When you deploy Portal Framework applications, you may also need to migrate your database connections and the related security for connecting to the databases. You will also need to create a set of project-level and application-level deployment profiles that indicate how a Portal Framework application and its associated files should be packaged so that the application can be deployed to an Oracle WebLogic Managed Server.

This section includes the following:

7.3.2.1 Packaging Database Connections and Application Security

When you deploy Portal Framework applications, you'll also need to package your database connections and the related security for connecting to the databases. This section describes how to package a Portal Framework application that uses one of the two database connection types: JDBC data source and JDBC URL. This section also describes security migration for applications that use database connections that specify passwords, or external applications that specify shared or public credentials.

Based on the policy defined by your administrator (if, for example, your administrator does not allow any application-level data sources), you may need to migrate the database connections and respective credentials to the target server. The packaging options described below allow you to choose how the database connections should be treated.

This section includes the following sub-sections:

7.3.2.1.1 Packaging the Database Connections

If your Portal Framework 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 check box 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 prior to or after deploying the application to a Managed Server in production mode using the default WebCenter Portal and Activities schemas. For more information about creating global data sources, see the "Creating a JDBC Data Source" section in Oracle Fusion Middleware Configuring and Managing JDBC Data Sources 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 WebLogic Server. That is, when the Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment check box is selected in the Application Properties dialog, as shown in Figure 7-7.

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

    Description of Figure 7-7 follows
    Description of "Figure 7-7 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 "Creating a JDBC Data Source" section in Oracle Fusion Middleware Configuring and Managing JDBC Data Sources 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.
7.3.2.1.2 Packaging Application Security Data

The following is applicable only 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

If you do not intend to migrate credentials, then deselect the Credentials check box in the Security Deployment Options section in the Application Properties dialog (see Figure 7-8).

Figure 7-8 Security Deployment Options

Description of Figure 7-8 follows
Description of "Figure 7-8 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 Portal Framework application to a Managed Server running 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 security-related sections in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

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

  • When you deploy a Portal Framework 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 7-8, in the Security Deployment Options section, the Users and Groups check box 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 identity 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 check box 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 check box 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.

7.3.2.2 Creating Deployment Profiles

Deploying your application to a Managed Server that resides outside JDeveloper using Fusion Middleware Control or the WLS Administration Console can only be done using a deployment profile, or Enterprise Archive (EAR) file. The EAR file packages (or archives) a Portal Framework application and its associated files so that the application can be deployed to an Oracle WebLogic Managed Server (this is typically done by a system administrator when the target is a production server).

Note:

You can deploy Oracle ADF applications, such as Portal Framework applications, only as EAR files.

The EAR file contains application artifacts such as, adf-config.xml, connections.xml, weblogic-application.xml, jazn-data.xml, metadata archive (MAR) files, and all project-related WAR files. For Portal Framework applications containing MDS metadata or portlets, a metadata archive file (with the extension .MAR) is automatically generated and included in the EAR file. This file contains all MDS metadata and portlet customization data.

For Portal Framework applications, both the WAR (project-level) and EAR-level deployment profiles are created for you as you build your application. These are named:

<application name>_webapp1
<application name>_application1

respectively, where <application name> is the name given to the application at creation time.

If your application, however, was not created using the WebCenter Portal Framework Application template, then you may need to create a deployment profile file for your application. You may also want to create your own EAR file if you want to give it a specific name or change what's included in the EAR file through the Application Assembly section. For information about creating an EAR deployment profile for an application, see the "Deploying Fusion Web Applications" chapter in Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

To create an EAR file:

  1. Open your application in JDeveloper.

  2. From the Application menu, choose Deploy, then select the name of the deployment profile. An EAR-level deployment profile is available out of the box, named application name_application1.

  3. In the Deploy dialog, on the Deployment Action screen, select Deploy to EAR, then click Next.

  4. On the Summary screen, verify the deployment details, and click Finish.

    This creates the EAR file in the deploy folder located in JDEV_HOME\mywork\application_name\deploy\, as shown in Figure 7-9.

    Figure 7-9 EAR Status in Deployment - Log

    Description of Figure 7-9 follows
    Description of "Figure 7-9 EAR Status in Deployment - Log"

7.3.3 Preparing the Target Environment for Deployment

This section describes how to create and provision a WebLogic Managed Server instance prior to deploying your Portal Framework application.

This section includes the following sub-sections:

7.3.3.1 Creating and Provisioning an Oracle WebLogic Managed Server Instance

Before deploying a Portal Framework application, you must create a WebLogic Managed Server based on the "Oracle WebCenter Custom Portal" template that contains all the required shared libraries and an MDS Repository. For instructions on how to create a new managed server, see the "Extending an Existing Domain" section in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.

Note:

Oracle does not recommend deploying Portal Framework applications to any of the pre-configured Managed Servers created during Oracle WebCenter Portal installation, or to a domain Administration Server.

7.3.3.2 Creating and Registering the Metadata Service Repository

After creating and provisioning the WebLogic Managed Server instance, you must create and register a Metadata Service Repository (MDS) schema for the application on the WebLogic Domain's Administration Server instance, as described in the "Creating and Registering the Metadata Service Repository" section in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

7.3.3.3 Configuring the Target Environment

After creating the Managed Server and creating and registering the MDS repository, continue by configuring the data sources, and the connections to the Identity Store, and the Policy and Credential Store. For information on configuring data sources, see the "Creating a JDBC Data Source" section in Oracle Fusion Middleware Configuring and Managing JDBC Data Sources for Oracle WebLogic Server. Note that when setting up the data source, you must provide a password or the connection may not be created when the application is deployed.

7.3.3.4 Creating a WebLogic Managed Server Connection

Before you can deploy your applications using JDeveloper to an Oracle WebLogic Managed Server instance that resides outside JDeveloper, you must create a connection to the Managed Server instance where you will deploy the application. Before you create a connection to an Oracle WebLogic Managed Server instance, ensure that the target Managed Server instance is up and running, and has the required libraries.

To create a connection to an Oracle WebLogic Managed Server:

  1. In JDeveloper, from the File menu, select New.

  2. In the New Gallery, expand General, select Connections, and then Application Server Connection.

  3. Click OK.

  4. In the Create Application Server Connection wizard, for Step 1, enter a name for the new connection (for example, WC_CustomPortal), and then click Next.

  5. At Step 2, specify the user name and password for authentication, and then click Next.

  6. At Step 3, enter the host name of the WebLogic Managed Server (for example, webcenter.myserver.example.com) and the port number (for example, 7888).

  7. In the Weblogic Domain field, specify the name of the domain in which the WebLogic Managed Server instance is created (for example, wc_domain), and then click Next.

  8. At Step 4, click Test Connection.

    If the test is successful, you now have a connection to the target WebLogic Managed Server.

  9. Click Finish.

7.3.4 Deploying a Portal Framework Application to a Managed Server

You can deploy a Portal Framework application to a Managed Server using either local application or global data sources. Local application data sources can only be accessed by the deployed application. However, it's an easy way to deploy in that it needs no other data source configuration in order to work if deployed directly from JDeveloper.

Global data sources benefit from being able to be shared by other applications on the server where database connection configuration updates can be more easily maintained and picked up by all users of the global data source. For more information about data sources, see the "Choosing the Data Source" section in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

This section contains the following subsections:

7.3.4.1 Deploying to a Managed Server Using Local Data Sources

When you deploy to a Managed Server, the application EAR file is generated. The EAR file packages the metadata archive (MAR file), which includes the metadata content to be deployed to an MDS repository. Additionally, the adf-config.xml file is reconfigured with a modified mds-config for the target deployment environment. Application-wide features, security, caching, and change persistence remain unchanged. Properties for other Oracle components, if any, are also configured in this file. Similarly, JSF and JSTL shared libraries are added in the weblogic.xml file during packaging.

To deploy a Portal Framework application to a Managed Server using local data sources:

  1. In JDeveloper, in the Application Navigator, open the application to be deployed.

  2. Create a local data source if your application contains task flows that use the WebCenter schema. If your application uses Analytics task flows, create a separate local data source for the Activities schema. For information, see Section 4.2.2, "Setting Up a Database Connection."

  3. From the Application menu, select Application Properties.

    The Application Properties dialog displays (Figure 7-10).

    Figure 7-10 Application Properties Dialog

    Description of Figure 7-10 follows
    Description of "Figure 7-10 Application Properties Dialog"

  4. Choose Deployment from the navigation panel to display the Deployment options.

  5. Make sure that the Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment check box is selected and click OK.

  6. From the Application menu, select Deploy and then the application name.

    The Deployment Action dialog displays (Figure 7-11).

    Figure 7-11 Selecting the Deployment Action

    Description of Figure 7-11 follows
    Description of "Figure 7-11 Selecting the Deployment Action "

  7. Select Deploy to Application Server and click Next.

  8. Select the connection name of the Managed Server (for example, WC_CustomPortal), and click Next (Figure 7-12).

    If the server to which you want to deploy is not listed, click the Add icon (+) and complete the connection details to add the server to the list.

    Figure 7-12 Select Server Dialog

    Description of Figure 7-12 follows
    Description of "Figure 7-12 Select Server Dialog"

  9. Select Deploy to selected instance in the domain, select the managed server from the list (for example, WC_CustomPortal), and click Next (Figure 7-13).

    In most cases you will want to deselect Deploy to all instances in the domain and select the specific servers and clusters to deploy to. Refer to the online help for more information about using these options.

    Figure 7-13 Deployment WebLogic Options dialog

    Description of Figure 7-13 follows
    Description of "Figure 7-13 Deployment WebLogic Options dialog"

  10. On the Deployment Summary dialog, verify the deployment details. Click Finish to start the deployment.

    The Deployment Configuration dialog displays (Figure 7-14).

  11. Select the Repository Name (for example, mds-CustomPortalDS), enter a Partition Name (if the partition doesn't already exist then it will be created during deployment), and click Deploy.

    Figure 7-14 Deployment Configuration Dialog

    Description of Figure 7-14 follows
    Description of "Figure 7-14 Deployment Configuration Dialog"

  12. Continue by doing any post-deployment security or data source connection configurations that may be required as described in the "Post-Deployment Configuration" section in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

7.3.4.2 Deploying to a Managed Server Using Global Data Sources

Deploying to a Managed Server using global data sources is recommended when the application is not intended to run on a Managed Server created with the WebCenter Custom Portal template, or is intended to run against custom data sources not named WebCenterDS or ActivitiesDS.

Oracle recommends using the default data source names, but if you use non-default pre-seeded data sources, then you must name your data sources accordingly and follow the pre- or post-deployment global data source creation steps to create data sources that map to the names you have chosen. For more information, see the "Choosing the Data Source" section in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

To deploy to a Managed Server using global data sources:

  1. Open the application to be deployed in JDeveloper.

  2. Determine the JNDI names your application will be using for the data sources.

    The JNDI names will depend on whether you've created a database connection for your application in JDeveloper or are using the defaults. The following table shows the default JNDI names:

    Data Source JDeveloper JNDI Name Default JNDI Name
    WebCenterDS jdbc/WebCenterConnectionNameDS

    (where WebCenterConnectionName is the name of the WebCenter schema database connection)

    		 jdbc/webcenter/CustomPortalDS
    ActivitiesDS jdbc/ActivitiesConnectionNameDS

    (where ActivitiesConnectionName is the name of the Activities schema database connection)

    		 jdbc/activities/CustomPortalDS

  3. From the Application menu, select Application Properties.

  4. Choose Deployment from the navigation panel to display the Deployment options.

  5. Deselect the Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment check box if selected and click OK.

  6. From the Application menu, select Deploy, and then the application name.

  7. Select Deploy to Application Server and click Next (Figure 7-15).

    Figure 7-15 Choosing a Deployment Action

    Description of Figure 7-15 follows
    Description of "Figure 7-15 Choosing a Deployment Action"

  8. Select the connection name of the Managed Server (for example, WC_CustomPortal), and click Next (Figure 7-16).

    If the server to which you want to deploy is not listed, click the Add icon (+) and complete the connection details to add the application server to the list.

    Figure 7-16 Selecting a Managed Server Connection

    Description of Figure 7-16 follows
    Description of "Figure 7-16 Selecting a Managed Server Connection"

  9. Select Deploy to selected instance in the domain, select the managed server from the list (for example, WC_CustomPortal), and click Next (Figure 7-17).

    In most cases you will want to deselect Deploy to all server instances in the domain and select the specific servers and clusters to deploy to using the Server Instances dialog. Refer to the online help for more information about using these options.

    Figure 7-17 Selecting the Managed Server

    Description of Figure 7-17 follows
    Description of "Figure 7-17 Selecting the Managed Server"

  10. On the Deployment Summary dialog, verify that the deployment options are correct and click Finish to start the deployment.

    The Deployment Configuration dialog displays (Figure 7-18).

  11. Select the Repository Name (for example, mds-CustomPortalDS), enter a Partition Name (if the partition doesn't already exist then it will be created during the deployment), and click Deploy.

    Figure 7-18 Deployment Configuration Dialog

    Description of Figure 7-18 follows
    Description of "Figure 7-18 Deployment Configuration Dialog"

  12. Continue by doing any post-deployment security or data source connection configurations that may be required as described in the "Post-Deployment Configuration" section in Oracle Fusion Middleware Administering Oracle WebCenter Portal.

7.4 Transporting Customizations Between Environments

When migrating a deployed application to a new environment, post-deployment customizations made to pages, WebCenter Portal tools and services, and portlets (PDK-Java and WSRP version 2 producers) must be migrated too. Export and import utilities are available to assist with this process. For more information, see the "Managing Export, Import, Backup, and Recovery for Portal Framework Applications" chapter in Oracle Fusion Middleware Administering Oracle WebCenter Portal.