Moving from a Test to a Production Environment 21-41
– migrationFile: This element specifies the file that was generated by the
export operation.
– serverURL: The SOA server URL
– adminUserLogin
– adminUserPassword
– objectDetails: Update the login and password elements.
b.
Export Organizations, using the following command:
ant -f ant-t2p-workspace.xml -Dbea.home=BEA_HOME
-Dbpm.home=BPM_HOME -Dbpm.t2p.migration.config=ORG_MIGRATION_CONFIG_FILE
c.
Create a configuration file to export Dashboards:
?xml version=1.0 encoding=UTF-8 standalone=yes? testToProductionMigrationConfiguration
xmlns=http:xmlns.oracle.combpmt2pmigrationconfig xmlns:ns2=http:xmlns.oracle.combpmcommon override=true skip=true
sourceEndPoint serverEndPoint
serverURLt3:hostname:portserverURL adminUserLoginadmin_usernameadminUserLogin
adminUserPasswordadmin_passwordadminUserPassword realmjazn.comrealm
serverEndPoint sourceEndPoint
targetEndPoint fileEndPoint
migrationFiletmpbpm_dashboard.xmlmigrationFile fileEndPoint
targetEndPoint operationEXPORToperation
objectDASHBOARDobject objectDetails
loginusernamelogin passwordpasswordpassword
identityContextjazn.comidentityContext userApplicationData
ownerIdusernameownerId userApplicationData
objectDetails testToProductionMigrationConfiguration
In the configuration file, you must specify the values for the test environment in the following elements:
–
serverURL: The SOA server URL
–
adminUserLogin
–
adminUserPassword
–
migrationFile. Note that this element specifies the file that was generated by the export operation.
–
objectDetails: Update the login and password elements.
–
userApplicationData: Update the ownerID element.
21-42 Oracle Fusion Middleware Administrators Guide
d.
Export Dashboards, using the following command:
ant -f ant-t2p-workspace.xml -Dbea.home=BEA_HOME
-Dbpm.home=BPM_HOME -Dbpm.t2p.migration.config=Dashboard_MIGRATION_CONFIG_FILE
3.
Import Organization and Dashboards:
a.
Create a configuration file to import Organizations. You pass that file to the ant command.
The following shows a sample configuration file that imports Organizations:
?xml version=1.0 encoding=UTF-8 standalone=yes? testToProductionMigrationConfiguration
xmlns=http:xmlns.oracle.combpmt2pmigrationconfig xmlns:ns2=http:xmlns.oracle.combpmcommon override=true skip=true
sourceEndPoint fileEndPoint
migrationFiletmpbpm_organization.xmlmigrationFile fileEndPoint
sourceEndPoint targetEndPoint
serverEndPoint serverURLt3:hostname:portserverURL
adminUserLoginadmin_usernameadminUserLogin adminUserPasswordadmin_passwordadminUserPassword
realmjazn.comrealm serverEndPoint
targetEndPoint operationIMPORToperation
objectORGANIZATIONobject objectDetails
loginusernamelogin passwordpasswordpassword
identityContextjazn.comidentityContext organization
objectDetails testToProductionMigrationConfiguration
In the configuration file, you must update the following elements with the values for the production environment:
– migrationFile: This element specifies the file that was generated by the
export operation.
– serverURL: The SOA server URL
– adminUserLogin
– adminUserPassword
– objectDetails: Update the login and password elements.
b.
Import Organizations, using the following command:
ant -f ant-t2p-workspace.xml -Dbea.home=BEA_HOME
-Dbpm.home=BPM_HOME -Dbpm.t2p.migration.config=ORG_MIGRATION_CONFIG_FILE
c.
Create a configuration file to import Dashboards. The format is the same as for Organizations, except that you substitute the following lines:
Moving from a Test to a Production Environment 21-43
sourceEndPoint fileEndPoint
migrationFiletmpbpm_dashboard.xmlmigrationFile fileEndPoint
sourceEndPoint targetEndPoint
serverEndPoint serverURLt3:hostname:portserverURL
adminUserLoginadmin_usernameadminUserLogin adminUserPasswordadmin_passwordadminUserPassword
realmjazn.comrealm serverEndPoint
targetEndPoint operationIMPORToperation
objectDASHBOARDobject objectDetails
loginusernamelogin passwordpasswordpassword
identityContextjazn.comidentityContext userApplicationData
ownerIdusernameownerId userApplicationData
objectDetails testToProductionMigrationConfiguration
In the configuration file, you must update the following elements with the values for the production environment:
– serverURL: The SOA server URL
– adminUserLogin
– adminUserPassword
– migrationFile. Note that this element specifies the file that was generated
by the export operation.
– objectDetails: Update the login and password elements.
– userApplicationData: Update the ownerID element.
d.
Import Dashboards, using the following command:
ant -f ant-t2p-workspace.xml -Dbea.home=BEA_HOME
-Dbpm.home=BPM_HOME -Dbpm.t2p.migration.config=Dashboard_MIGRATION_CONFIG_FILE
Task 7 Move UMS-Related Details to the New Production Environment
To move UMS details to the new production environment:
1.
Configure the required UMS drivers in the production environment.
■
Use Fusion Middleware Control to configure the User Messaging Service drivers with production driver information.
■
Use the WLST command deployUserMessagingDriver to deploy multiple drivers similar to the test environment.
Note: To see different options for deploying additional drivers,
execute helpdeployUserMessagingDriver at the wls:offline prompt.
21-44 Oracle Fusion Middleware Administrators Guide
■
Re-create any custom-created business terms in the production environment. This step is essential in order to use the same set of User Preferences filter
settings in the production environment, and to ensure that filters built with custom business terms are functional.
■
Restart the production environment to apply the changes.
2.
Move the User Messaging preferences from the test environment to the production environment:
a.
In the test environment, run the following WLST command to download the User Messaging preferences from the backend database to the specified .xml
file:
wls:offline manageUserMessagingPrefsoperation=download, filename=tmpuserprefs-dump.xml, url=t3:localhost:8001,
username=username, password=password
In this example, 8001 is the Managed Server port on which UMS is running. Replace it with the appropriate value.
b.
Copy the tmpuserprefs-dump.xml file to the production environment.
c.
In the production environment, run the following WLST command to upload the User Messaging preferences from file to the backend database:
wls:offline manageUserMessagingPrefsoperation=upload, filename=tmpuserprefs-dump.xml, url=t3:localhost:8001,
username=username, password=password
In this example, 8001 is the Managed Server port on which UMS is running. Replace it with the appropriate value.
d.
Observe the message displayed for successful upload. Exit the WLST command line tool.
e.
Test the UMS drivers for send and receive capabilities for supported drivers.
f.
Test the successful upload of user messaging preferences by invoking the http:host:portsdpmessaginguserprefs-ui URL. Log in as the
desired user and validate that the messaging channels and filters are identical to those in the test environment. Alternatively, send and receive messages that
are expected to be delivered based on the User Messaging preferences.
Task 8 Enable SSL and Create Custom Keystores
During the pasteConfig operation, SSL is disabled. In addition, custom keystores are not created in the production environment. Take the following steps:
1.
Enable SSL, as described in Section 6.5
.
2.
Create custom keystores, as described in Section 8.3.3.1
.
Note: To see different options for performing download and upload
operations, execute helpmanageUserMessagingPrefs at the wls:offline prompt. Please note that user devices provisioned
in the LDAP store are dynamic. The assumption is that both the test and production environments point to the same LDAP store or you
reconfigured it to use the same set of information.
Moving from a Test to a Production Environment 21-45
21.4.2.2 Moving Oracle SOA Suite to an Existing Production Environment
In this scenario, you have a working production environment and want to test changes in your applications or configuration before rolling those changes into the production
environment. In the test environment, you have the same environment as described in Section 21.4.2
. To move Oracle SOA Suite to an existing production environment:
■
Task 1, Move Oracle SOA Suite Changes
■
Task 2, Move Oracle B2B Changes
■
Task 3, Move Oracle Business Process Management Changes
■
Task 4, Move Oracle Business Activity Monitoring Data
■
Task 5, Move Oracle User Messaging Service Data
Task 1 Move Oracle SOA Suite Changes Move any changes that you have made to Oracle SOA Suite:
1.
If you have added users and groups in the test environment or modified security policies or credentials, follow the steps in
Section 21.3.6 to move them to the
production environment.
2.
If you have modified EJBs or Plain Old Java Objects POJOs in the test environment that support the composite references, move them to the production
environment:
a.
To deploy EJB Modules, see Deploy EJB Modules in the Oracle WebLogic Server Administration Console Online Help.
b.
To deploy Enterprise Applications, see Working with Enterprise Applications in the Oracle WebLogic Server Administration Console Online
Help.
c.
If you have made any changes to Human Workflow in the test environment, move them to the production environment. See Moving Human Workflow
Data from a Test to a Production Environment in the Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle Business Process
Management Suite.
3.
If you have modified any information in the configuration plans, copy those changes to the production environment. For more information about configuration
plans, see Moving SOA Composite Applications to and from Development, Test, and Production Environments in the Oracle Fusion Middleware Developers Guide
for Oracle SOA Suite.
Task 2 Move Oracle B2B Changes
If you have made any changes to Oracle B2B in the test environment, move those changes to the production environment.
Note that if you export selective agreements using the tpanames parameter, you must import each zip file individually.
1.
Move Oracle B2B system configuration parameters by using the Oracle B2B interface to configure the properties. See Configuring System Parameters in the
Oracle Fusion Middleware Users Guide for Oracle B2B for details.
2.
Move other configuration properties by using the B2B command line, as described in Setting Properties of b2b-config in the Oracle Fusion Middleware Users Guide for
Oracle B2B.
21-46 Oracle Fusion Middleware Administrators Guide
3.
Move the B2B agreements and trading partners to the production environment:
a.
Export the data from the test environment. The following example exports multiple deployed and active agreements:
ant -f ant-b2b-util.xml b2bexport -Dtpanames=Acme_GC_Agreement1, GC_Acme_Agreement1 -Dactive=true -Dexportfile=tmpexport.zip
b.
Import the data to the production environment. The following example imports the elements in the file tmpexport.zip:
ant -f ant-b2b-util.xml b2bimport -Dlocalfile=true -Dexportfile=tmpexport.zip
For more information about these commands, see B2B Command Line Tools in the Oracle Fusion Middleware Users Guide for Oracle B2B.
4.
Configure B2B agreement external endpoints with production locations and credentials, as described in Configuring Channels in the Oracle Fusion Middleware
Users Guide for Oracle B2B.
5.
If your Oracle B2B environment has been configured with Java callouts, manually move the callout library. See Managing Callouts in the Oracle Fusion Middleware
Users Guide for Oracle B2B.
6.
Deploy the B2B agreements, as described in Deploying an Agreement in the Oracle Fusion Middleware Users Guide for Oracle B2B.
Task 3 Move Oracle Business Process Management Changes If you have made any changes to Oracle Business Process Management in the test
environment, move them to the production environment.
To move Oracle Business Process Management to the existing production environment, you move Oracle Business Process Management user metadata, such as
organizations and dashboards, from the test environment to the production environment, using the migration tool, as described in
Task 6, Move Oracle Business Process Management to the New Production Environment
in Section 21.4.2.1
.
Task 4 Move Oracle Business Activity Monitoring Data Move any Oracle BAM data that has changed:
1.
Export Oracle BAM artifacts from the test environment using the icommand, which is located in the following directory:
UNIX ORACLE_HOME\bam\bin\icommand.sh Windows ORACLE_HOME\bam\bin\icommand.bat
For example:
icommand -cmd export -type dataobject -all 1 -PERMISSIONS 1 -OWNER 1 -file dataobject.xml
icommand -cmd export -type folder -all 1 -PERMISSIONS 1 -OWNER 1 -file folder.xml
icommand -cmd export -type report -all 1 -file reports.xml icommand -cmd export -type rule -all 1 -file rules.xml
icommand -cmd export -type ems -all 1 -file ems.xml icommand -cmd export -type eds -all 1 -file eds.xml
In addition to exporting all artifacts of a particular type, you can export individual artifacts. For more information about using the icommand to export artifacts, see
Export in the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.
Moving from a Test to a Production Environment 21-47
2.
Export the BAM users from the LDAP identity store on the test environment, using the ldapsearch command. This produces an ldif file that you later import
into the LDAP identity store in the production environment. The ldapsearch command is located in the ORACLE_HOMEbin directory of the Identity
Management components. For example:
ORACLE_HOMEbinldapsearch -h test_oid_host -p test_oid_port -D cn=orcladmin
-w test_orcladmin_passwd -b cn=Users,dc=us
3.
Import BAM data and artifacts into the production environment:
a.
Deactivate the rules that are set up by default, using Oracle BAM Architect. See To change the activity status of an alert rule in the Oracle Fusion
Middleware Developers Guide for Oracle SOA Suite.
b.
If you have not already done so, make the LDAP security provider the default provider, as described in Step 2 in
Task 5, Move Oracle Business Activity Monitoring Data to the New Production Environment
.
c.
Import the BAM users from the ldif file that you exported from the test environment into the LDAP provider, such as Oracle Internet Directory, on
the production environment. ORACLE_HOME is the Oracle home for Identity Management.
ORACLE_HOMEbinldapadd -h production_oid_host -p production_oid_port -D cn=orcladmin -w production_orcladmin_passwd -vf ldif_filename
d.
Move the BAM application policy and roles to LDAP using Fusion Middleware Control:
– From the navigation pane, right-click the domain that contains Oracle
BAM and choose Security, then Security Provider Configuration. –
Follow the steps in Reassociating Domain Stores with Fusion Middleware Control in the Oracle Fusion Middleware Application Security Guide.
e.
Import the Oracle BAM artifacts using the icommand, which is located in the following directory:
UNIX ORACLE_HOME\bam\bin\icommand.sh Windows ORACLE_HOME\bam\bin\icommand.bat
For example:
icommand -cmd import -file dataobject.xml -UPDATELAYOUT 1 -MODE UPDATE -CONTINUEONERROR
icommand -cmd import -file folder.xml -MODE OVERWRITE -PRESERVEOWNER icommand -cmd import -file reports.xml -MODE OVERWRITE -PRESERVEOWNER
icommand -cmd import -file ems.xml -MODE OVERWRITE icommand -cmd import -file eds.xml -MODE OVERWRITE
4.
Start the BAM server.
Task 5 Move Oracle User Messaging Service Data
Move Oracle User Messaging Service data:
1.
Configure the required UMS drivers in the production environment.
21-48 Oracle Fusion Middleware Administrators Guide
■
Use Fusion Middleware Control to configure the User Messaging Service drivers with production driver information.
■
Use the WLST command deployUserMessagingDriver to deploy multiple drivers similar to the test environment.
■
Re-create any custom-created business terms in the production environment. This step is essential in order to use the same set of User Preferences filter
settings in the production environment, and to ensure that filters built with custom business terms are functional.
■
Restart the production environment to apply the changes.
2.
Move the User Messaging preferences from the test environment to the production environment. Filters cannot be updated or appended to an existing filter set. You
must do one of the following:
■
Delete the entire filter set and upload a new set if there are changes made to the filter set in the test environment.
■
Newly created or modified user devices and filters in the test environment must be created or modified using the following URL in the production
environment:
http:host:portsdpmessaginguserprefs-ui
3.
Test the UMS drivers for send and receive capabilities for supported drivers.
4.
Test the successful upload of user messaging preferences by invoking the http:host:portsdpmessaginguserprefs-ui URL. Log in as the
desired user and validate that the messaging channels and filters are identical to those in the test environment. Alternatively, send and receive messages that are
expected to be delivered based on the User Messaging preferences.
21.4.3 Moving Oracle WebCenter to a Production Environment
The following topics describe how to move Oracle WebCenter from a test environment to a production environment:
■
Moving Oracle WebCenter to a New Production Environment
■
Moving Oracle WebCenter to an Existing Production Environment In both scenarios, you have performed the following in a test environment:
■
Installed Oracle WebLogic Server.
■
Installed Oracle WebCenter.
Note: While moving Oracle User Messaging Service to an existing
production environment configured against an LDAP Store, only use the Userprefs-UI option to change User Preferences. Using the WLST
command manageUserMessagingPrefs is not recommended as it may not correctly migrate identity-store backed device preferences
that have been removed from the test instance.
Note: To see different options for deploying additional drivers,
execute helpdeployUserMessagingDriver at the wls:offline prompt.
Moving from a Test to a Production Environment 21-49
■
Created the required schemas in the test database using RCU.
■
Installed and configured Oracle SOA Suite.
■
Configured Oracle WebCenter using the Configuration Wizard. You created a domain and Managed Servers and configured Oracle WebCenter Spaces, Oracle
WebCenter Portlets, Oracle Discussions, Oracle WebCenter Wiki and Blog Server.
■
Installed and configured Oracle Universal Content Management.
■
Installed Identity Management components, such as Oracle Internet Directory, Oracle Identity Federation, and Oracle Access Manager.
■
Configured Group Spaces.
■
Configured Oracle WebCenter to use LDAP and created some users and groups in the embedded LDAP or an LDAP store.
■
Created the required Oracle Platform Security Services policies in the policy store.
■
Created the required user credentials in the credential store.
■
Created and deployed custom WebCenter applications.
■
Created instance data in the WebCenter Spaces application, including creating a group space based on a Community of Interest template, and provisioned services.
In addition, created some roles and assigned new members to the roles.
21.4.3.1 Moving Oracle WebCenter to a New Production Environment
To move Oracle WebCenter to a new production environment, perform the following tasks:
■
Task 1, Move the Database, Middleware Home, and Perform the Initial Configuration
■
Task 2, Export WebCenter Spaces Applications and Required Data from the Test Environment
■
Task 3, Export Custom WebCenter Framework Applications from the Test Environment
■
Task 4, Import WebCenter Spaces Data and Application to the Production Environment
■
Task 5, Import Custom WebCenter Framework Applications to the Production Environment
■
Task 6, Enable SSL and Create Custom Keystores
Task 1 Move the Database, Middleware Home, and Perform the Initial Configuration
To move the database, Middleware home, and perform the initial configuration:
1.
Move or create the database, as described in Section 21.3.2
.
2.
Move Identity Management components, as described in Section 21.4.1
.
3.
Move the Middleware home and binary files, as described in Section 21.3.3
.
4.
Because Oracle Universal Content Management requires a Web server, move Oracle HTTP Server, as described in
Section 21.4.6.1.1 .
5.
Move the configuration, as described in Section 21.3.4
.
21-50 Oracle Fusion Middleware Administrators Guide
Note that when you move the configuration, the pasteConfig script copies the configuration of the domain, including the domain, Administration Server, and
Managed Servers. In addition, that step:
■
Associates WebCenter Spaces with an external identity store.
■
For WebCenter Spaces and WebCenter Framework, creates authenticators for Identity Management in Oracle WebLogic Server.
■
For WebCenter Spaces and WebCenter Framework, reassociates the policy and credential store.
■
For WebCenter Spaces, moves application producer data.
■
For WebCenter Spaces, moves portlet customization, personalizations, and metadata from the test environment to the production environment.
■
Moves the data for the policy and credential store from the test environment to the production environment.
■
Moves the custom Oracle WebCenter Framework application metadata from the test environment to the production environment.
■
Starts the Administration Server.
6.
Configure users, groups, the security policies, and the credential store, as described in
Section 21.3.6 .
Task 2 Export WebCenter Spaces Applications and Required Data from the Test Environment
Export WebCenter Spaces applications and data required for the applications from the test environment:
1.
If necessary, export the required data for WebCenter Spaces applications, including the Content Server and the Discussion Forum.
a.
Export Oracle Content Server, executing the following commands ORACLE_ HOME is the Oracle home for the Oracle Database:
ORACLE_HOMEbinsqlplus syspassword as sysdba create or replace directory directory as path;
grant read,write on DIRECTORY directory to user; exit;
ORACLE_HOMEbinexpdp syspasswordconnect_id as sysdba schemas=prefix_OCSERVER directory=directory dumpfile=filename
b.
Export the Discussion Forum using the Oracle Database export utility ORACLE_HOME is the Oracle home for the Oracle Database:
ORACLE_HOMEbinexport syspasswordconnect_id as sysdba OWNER=prefix_DISCUSSIONS FILE=tmpdf.dmp statistics=none
Refer to Exporting and Importing WebCenter Spaces Applications for Data Migration in the Oracle Fusion Middleware Administrators Guide for Oracle
WebCenter for more information.
See Also: The chapters on Oracle Data Pump in the Oracle Database
Utilities, which is available at:
http:www.oracle.comtechnetworkdatabaseenterprise-editio ndocumentationindex.html
Moving from a Test to a Production Environment 21-51
2.
Move Oracle SOA Suite from the test environment to the production environment, as described in
Section 21.4.2 .
3.
Export Portlet customization, personalizations, and metadata from the test environment, using the following command:
exportPortletClientMetadataappName=app_name, fileName=filename, exportPersonalizations=1
For detailed syntax, see exportPortletClientMetadata in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
4.
Export the WebCenter Spaces application by using the following WLST commands:
connectusername,password,t3:hostname:port exportWebCenterApplicationappName,fileName,
exportCustomizations=true, exportSecurity=true, exportData=true
Refer to Exporting and Importing Custom WebCenter Applications for Data Migration in the Oracle Fusion Middleware Administrators Guide for Oracle
WebCenter for details.
Task 3 Export Custom WebCenter Framework Applications from the Test Environment
To export custom WebCenter Framework applications from the test environment:
1.
Export Portlet customizations, personalizations, and metadata from the test environment, using the following command:
exportPortletClientMetadataappName=app_name,fileName=filename, exportPersonalizations=1
For detailed syntax, see exportPortletClientMetadata in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
2.
Export the WebCenter Framework application data from the test database, using the following commands ORACLE_HOME is the Oracle home for the Oracle
Database:
ORACLE_HOMEbinsqlplus syspassword as sysdba create or replace directory directory as path;
grant read,write on DIRECTORY directory to user; exit;
ORACLE_HOMEbinexpdp syspasswordconnect_id as sysdba schemas=prefix_WEBCENTER directory=directory dumpfile=filename
For information about the CREATE OR REPLACE DIRECTORY command, see CREATE DIRECTORY in the Oracle Database SQL Language Reference.
For information about the expdp command, refer to the chapters on Oracle Data Pump in Oracle Database Utilities, which is available at:
http:www.oracle.comtechnetworkdatabaseenterprise-editiondocum entationindex.html
3.
Export Oracle Content Server, executing the following commands ORACLE_ HOME is the Oracle home for the Oracle Database:
ORACLE_HOMEbinsqlplus syspassword as sysdba create or replace directory directory as path;
21-52 Oracle Fusion Middleware Administrators Guide
grant read,write on DIRECTORY directory to user; exit;
ORACLE_HOMEbinexpdp syspasswordconnect_id as sysdba schemas=prefix_OCSERVER directory=directory dumpfile=filename
4.
Export the Discussion Forum using the Oracle Database export utility ORACLE_ HOME is the Oracle home for the Oracle Database:
ORACLE_HOMEbinexport syspasswordconnect_id as sysdba OWNER=prefix_DISCUSSIONS FILE=tmpdf.dmp statistics=none
Task 4 Import WebCenter Spaces Data and Application to the Production Environment
To import the WebCenter Spaces data and application to the production environment:
1.
Import Content Server:
a.
Import the Oracle Content Server data to the production database, using the file you exported in
Task 2 . Execute the following commands ORACLE_
HOME is the Oracle home for the Oracle Database:
ORACLE_HOMEbinsqlplus syspassword as sysdba create or replace directory directory as path;
grant read,write on DIRECTORY directory to user; exit;
ORACLE_HOMEbinimpdp syspasswordconnect_id as sysdba remap_schema=testprefix_OCSERVER:prod_prefix_OCSERVER
DIRECTORY=directory dumpfile=filename TABLE_EXISTS_ACTION=REPLACE
b.
Copy the following directories from the test environment to the production environment. You can use tar to compress the files from the test environment
and restore them on the production environment:
WebCenter_ORACLE_HOMEucmvault WebCenter_ORACLE_HOMEucmweblayout
2.
Import the Discussion Forum:
a.
Connect to the production database using SQLPlus. ORACLE_HOME is the Oracle home for the production database.
ORACLE_HOMEbinsqlplus syspassword as sysdba
b.
Drop the target user:
drop user prefix_DISCUSSIONS cascade;
c.
Create the target user:
create user prefix_DISCUSSIONS identified by password default tablespace prefix_IAS_DISCUSSIONS
temporary tablespace prefix_IAS_TEMP;
See Also: The chapters on Oracle Data Pump in the Oracle Database
Utilities, which is available at:
http:www.oracle.comtechnetworkdatabaseenterprise-editio ndocumentationindex.html
Moving from a Test to a Production Environment 21-53
d.
Grant connect and resource privileges to the user and exit from SQLPlus:
grant connect,resource to prefix_DISCUSSIONS; exit;
e.
Import the Discussion Forum data into the production database. You import the file that you exported from the test database in
Task 2 . ORACLE_HOME is
the Oracle home for the production database.
ORACLE_HOMEbinimp syspasswordconnect_id as sysdba FROMUSER=testprefix_DISCUSSIONS TOUSER=prod_prefix_DISCUSSIONS
FILE=filename statistics=none
3.
Import the WebCenter Spaces application by using the following WLST commands:
connectusername,password,t3:hostname:port importWebCenterApplicationappName=appName, fileName=fileName
Refer to Exporting and Importing Custom WebCenter Applications for Data Migration in the Oracle Fusion Middleware Administrators Guide for Oracle
WebCenter for details.
4.
Import Portlet customization, personalizations, and metadata to the production environment, using the following command:
importPortletClientMetadataappName=app_name, fileName=filename
For detailed syntax, see importPortletClientMetadata in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
Task 5 Import Custom WebCenter Framework Applications to the Production Environment
To import custom WebCenter Framework applications to the production environment:
1.
Import Portlet customizations and metadata from file you exported in Task 3
to the production environment, using the following WLST command:
importPortletClientMetadataappName=app_name,fileName=filename
2.
Import the data from the database, using the following commands ORACLE_ HOME is the Oracle home for the Oracle Database:
ORACLE_HOMEbinsqlplus syspassword as sysdba create or replace directory directory as path;
grant read,write on DIRECTORY directory to user;
Note:
If you are using the embedded Oracle WebLogic Server LDAP identity store, see Managing Security in the Oracle Fusion Middleware
Administrators Guide for Oracle WebCenter. Although secure, the embedded LDAP identity store is not a
production-class store and should be replaced with an external LDAP-based identity store, such as Oracle Internet Directory, for
enterprise production environments.
See Also: Exporting and Importing WebCenter Portal Applications
for Data Migration in the Oracle Fusion Middleware Administrators Guide for Oracle WebCenter for more information
