5.1 Creating Sandbox

Introduction

A sandbox in STSA is an isolated workspace used for modeling, testing, and validating stress testing configurations, without affecting the live production environment. It acts as a controlled environment where analysts can ingest metadata, configure variables, simulate models, and preview outcomes.

A Sandbox is used for the following:

  • To safely test new configurations and modeling scenarios.
  • To perform impact analysis without influencing production data.
  • To validate metadata and data catalog setups before actual stress testing execution.
  • To manage project-specific data and metadata in a structured and independent context.

The uses of Sandbox in STSA are as follows:

  • Hosts a cloned or migrated version of production metadata.
  • Serves as the foundation for defining portfolios, metrics, models, variables, and process pipelines.
  • Allows users to perform dry runs, trial configurations, or simulate project executions with custom data.
  • Facilitates consistent, reproducible project setups across different teams.
For general queries such as purpose, frequency, and lifecycle of sandbox usage, see the following sections:
To create a sandbox:
Prerequisites
  1. Create a new empty DB schema.

    CREATE USER schemaname IDENTIFIED BY password DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP QUOTA UNLIMITED ON USERS;

    Note:

    Ensure that the new database schema is created on the same database server as the OFSAA application database server.
  2. Ensure that you use the database name to create the workspace name.
  3. To enable the object migration, in CONFIGURATION table present in the AAI OFSAA setup, update the PMF_OM_SANDBOX_ENABLED parameter value from N to Y.
  4. Provide the required SELECT privileges to the target schema (atomic user) from the OFSAA application configuration schema.

    These privileges are predefined in the script config_table_privileges_for_atomic_user.sql, available at the following path on the OFSAA server:

    <FIC_HOME>/config_table_privileges_for_atomic_user.sql

    Run this script to assign all the necessary configuration table privileges to the specified schema.

    
grant create SESSION to schemaname;
grant create PROCEDURE to schemaname;
grant create SEQUENCE to schemaname;
grant create TABLE to schemaname;
grant create TRIGGER to schemaname;
grant create VIEW to schemaname;
grant create MATERIALIZED VIEW to schemaname;
grant create SYNONYM to schemaname;
grant create TYPE to schemaname;
grant SELECT ON DBA_TABLES TO schemaname;
grant SELECT ON DBA_MVIEWS TO schemaname;
grant SELECT ON DBA_TAB_IDENTITY_COLS TO schemaname;
grant SELECT ON DBA_TAB_COLS TO schemaname;
grant SELECT ON DBA_TAB_COMMENTS TO schemaname;
grant SELECT ON DBA_VIEWS TO schemaname;
grant SELECT ON DBA_SOURCE TO schemaname;
  5. Provide select grant to the AAI application configuration schema, configured during the installation of the application that you want to do stress testing on:
    
