Skip Headers

Oracle® Argus Safety English Administrator's Guide Release 7.0.1 E26224-01 |
Home | Book List | Contents | Contact Us

Previous
| PDF · Mobi · ePub

# 8 Multi-Tenancy Best Practices

This chapter provides the administrator of a multi-tenant environment best practice information.

## Best Practices in a Multi-Tenant Environment

This section lists the the best practices to follow in a multi-tenant environment.

### Single Sign On

Single Sign On needs to be enabled to have the capability to switch client context and to open the Argus Safety application from the Global Worklists/Application Access Portlet. If SSO is enabled, then it becomes mandatory for a user to be configured as an LDAP user in all the enterprises where the data displays on the screen/portlet.

#### Accessing Argus Safety Directly via URL

It is expected that the you will pass the internal Enterprise ID as a URL parameter for the Argus Safety application to open with the appropriate Enterprise context. If Enterprise ID is not passed, the user is validated against the default enterprise.

For ESM Mapping Utility and EOSU Tool which are client-server applications and do not have a mechanism to specify the Enterprise ID, will always validate users against the default enterprise. Hence, users that are expected to login into these applications are configured with appropriate access/roles within default enterprise. For this reason, "Active" checkbox for the default enterprise is always marked checked and disabled in Global Enterprise Management screen.

### Global Hompage and Portlets

Set up appropriate Portal user and user group privileges to restrict access to Portlets and the Global Homepage. It is recommended that the you configure the out-of-the-box Portlets so these (specified below) are accessible to all multi-tenant users who need to access data across multiple enterprises except the ones specifically recommended for administrators.

- Global Worklist - New

- Global Worklist - Open

- Global Worklist - Action Items

- Global Worklist - Contacts

- Global Enterprise Management: Recommended for Administrators

- Global User Management: Recommended for Administrators

- Application Access Portlet

#### Global Worklists Columns

The system allows flexibility to hide some of the fields/columns in the Global Worklist Portlets through the Global Worklist grid/menu XML(s) which resides on the Web Server(s). It is advisable to hide only those fields/columns which are not updated nor referred by any Worklist context menu actions.

#### Global User Management

In order to apply updates to the "Synchronizable" fields to all the enterprises in the system, you should maintain some administrative users with the Console'Access Management 'Groups' Menus 'Console: Access Management: User menu access enabled for all enterprises in the system.

#### User-Enterprise Association

When a user is copied from one enterprise to another, it is expected that you have set up the appropriate site and the usergroups in the target enterprise. Otherwise the user-association with fail with the appropriate error message.

#### New User Creation/Association

Argus Console allows same UserID to be used to create different users across multiple enterprises. It is recommended that this feature is only be used if users are not expected to be shared across enterprises. Otherwise, if users are expected to be shared across multiple enterprises, then same UserID will not be used to create different users across different enterprises. Instead of that, a user created in one enterprise is associated to other enterprises through Global User Management.

#### Inactivating an Enterprise

It is recommended that you first archive all the cases belonging to the Enterprise before inactivating the Enterprise.

### New Enterprise Setup

It is expected that you create and choose the appropriate Enterprises with generic configuration data which can be used as source for copying the configuration data for creation of a new enterprises. Following is a list of items that the you are recommended to ensure that the values being copied from the source enterprise are appropriate for the newly created enterprise:

- Advanced Conditions used within any configuration item

- Reporting Destination Code List ' Company identifier field values

- System Numbering and LAM System Numbering Formats

- ESM Mapping Utility ' Setup INI File Setup ' Service DB Setup ' Outgoing and Incoming folders for each Agency.

Common Profile Switches

- MedWatch Configuration

- Documentum configuration

- Lot Number Web Service Configuration

### Segregated by Enterprise

Following is the list of items that are segregated by enterprises. It is recommended that you configure distinct values across enterprises to ensure proper data segregation across enterprises

- Literature Intake folder: Argus Console ' Common Profile Switches ' Argus J ' Shared Path for the Literature Intake

- Case Intake folder: Argus Console ' Code List ' User Sites ' Intake File Path

- Path for New Case from Image: Argus Console ' Common Profile Switches ' Case Processing ' Default Network directory for scanned images

- E2B Incoming Folder: ESM Mapping Utility ' Setup INI File Setup ' Service DB Setup ' Incoming Folder

- Site Printers: Argus Console ' Code List ' User Sites ' Site Printers ' Path

