Oracle Fusion CRM_Using Sandboxes

Download Oracle Fusion CRM_Using Sandboxes

Post on 05-Jan-2016

7 views

Category:

Documents

0 download

Embed Size (px)

DESCRIPTION

Oracle Fusion CRM_Using Sandboxes

TRANSCRIPT

<ul><li><p>An Oracle White Paper </p><p>October 2012 </p><p>Customizing Oracle Fusion CRM Applications </p><p>Using Sandboxes </p></li><li><p>Safe Harbor </p><p>The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracles products remains at the sole discretion of Oracle. </p><p>About This Document </p><p>This document supplements standard product documentation, which you are encouraged to review. To find documentation, such as guides, click Help and search for topics. </p><p>The information in this document is applicable to Oracle Fusion CRM versions 11.1.3.0.0 and 11.1.4.0.0.</p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers </p><p>Executive Overview ............................................................................................. 1 </p><p>Introduction ......................................................................................................... 1 </p><p>Customizations .................................................................................................... 2 </p><p>Composers ................................................................................................................ 2 </p><p>Sandboxes .......................................................................................................... 4 </p><p>Using the Sandbox Manager ...................................................................................... 6 </p><p>Creating a Sandbox ................................................................................................................7 </p><p>Creating Multiple Sandboxes..................................................................................................8 </p><p>Activating a Sandbox ..............................................................................................................8 </p><p>Exiting a Sandbox and Returning to the Mainline ............................................................... 10 </p><p>Publishing a Sandbox .......................................................................................................... 11 </p><p>When should you publish a sandbox? ........................................................................ 11 </p><p>How frequently should you publish a sandbox? ......................................................... 12 </p><p>Deleting a Sandbox ............................................................................................................. 12 </p><p>Using Sandboxes: Guidelines .................................................................................. 13 </p><p>Guidelines: Multiple Users ................................................................................................... 13 </p><p>Guidelines: Sandbox Operations ......................................................................................... 15 </p><p>Exceptions ......................................................................................................... 16 </p><p>Lookup Types and Values ........................................................................................ 16 </p><p>Reports and Custom Fields ...................................................................................... 16 </p><p>Web Services (including Object Workflows) ............................................................. 17 </p><p>Import and Export .................................................................................................... 18 </p><p>Server Exception ...................................................................................................... 18 </p><p>ProfileMO.xml Error ............................................................................................................. 18 </p><p>Data Security Service Error ................................................................................................. 18 </p><p>Other Errors ......................................................................................................................... 19 </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers </p><p>Development Lifecycle ...................................................................................... 20 </p><p>Publishing a Sandbox .............................................................................................. 22 </p><p>Example of Multi-week Cycle ................................................................................... 24 </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers 1 </p><p>Executive Overview Todays dynamic business landscape demands fast responses from companies to address both customer and market needs, typically requiring several different teams to work simultaneously on application customizations while sharing the same data model and configuration starting point. </p><p>Oracle Fusion CRM Applications use sandboxes to allow companies to meet these requirements. Sandboxes let companies avoid the risk of conflicts between teams working in parallel, and give administrators the ability to test all customizations before their users ever see them. </p><p>Introduction Sandboxes in Oracle Fusion Applications provide robust out-of-the-box functionality to help isolate and control customization efforts without impacting other users configuration environments, and/or the production environment. You can read all about sandboxes in the Oracle Fusion Applications Extensibility Guide. Or, review this document to learn how to customize Oracle Fusion CRM Applications, specifically, using sandboxes. </p><p>Sandboxes let users make changes isolated from the mainline application, as well as from other sandboxes. The mainline is the source of data and definitions used at the time of creating a new sandbox. Business analysts can implement and test application customizations in a sandbox and, once satisfied, publish them back to the mainline. When making changes in a sandbox, your customizations will not be available to any other sandbox or to the mainline application until you have published your sandbox. When publishing a sandbox, the included application customizations overwrite the mainline applications existing configuration. </p><p>Within this document, the term customizing means to change an existing artifact, for example, adding a new field to an existing business object. Customizing also refers to changing what is displayed on a page, as well as creating a completely new artifact, such as a business object or page. </p><p>Note: NEVER make your customizations directly in the mainline. Instead, always use sandboxes whenever possible. </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers 2 </p><p>Customizations At a technical level, your customizations affect two major areas: the Metadata Services repository and the database layer. </p><p>First, all changes result in the creation or updating of many files within the Metadata Services repository. Your customizations are stored as XML files in the repository, segregated by sandbox. </p><p>Additionally, as custom objects and fields are created, their definitions are allocated to generic placeholders that already exist as tables or columns in the database. </p><p>Composers </p><p>To customize applications within Oracle Fusion CRM, you can use these composers: </p><p>COMPOSER USE </p><p>CRM Application Composer </p><p>Customize pages, business objects, and all the artifacts that support them (such as fields, pages, buttons and links, security, server scripts, and saved searches). Extend Oracle Fusion CRM applications by creating completely new business objects and artifacts. For more information on customizing Oracle Fusion CRM Applications using CRM Application Composer, refer Oracle Fusion Applications CRM Extensibility Guide on Oracle Technology Network at http://www.oracle.com/technetwork/indexes/documentation </p><p>Oracle Composer Customize pages. For more information on customizing pages using Oracle Composer, refer Oracle Fusion Applications Extensibility Guide on Oracle Technology Network at http://www.oracle.com/technetwork/indexes/documentation </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers 3 </p><p> CRM Application Composer </p><p> Oracle Composer </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers 4 </p><p>Sandboxes Sandboxes handle metadata customizations made to the data stored in the Metadata Services repository (MDS). </p><p>Sandboxes typically have one of two purposes: </p><p> Test-Only - Users perform all customizations using the test-only sandbox. Changes made here should never be published to the mainline. </p><p> Publish - Once satisfied with the customizations made in the test-only sandbox, users replicate their changes in this sandbox, and then publish the sandbox. This sandbox type is also known as the integration sandbox, because teams working in parallel will use this sandbox as the final staging point before publication to the mainline. </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers 5 </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers 6 </p><p>Using the Sandbox Manager </p><p>Maintain sandboxes using the Sandbox Manager, which you can access by selecting Manage Sandboxes from the Administration menu. </p><p>Note: Do not use the Customization Manager without approval from Oracle Support. </p><p>Use the Sandbox Manager to: </p><p> Create sandboxes </p><p> Activate sandboxes </p><p> Delete sandboxes </p><p> Publish sandboxes </p><p> Review a list of available or published sandboxes </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers 7 </p><p>Creating a Sandbox </p><p>Using the Sandbox Manager, create a new sandbox by using the Actions menu option, or by clicking the New button. </p><p>Note: Data security sandboxes are not supported in Oracle Fusion CRM and are reserved for Oracle internal use. </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers 8 </p><p>Creating Multiple Sandboxes </p><p>When creating multiple sandboxes, create one for testing only which you will never publish. Also, create a single integration sandbox that you do intend to eventually publish. </p><p> Private sandbox Testing and prototyping only. Never publish. Delete when finished, or after its related integration sandbox has been published. </p><p> Integration sandbox Testing and validations with the intent to publish. Ensure only one administrator user works in this sandbox at a time. Coordinate with other administrator users to manually migrate (re-key) approved configurations from a private sandbox into the integration sandbox. </p><p> To avoid confusion, establish naming conventions such as rjones4_19nopub, mhoope4_19nopub, and integrationsandbox4_19topub. The date indicates when a sandbox was derived from the mainline application. You can also check the sandbox creation date and time using the Sandbox Manager, as illustrated below: </p><p>Activating a Sandbox </p><p>After creating a new sandbox, you must next activate it to be able to use it. To activate a sandbox, select the sandbox and then click the Set as Active button. Only one sandbox can be active at a time. </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers 9 </p><p>Once a sandbox is active for your session, the sandbox name is displayed in the global area: </p><p>After activating a sandbox, you should always log out from Oracle Fusion Applications and log back in. This helps you to avoid conflicts by ensuring that the cache is cleared. </p><p>Note that if you log out and log back in, your sandbox remains active. A sandbox remains active until you exit the sandbox, publish the sandbox, delete the sandbox, or set another sandbox as active. </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers 10 </p><p>Exiting a Sandbox and Returning to the Mainline </p><p>To exit from the current sandbox session, hover over the sandbox name in the global area and then click Exit Sandbox. </p><p>The sandbox session is closed and you are returned to the mainline application. After exiting a sandbox session, you should always log out from Oracle Fusion Applications and log back in. This helps you to avoid conflicts by ensuring that the cache is cleared. </p><p>IMPORTANT: Once back in the mainline application, avoid making customizations using the CRM Application Composer. To start making customizations again, use the Sandbox Manager to set a new sandbox as active. </p></li><li><p> Customizing Oracle Fusion CRM Applications Using Sandboxes </p><p>Copyright 2012, Oracle and/or its affiliates. All rights reserved. </p><p>Oracle Proprietary and Confidential - Distributed to Authorized Customers 11 </p><p>Publishing a Sandbox </p><p>Completed customizations created within a test-only sandbox and then replicated to an integration sandbox must be published to be available to other users in the mainline application. Always publish customizations from the integration sandbox only. Refer to the Development Lifecycl...</p></li></ul>