grant select on CSSMS_USR_PROFILE to schemaname;
grant select on CSSMS_ROLE_MAST to schemaname;
grant select on CSSMS_GROUP_MAST to schemaname;
grant select on CSSMS_FUNCTION_MAST to schemaname;
grant select on CSSMS_USR_GROUP_MAP to schemaname;
grant select on CSSMS_USR_GROUP_DSN_SEG_MAP to schemaname;
grant select on CSSMS_ROLE_FUNCTION_MAP to schemaname;
grant select on cssms_usr_attrib to schemaname;
grant select on AAI_DB_DETAIL to schemaname;
grant select on CSSMS_GROUP_ROLE_MAP to schemaname;
grant select on CSSMS_SEGMENT_MAST to schemaname;
grant select on BATCH_TASK to schemaname;
grant select on CSSMS_USR_DSN_SEG_MAP to schemaname;
grant select on CSSMS_USR_ROLE_MAP to schemaname;
grant select on CSSMS_METADATA_SEGMENT_MAP to schemaname;
grant select on BATCH_RUN to schemaname;
grant select on PR2_FILTERS to schemaname;
grant select on PR2_TASK_FILTER_DETAIL to schemaname;
grant select on ST_STRESS_MASTER to schemaname;
grant select on BATCH_MASTER to schemaname;
grant select on ICC_MESSAGELOG to schemaname;
grant select on MF_MODEL_SCRIPT_MASTER to schemaname;
grant select on MF_INPUT_VALUES to schemaname;
grant select on MF_MODEL_OUTPUT_VALUES to schemaname;
grant select on DB_MASTER to schemaname;
grant select on DSNMASTER to schemaname;
grant select on pr2_rule_map to schemaname;
grant select on FORMS_LOCALE_MASTER to schemaname;
grant ALL PRIVILEGES on pr2_rule_map_pr to schemaname;
grant ALL PRIVILEGES on pr2_rule_map_pr_tmp to schemaname;
grant select on pr2_rule_map_exclude to schemaname;
grant ALL PRIVILEGES on pr2_rule_map_exclude_pr to schemaname;
grant ALL PRIVILEGES on pr2_rule_map_exclude_pr_tmp to schemaname;
grant select on pr2_run_object to schemaname;
grant select on pr2_run_object_member to schemaname;
grant select on pr2_run_map to schemaname;
grant select on pr2_run_execution_b to schemaname;
grant select on AAI_BACKDATED_EXEC_INFO to schemaname;
grant select on pr2_run_execution_filter to schemaname;
grant select on pr2_firerun_filter to schemaname;
grant select on pr2_filters to schemaname;
grant select on configuration to schemaname;
grant select on batch_parameter to schemaname;
grant select on component_master to schemaname;
grant select on MDB_OBJECT_TYPE_ATT_LAYOUT to schemaname;
grant select on REV_OBJECT_ATTRIBUTE_DTL to schemaname;
grant select on mdb_object_dependencies to schemaname;
grant select on REV_STAT_DATA to schemaname;
grant select on REV_OBJECT_REPOSITORY_B to schemaname;
grant select on REV_OBJECT_REPOSITORY_TL to schemaname;
grant select on REV_OBJECT_ATTRIBUTE_DTL_MLS to schemaname;
grant select on REV_OBJECT_APPLICATION_MAP to schemaname;
grant select on MDB_OBJ_EXPR_DETAILS to schemaname;
grant select on MDB_EXECUTION_DETAILS to schemaname;
grant select on REV_OBJECT_TYPES_CD to schemaname;
grant select on REV_OBJECT_TYPES_MLS to schemaname;
grant select on REV_APPLICATIONS_CD to schemaname;
grant select on REV_APPLICATIONS_MLS to schemaname;
grant select on METADATA_BROWSER_LOCALE to schemaname;
grant select on MDB_STAT_DATA to schemaname;
grant select on MDB_OBJECT_TYPE_LAYOUT to schemaname;
grant select on ofsa_md_id_ref to schemaname;
grant select on MDB_ETL_MAPPING to schemaname;
grant select on setupinfo to schemaname;
grant select on LOCALEREPOSITORY to schemaname;
grant select on MF_MODEL_MASTER to schemaname;
grant select on MF_SANDBOX_MASTER to schemaname;
grant select on MF_VARIABLE_MASTER to schemaname;
grant select on MF_TECHNIQUE_MASTER to schemaname;
grant select on MDB_RULE_SOURCE_HEADER to schemaname;
grant select on MDB_RULE_TARGET_HEADER to schemaname;
grant select on MDB_RULE_TARGET_MEMBER_HEADER to schemaname;
grant select on MDB_RULE_GRID_DATA to schemaname;
grant select on MDB_MODEL_MAPPING to schemaname;
grant delete on AAI_MAP_MAPPER to schemaname;
grant insert on AAI_MAP_MAPPER to schemaname;
grant update on AAI_MAP_MAPPER to schemaname;
grant select on AAI_MAP_MAPPER to schemaname;
grant select on infodom_patches to schemaname;
grant select on MDB_OBJECTS_GROUP_MASTER to schemaname;
grant select on MDB_OBJECTS_GROUPING to schemaname;
grant select on aai_wf_filter_exec_map to schemaname;
grant select,insert,update on aai_wf_request_queue to schemaname;
grant select,insert,update on aai_wf_request_queue_hist to schemaname;
grant select,insert,update on aai_wf_request_parameter to schemaname;
grant select,insert,update on aai_wf_request_parameter_hist to schemaname;
grant select,insert,update on AAI_WF_APP_REGISTRATION to schemaname;
---------------Attribution Analaysis------------------------------------