#### Maintaining Consistency Across Enterprises

The following is the list of items that are segregated by enterprises but the CRO is recommended to maintain consistent across all enterprises:

- Common Profile Switches ' Argus Insight URL

- Common Profile Switches ' Argus Safety Load Balancer Server

- System Configuration ' Enabled Modules

### Shared Across Enterprises

Following is the list of items that are common for all enterprises

- MedDRA and WHO Web Services

- Common Profile Switches ' Security ' LDAP ' Enable/disable LDAP

- Common Profile Switches ' Security ' LDAP ' LDAP Server configuration

- Common Profile Switches ' Security ' Enable/disable SSO

- Common Profile Switches ' Security ' SSO Header Configuration

- Common Profile Switches ' Case Processing ' Where to store temporary case information during data entry

- Common Profile Switches ' Case Processing 'Auto Archiving ' The database job and its frequency - "Execution Period (in Days)"

- Default Enterprise

The common profile switches (related to SSO, LDAP, Auto Archiving job & frequencyand Temporary Case Data Storage) which are common for all enterprises will only be displayed, updated and audit logged in DEFAULT enterprise. This is because any update to global level profile switches impacts all enterprises and is controlled. Also, such an update will also require propagation of the audit log to all other enterprises where the current user may not even exist or may not have proper access.

### Pre-upgrade Considerations for Existing Databases

Make sure that all the AG Service users (login user id) in all the databases that are to be merged into single database are in sync with the DEFAULT ENTERPRISE. If there are AG Service users in other enterprises which do not exist in the DEFAULT ENTERPRISE, then you can either rename their login user IDs to map them to existing AG Service users in the DEFAULT ENTERPRISE or delete them. If extra users are found in other enterprises during multi-tenant database migration, then they will be marked disabled and you will not be enable them later.

Make sure that all the event & indication and who-drug encoding dictionaries used in Argus Console ' System Configuration 'Common Profile Switches 'Case Form Configuration 'Auto Encoding, Dictionary and Central Encoding section and Argus Console ' Business Configuration 'Studies 'Enable Study Specific Encoding 'Auto Encoding dialog, in all databases that are to be merged into single database are already loaded in the target database with the same name. This is required to enable the automatic linking of dictionaries configured in the separate databases to the already existing dictionaries present in the target database during the database merge script/process.

### Post-upgrade Considerations for Existing Databases

E2B Outgoing and Incoming folders is configured again in ESM Mapping Utility because various folders for different transmission methods are now merged as one pair of folders for all transmission methods. Now these are saved into database rather than the ESM Service INI file.

Document Type field value from ESM Service configuration and AG Service configuration tool is now be configured again into Argus Console ' Common Profile Switches ' Documentum configuration as these fields are now moved to Argus Console.

Make sure that all the event & indication and who-drug encoding dictionaries used in Argus Console ' System Configuration 'Common Profile Switches 'Case Form Configuration 'Auto Encoding, Dictionary and Central Encoding section and Argus Console ' Business Configuration 'Studies 'Enable Study Specific Encoding 'Auto Encoding dialog, in the newly migrated enterprises are linked properly to the global dictionaries already present in the target database. This is required to correct any dictionary configuration linking that could not be done automatically by the database merge script due to mismatch in dictionary names in the source and target databases.

### Documentum Migration

Existing single-tenant as well as multi-tenant Documentum users upgrading to AS 7.0 release, and are migrating/keeping all the documents in the Documentum server, is also add additional attributes- "enterprise_id" and "enterprise_short_name" and populate these appropriately for all their documents that are to be accessed by Argus Safety in Documentum server.

Existing single-tenant as well as multi-tenant users which are upgrading to AS 7.0 release, and have configured "Use Logged in User's Username/Password" for Argus Console ' System Configuration ' Common Profile Switches ' Document Management for Case Attachments will switch to Common Username/Password for Documentum login if not already configured for E2B, Expedited and Periodic Reports.

MedDRA and WHO Webservices: As MedDRA and WHO webservice is common for each enterprise, it will use only single version for encoding events and drugs. However, as these web services use the dictionaries configured in Argus Console ' System Configuration 'Common Profile Switches 'Case Form Configuration 'Auto Encoding, Dictionary and Central Encoding section for the respective enterprises for populating dictionary id and dictionary version information for the encoded items, configure these dictionaries as same across all enterprises.