- Managing Sandboxes
- Skin Customization in OIM
- Customizing Pages at Runtime
- Securing a Task Flow Region Using EL Expressions
- Customizing OIM Help
- Developing Managed Beans and Task Flows
- Configuring Additional Request Form
- Managing UI Customizations
- UI Customization Best Practices
Managing Sandboxes
- Activate
- Deactivate
- Publish
Note:
Before publishing a sandbox, export the sandbox to a ZIP file to have a backup of UI customizations done.
Oracle recommends creating a backup of the MDS before publishing any sandbox. MDS backup can be created by using tools, such as Oracle Enterprise Manager. See "Creating MDS Backup" for information about creating a backup of the MDS by using Oracle Enterprise Manager.
Export
Import
Note:
When you create a sandbox, a new branch is created. You can modify MDS content within that branch. Note that you will not be able to view the changes made in other sandboxes that are created later and published to the main branch. Similarly, when you try to merge this sandbox, a concurrent modification exception is generated. It is recommended that you edit the contents of the sandbox manually to remove the conflicting files. However, if manual editing is not possible, then create a new sandbox again and redo the change.
Skin Customization in Oracle Identity Manager
- Configuring a New Skin
- You can extend oim-alta skin to configure custom skins.
- oracle.iam.ui.custom-dev-starter-pack.war
- Changing Branding and Logo
- Via the Sandbox
Customizing Pages at Runtime
- Customizing Oracle Identity Manager can be broadly categorized into customizing the UI and extending the object definitions of the user, role, organization, catalog, and provisioning target resource entities.
- Using Expression Language in UI Customization
- Showing or Hiding UI Components Conditionally
- Showing Request Profiles Conditionally
- Validating Input Data Using ADF Validators
- <af:validateDateTimeRange>
- <af:validateLength>
- Marking Input Attribute as Required
- Adding a Link or Button
- Hiding and Deleting an ADF Component
- Showing and Hiding Attributes
- Customizing Unauthenticated Pages
- Customizing Certification Pages
- Customizing the Certification Detail Pane
- Adding Custom Attributes to the Certification Table
- Customizing the Certification Table
Securing a Task Flow Region Using EL Expressions
jazn-data.xml file
Customizing Oracle Identity Manager Help
Adding Custom Help Topics
Adding Inline Help
Customizing the Home Page
Adding a Tile to the Home Page
Launching a New Page From the Tile Icon - jsff.xml
Launching a New Page From the Tile Menu
Showing Tiles Conditionally
Developing Managed Beans and Task Flows
- Request beans: New instance of the bean is created for every request. JSFF component bindings and listeners are usually bound to request beans.
- State beans: Beans holding the state of the application, user session, or a particular flow. Values of components, such as af:inputText, can be bound to state beans. State beans must be serializable (implement java.io.Serializable) as ADF serializes/deserializes these beans between requests.
Tasks
- Setting Up the ViewController Project
- Setting Up a Model Project
- Adding Custom Managed Bean
- Deploying Custom Code to Oracle Identity Manager
- Using Managed Beans
Topics
- Showing Components Conditionally
- Prepopulating Fields Conditionally
- Setting a Conditional Mandatory Field
- Implementing Custom Field Validation
- Implementing Custom Cascading LOVs
- Customizing Forms By Using RequestFormContext
- Overriding the Submit Button in Request Catalog
- Launching Taskflows
- Creating an External Link
- Using Managed Beans to Populate Request Attributes
- Populating Request Attributes Using Managed Beans
- Populating Request Attributes by Using the Prepopulate Plug-in
- Using Public Taskflows
- Customizing Catalog Search
- Customizing Task Details Page for Approval Tasks
Configuring Additional Request Form
- Tasks
- Additional Request Information Concepts
- Additional Information for the Request Cart Item
- Additional Information for the Request
- Understanding the Guidelines for Developing Custom Taskflow for Additional Request Information
- Implementing Custom Taskflow for Additional Request Information
- Saving and Retrieving Additional Information in Managed Bean Developed for the Project
- Understanding the AdditionalRequestInfo Interface
- Using RequestFormContext to Achieve the Required Customizations
- Configuring Custom Taskflow for Additional Request Information
- Configuring Custom Taskflow for the Cart Item Level
- Configuring Additional Request Information at Request Level
- Validating Additional Request Information
- RequestDataValidator Plug-in
Migrating UI Customizations
Incremental T2P
Fusion Middleware Framework-Based Full T2P
UI Customization Best Practices
- Create sandboxes with detailed description
- Create a backup of MDS before publishing a sandbox
- Migrate all sandboxes to the target environment and publish in the same order
- Export the sandbox before publishing
- Test the sandbox before publishing
- Do not change default component IDs
- Use discretion when deleting components from a page
- Note that direct changes to default EOs/VOs are not supported
- Specify name space for JSFF tags
- Note that customizations are only allowed in site/site layer
- Note that each application instance or entitlement form has three page fragments (JSFF)
- create
- modify
- bulk
- Use Discretion when using the Searchable Picklist option
- Sign-out after adding/updating UDF
- Verify the UDF after adding it to the page
- Map UDF with correct LDAP attribute
- Deploy custom managed beans as part of the oracle.iam.ui.custom-dev-starter-pack.war shared library
- Consider replacing the entire taskflow
- Do not update Oracle Identity Manager WAR/EAR files
- Consider conditionally showing certain home page tiles
- Do not invoke Platform APIs from custom managed bean
- Use recommended value of Display Width while creating lookup UDFs (40)
