Creating an On-premise WebLogic Server Environment

An on-premise environment is a local WebLogic Server /Java EE environment that is comparable to an Oracle Java Cloud Service - SaaS Extension instance. It is useful for both developing and troubleshooting applications deployed to Oracle Java Cloud Service - SaaS Extension.

Tip:

Review the topics in Preparing Applications for Oracle Java Cloud Service - SaaS Extension Deployment to verify whether your existing on-premise applications need to be updated to utilize the latest Oracle Java Cloud Service - SaaS Extension features. For example, there are Guidelines for Applications When Accessing a Local File System and Guidelines for Applications When Using Log4j Appenders.

To create an on-premise WebLogic Server environment, do the following:

  1. Install WebLogic Server 10.3.6. No other version of WebLogic Server is supported as an on-premise environment for Oracle Java Cloud Service - SaaS Extension.

  2. Create a domain as follows:

    • If the application you are deploying is not an ADF application and does not use any web services security (using OWSM), use the plain wls.jar WebLogic Server domain configuration template.

    • If the application you are deploying is using ADF or web services (by either exposing or invoking them) that must be protected through OWSM security policies, use the plain wls.jar as well as the JRF and OWSM domain configuration templates.

      Tip:

      You can apply the JRF and OWSM domain configuration templates through the WebLogic Server configuration wizard. To accomplish this, use the version of the configuration wizard packaged with Oracle JDeveloper release 11.1.1.7.1 or ADF download. To learn how to extend a WebLogic Server domain for ADF applications, see How to Create and Extend Oracle WebLogic Server Domains in Oracle Fusion Middleware Administrator's Guide for Oracle Application Development Framework.

  3. Deploy the deployment archives listed in the following table as shared libraries to the domain. Note that MW_HOME refers to the Middleware Home directory you used when you installed WebLogic Server.

    Tip:

    During deployment, you must use the exact deployment names specified in this table.

    Application Type Deployment Archive Path Deployment Name

    Uses JAX-RS 1.9 REST interfaces

    MW_HOME/wlserver_10.3/common/deployable-libraries/jersey-bundle-1.9.war

    jax-rs

    Uses JSF 2.0 for web application components

    MW_HOME/wlserver_10.3/common/deployable-libraries/jsf-2.0.war

    jsf

  4. Create a single XA enabled JDBC data source using the Oracle JDBC Thin driver connected to an on-premise Oracle Database 11g release 1 (11.1) data source. Give the data source the same name as the Database Cloud Service instance associated with your target Oracle Java Cloud Service - SaaS Extension.

    To learn more about JDBC data sources, see How to Create a JDBC Data Source for Oracle WebLogic Server in Oracle Fusion Middleware Administrator's Guide for Oracle Application Development Framework.

Moving an Application between an On-premise Environment and an Oracle Java Cloud Service - SaaS Extension Instance

To move an application (represented by a set of EAR/WAR files) between an on-premise environment and Oracle Java Cloud Service - SaaS Extension instances (or vice-versa), you must ensure that their database and Identity Management user repository content are also moved appropriately.

Moving Data from an on-premise Environment to Database Cloud Service Instances

To move database data from an on-premise environment to Database Cloud Service instances associated with Oracle Java Cloud Service - SaaS Extension instances:

  1. Ensure that your schema tables are created within the target Database Cloud Service instance. To do this you can use either the database service's SQL Workshop interface (see the Using SQL Workshop Data Upload Utility section in Using Oracle Database Cloud Service) or SQL Developer (see the Using SQL Developer for Data Loading section in Using Oracle Database Cloud Service).

    When using EclipseLink JPA, you can also have the schemas created upon application deployment by using the following snippet within your application's persistence.xml descriptor:

    <property name="eclipselink.ddl-generation" value="create-tables"/>
    
  2. Make sure that the data source name in the persistence.xml is configured to match the Database Cloud Service instance name that is associated with your Oracle Java Cloud Service - SaaS Extension instance.

  3. Import your bulk data from on-premise to the target Database Cloud Service instance by using the SQL Workshop Data Upload Utility (for instructions, see Importing Data in Using Oracle Database Cloud Service).

Moving Data from Database Cloud Service Instances Associated with Oracle Java Cloud Service - SaaS Extension Instances to On-premise Schemas

To import your bulk data from on-premise to the target Database Cloud Service instance, see Exporting Data in Using Oracle Database Cloud Service.

Moving Repository Data from On-premise User Repositories to the Identity Domain Associated with an Oracle Java Cloud Service - SaaS Extension Instance

Export data from your on-premise identity repository into a single file in CSV format (for instructions, see Managing Users and Roles in Using Oracle Database Cloud Service).