grant select on AAI_WF_ATTR_ANALYSIS_DETAILS to schemaname;
grant select on AAI_WF_ATTR_COMPONENT to schemaname;
grant select on AAI_WF_RUNSKEY_MAPPING to schemaname;
grant select on AAI_WF_ATTR_VAR_MAPPING to schemaname;
grant select on AAI_WF_ATTR_COMP_VAR_MAPPING to schemaname;
grant select on AAI_WF_ATTR_EXECUTION to schemaname;
grant select on AAI_WF_ATTR_VAR_EXEC_INST to schemaname;
grant select on AAI_WF_RUN_EXEC_PARAMS to schemaname;
---------------Attribution Analaysis------------------------------------

grant select on cssms_usr_group_map_view to schemaname;
grant execute on checkEnvForDataRedaction to schemaname;

-----  Begin ABC 8.1 grant Scripts----------

grant select,references on AAI_ABC_DIM_PURPOSE to schemaname;
grant select,references on AAI_ABC_DIM_SB_EFFECTIVE to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_TYPE to schemaname;
grant select,references on AAI_ABC_DIM_STATUS_QTNR to schemaname;
grant select,references on AAI_ABC_DIM_STATUS_QTNR_MLS to schemaname;
grant select,references on AAI_ABC_DIM_SIGNOFF_TYPES to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_APP_TYPES to schemaname;
grant select,references on AAI_ABC_DIM_QTN_SEL_TYPE to schemaname;
grant select,references on AAI_ABC_DIM_QTN_TYPE to schemaname;
grant select,insert,update,delete,references on AAI_ABC_DIM_QTN_CATEGORY to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_RESP_TYPE to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_DEPUTE_TYPE to schemaname;
grant select,references on AAI_ABC_DIM_RESULT_SET_CAT_OPT to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_CRITICALITY to schemaname;
grant select,references on AAI_ABC_SETUP_COMPONENTS to schemaname;
grant select,references on AAI_ABC_SETUP_QTN_CONF_TYP to schemaname;
grant select,references on AAI_ABC_SETUP_QTN_CONF_TYP_MLS to schemaname;
grant select,references on AAI_ABC_FCT_QTNR_CONF to schemaname;
grant select,references on AAI_ABC_DIM_PURPOSE_MLS to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_TYPE_MLS to schemaname;
grant select,references on AAI_ABC_DIM_EMPLOYEE to schemaname;
grant select,insert,update,delete,references on AAI_ABC_DIM_QTN_CATEGORY_MLS to schemaname;
grant select,references on AAI_ABC_DIM_QTN_SEL_TYPE_MLS to schemaname;
grant select,references on AAI_ABC_DIM_QTN_TYPE_MLS to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_APP_TYPES_MLS to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_CRITICAL_MLS to schemaname;
grant select,references on AAI_ABC_DIM_QTN_DEPUT_TYPE_MLS to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_RESP_TYPE_MLS to schemaname;
grant select,references on AAI_ABC_DIM_RESSET_CAT_OPT_MLS to schemaname;
grant select,references on AAI_ABC_DIM_SB_EFFECTIVE_MLS to schemaname;
grant select,references on AAI_ABC_DIM_SIGNOFF_TYPES_MLS to schemaname;
grant select,references on AAI_ABC_FCT_QTNR_ENTITY_MAP to schemaname;
grant select,references on AAI_ABC_SETUP_COMPONENTS_MLS to schemaname;
grant select,references on AAI_ABC_ENTITY_DOCUMENT_MAP to schemaname;
grant select,references on AAI_ABC_DIM_OR_STATUS_MLS to schemaname;
grant select,references on MESSAGES_EN_US to schemaname;
grant select,references on AAI_ABC_DIM_FREQUENCY to schemaname;
grant select,references on AAI_ABC_SETUP_PURPOSE_PROC_MAP to schemaname;
grant select,references on AAI_ABC_DIM_FREQUENCY_MLS to schemaname;
grant select,references on AAI_ABC_SETUP_DOCUMENT_CLASS to schemaname;
grant select,references on AAI_ABC_SETUP_DOC_CLASS_MLS to schemaname;
grant select,references on AAI_ABC_DIM_OR_STATUS to schemaname;
grant select,references on DOCUMENT_MASTER to schemaname;
grant select,references on AAI_ABC_DIM_COND_OPERATORS to schemaname;
grant select,references on AAI_ABC_DIM_COND_OPERATORS_MLS to schemaname;
grant select,references on AAI_ABC_DIM_OPT_COND_SCOPE to schemaname;
grant select,references on AAI_ABC_DIM_OPT_COND_SCOPE_MLS to schemaname;
grant select,references on AAI_ABC_DIM_QTN_OPT_TYPES to schemaname;
grant select,references on AAI_ABC_DIM_QTN_OPT_TYPES_MLS to schemaname;
grant select,references on AAI_APP_TL to schemaname;
grant select,references on AAI_ABC_DIM_QTN_DT_RST_CAT to schemaname;
grant select,references on AAI_ABC_DIM_QTN_DT_RST_CAT_MLS to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_AUDIT_STATUS to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_AUDIT_STS_MLS to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_ERROR_CODE to schemaname;
grant select,references on AAI_ABC_DIM_QTNR_ERROR_COD_MLS to schemaname;
grant select on AAI_WF_APP_REGISTRATION to schemaname;
grant select on CSSMS_PROFILE_HOLIDAY_MAP to schemaname;
grant select on CSSMS_PROFILE_MAST to schemaname;
grant select on WEB_SERVER_INFO to schemaname;
grant select,references on AAI_APP_B to schemaname;
grant select,references on AAI_USR_PREFERENCE_DETAIL to schemaname;
grant select on RTI_UI_EXCLUDE_PDM_LIST  to schemaname;
grant select on RTI_VIR_PHY_TBL_NAME  to schemaname;
grant select on RTI_DOMAIN  to schemaname;
----  End ABC 8.1 grant Scripts----------
grant select on aai_wf_process_b to &atomic_db_user;
grant select on aai_wf_process_tl to &atomic_db_user;
  6. Create a wallet alias for the newly created schema in the STSA server wallet.

    For more information, see the Setup the Password Stores for Database User Accounts.

  7. Create a data store object for the newly created data schema and the OFSAA production information domain schema from the Add Data Store pane in the Create Workspace wizard.
    Ensure that:
    • A wallet alias is created for the OFSAA production information domain schema.
    • All additional properties for the data store are completed if you are using single-click workspace provisioning.

    For more information about creating a Data Store, see the Adding a Data Store in the Oracle Financial Services Model Management and Governance User Guide.

  8. Register the simulation and production environment details in the OFSAA Environment.

    Note:

    To access the Register Environment menu link, the ENVSUMM function must be mapped to the user.
    To register the environments:
    1. Click the context menu representing the user name and click OFSAA Environment.
    2. Click Register Environment and provide the name, description and select the type of environment from the Type drop-dowm menu.
    Provide the following metadata for the production environment:
    • PROD_infodom - provide the production workspace name. For example, OFSAA_PROD.
    • PROD_instanceName - provide the production instance name.
    • PROD_instanceAccessToken - generate and provide the instance access token from the production workspace.
    • PROD_baseUrl - provide the production base URL.
    Provide the following metadata for the simulation (sandbox) environment:
    • SIM_instanceName - provide the simulation workspace name. For example, SANDBOX1.
    • SIM_instanceAccessToken - generate and provide the instance access token.
    • SIM_baseUrl - provide the simulation or sandbox base url.
    • SIM_sys_auth_user - provide the simulation or sandbox user details.
    • SIM_sys_admin_user - provide the admin user details.
    • SIM_ftpshare_path - provide the ftpshare path details.

    Note:

    Generate the instance name and instance access token from the application's OFSAA Environment. For more information, see the Creating the Instance Access Token section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.
