1. Cloud Native Deployment Guide
  2. Differences Between UIM Cloud Native and UIM Traditional Deployments

14 Differences Between UIM Cloud Native and UIM Traditional Deployments

If you are moving from a traditional deployment of UIM to a cloud native deployment, this section describes the differences between UIM cloud native and UIM traditional.

  • Embedded LDAP and Open LDAP

    You no longer need to create human users using the embedded LDAP capabilities of WebLogic Server.

    By default, UIM uses the WebLogic embedded LDAP as the authentication provider and all UIM fixed set of users are created in embedded LDAP during the creation of the instance. The UIM cloud native toolkit provides a sample configuration that uses OpenLDAP to demonstrate how to integrate with external LDAP server for human users.

    A sample script for populating users to OpenLDAP can be found at: $UIM_CNTK/samples/credentials/manage-uim-credentials.sh. See "Creating Users in OpenLDAP" for more details.

  • WebLogic Domain Configuration

    In a traditional deployment of UIM, the WebLogic domain configuration is done using WLST or the WebLogic Admin Console. In UIM cloud native, domain configuration is done by providing WDT metadata in the instance creation process. See "Extending the WebLogic Server Deploy Tooling (WDT) Model" for details.

    Do not perform WebLogic administrative activities such as changing the configuration, shutting down and restarting the server directly on the WebLogic Server cluster of the UIM cloud native instance. The same applies to the activities done using WebLogic Server Admin Console, WLST invocation, or any mechanism, other than those supplied by the specification files for updating and upgrading the UIM cloud native instance.

  • Incoming SAF and Outgoing SAF

    For incoming SAF agents, the originator must use T3 over HTTP tunneling.

    Outgoing SAF mechanism has not changed.

  • UIM Solution Cartridges

    Deploy the solution cartridges in UIM cloud native as follows.

    1. Build the customized image with solution cartridges.
    2. Deploy the cartridge using CMT or Design Studio on UIM cloud native running instance.

      In UIM Cloud Native, the cartridge management variables wladmin.host.name and wladmin.host.port are not required for deploying cartridges unlike in Traditional Deployments.

    See "Deploying Cartridges" for more information.

  • UIM Shared Storage File System: Dependency on shared file system is removed in UIM cloud native. Persistent Volume Mounts are used only for logging purpose.
  • Custom WebServices: The Custom Webservices are packaged in custom.ear in the traditional environment and are packaged in Inventory application in the cloud native. See "Customizing Images" to package the Custom WebServices.
  • UIM Application Roles: The assignment of UIM application roles to UIM users can be achieved using sample script provided in $UIM_CNTK/samples/credentials/assign-role.sh. The EM console can also be used like in traditional environment.
  • UIM User Interfaces: All UIM user interfaces are still available with both UIM traditional and UIM cloud native deployments. The UIs can be accessed using the default hostname: instance.project.uim.org and port 30305, which is the default but configurable and the path that is necessary for the specific UI. For example, to access the Inventory UI, use: 
    http://instance.project.uim.org:30305/Inventory
  • UIM API: Accessing UIM through the traditional APIs such as the Web Services API and the REST API has not changed.
  • UIM System Configuration Properties: UIM system configuration parameters can be controlled using the system-config.properties file. This configuration is still available in the UIM cloud native, but is managed differently. See "Customizing UIM Configuration Properties" for more details.