Procedure
  1. Login to STSA.
    The Workspace Summary page is displayed.
  2. Click Add Workspace.
    The Create Workspace wizard is displayed.
  3. (Optional) To create a workspace from a template, click Use Template option.
    The zip files stored in the path: <STSA Installation path>/scratch/ofsaadb/ftpshare/mmg/seeded/workspace-templates is displayed in the Library drop-down menu. On selecting the template, any pre-filled values are overridden with the template provided values.
  4. In the Basic Details pane, provide the following details and click Next:
    1. (Optional) If there is an imported file for the basic details, import the basic details using the Import Archive File option. Select the archived file or drag the file from its directory and drop it in the box.
      If you use this feature, the other fields described in the preceding rows are auto populated.
    2. In the Workspace Code field, enter the workspace ID.

      Note:

      Ensure that you provide a maximum of 12 characters for the workspace code and you can provide alphanumeric characters.

      Note:

      Ensure that you do not use the word "ALL" as a workspace code.
    3. In the Purpose field, provide a description for the workspace.
    4. In the User-group field, select the user groups who require access to this workspace.

      Note:

      In the User-group field, you must select the user-groups that are part of the OFSAA application (production environment).
    5. In the Production field, select the production OFSAA environment.
    6. In the Simulation field, select the sandbox OFSAA environment.

      The Simulation Infodom is auto-populated after you enter the same value in the Workspace Code field.

      Provide a Simulation Segment Code. This code specifies a unique segment or folder where you want to import objects. The code must meet the following requirements:
      • Maximum of 10 characters
      • No special characters (except underscore)
      • No extra spaces
    7. In the Application Server IP/Hostname field, provide the IP address or host name of the OFSAA application.

      Note:

      In the Application Server IP/Hostname field, the IP/hostname must match the production environment's host/IP address. Refer to the V_DB_Server column in the AAI_DB_Details table in the OFSAA Configuration schema.
    8. Click More Options.
    9. In the Type field, select the either of the following options:
      • Modeling

        Note:

        Select this option to create the MMG workspace.
      • Simulation
      • STSA

        Note:

        This option is selected by default
      Select this option to provision the workspace. All data model objects from the production schema are copied to the sandbox schema.

      Note:

      If you want to proceed with selecting specific objects instead of replicating all objects, use the More Options feature.
    10. In the Simulation DB Schema Name field, provide the name of the newly created schema.
    11. In the Simulation DB Password field, provide the password of the schema.
    12. In the Simulation Jdbc Connection String field, provide the JDBC URL.
      The format is: jdbc:oracle:thin:@host_name:port_number/service_name
  5. Click Next.
  6. In the Workspace Schema section, select schema (sandbox) name or add a data schema in the Data Schema field and click Next.
    For more information about creating a Data Store, see the Adding a Data Store in the Oracle Financial Services Model Management and Governance User Guide.
  7. To copy all the database objects from production to sandbox, provide the following details in the Data Sourcing section:
    1. In the Source Data Schema drop-down menu, select the atomic schema of the production environment.
    2. In the Target Data Schema drop-down menu, select the sandbox or newly created workspace.
    3. In the Object Type drop-down menu, select each object type and the database objects under each object type.

      Note:

      If you select the child tables for import, the parent table is automatically selected.
  8. Click the Data Pipeline tab. In the Pipeline field, select the pipeline you want to add and click Next
  9. Skip the Metadata Sourcing step for this release. and click Next.

    Note:

    Metadata migration is performed using the OFSA Object Migration option, not through the UI.
    Import the metadata of the application, using the OFSA migration option.

    For information about OFSAA metadata required for metadata migration see the Migrating Production Metadata to Sandbox from OFSAA Instance section.

    For more information about the migration, see the Object Migration section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.

  10. In the Validate pane review all the selections and click Finish and then click Physicalise Workspace.
    The status of the workspace creation is displayed in the Summary screen.
    If the workspace is created sucessfully, the following message is displayed: 
    Workspace creation successful.

    (Optional) To download the current configurations, click Finish and then click Download Configuration Archive.

    You can use this downloaded configuration for the Import Archive File option that is available in the Create Workspace wizard the next time you are creating a sandbox with similar configurations.

    If the sandbox creation fails, then check the log messages and fix the errors and then restart the sandbox creation process.

  11. To return to the Workspace Summary page, click the Close button.

After the sandbox is created:

Note:

  • The model upload or object registration process must be manually triggered in the OFSAA Application (production environment) for newly created workspace infodom.
  • Ensure that the tnsnames.ora file in the OFSAA production environment contains the correct entry for the workspace schema.
  • The connection pooling for the newly created JNDI name must be available in the web layer.
  • A default EST (Display Name: EST - Global Glossary of STSA) glossary is created. For more information about mapping the global glossary to glossary terms, see the Uploading Glossary Terms Mapping to Table Columns and Tags section.
  • A database service job is created internally and triggered automatically. For more information, see the Adding Database Service in STSA section.
  • When EST_ENABLED attribute is enabled in the configuration file, the modelling and simulation type workspaces are listed along with STSA workspace.
  • A background database service job is triggered post-sandbox creation for indexing and synchronization.
  • If the EST_ENABLED attribute is set to Y, you will see STSA workspaces alongside modeling and simulation workspaces.