Add attributes on Solaris in a clustered environment

The VMM is configured with a default attribute schema that might not be compatible with LDAP server. If this is the case, extend the VMM attribute schema by adding new attributes that you can map between WebSphere Portal and user registry.

Add new attributes to user registry:

  1. Install the required Enterprise Archive (.ear) file on WAS.

    Environment Steps
    Standalone

    1. Open a command prompt.

      • cd WP_PROFILE/ConfigEngine


      ./ConfigEngine.sh wp-la-install-ear -DWasPassword=foo

    Cluster

    1. Open a command prompt on primary node.

      • cd WP_PROFILE/ConfigEngine


      ./ConfigEngine.sh wp-la-install-ear -DWasPassword=dmgr_password -DServerName=dmgr_server_name -DNodeName=node_name

    You can find the dmgr_server_name value in the WAS console under

    System administrator -> Deployment Manager -> Configuration tab -> General Properties -> Name.

    You can find the node_name value in the WAS console under

    System administrator -> Deployment Manager -> Runtime tab -> General Properties -> Node Name.

  2. Stop and restart the appropriate servers to propagate the changes.

  3. Edit WP_PROFILE/ConfigEngine/properties/wkplc.properties

  4. Enter a value under the VMM Property Extension Properties heading:

        la.providerURL
        la.propertyName
        la.entityTypes
        la.dataType
        la.multiValued

  5. Save changes to wkplc.properties.
    ./ConfigEngine.sh wp-add-property -DWasPassword=footo add the attribute to the user registry.

      This task performs an EJB call to WAS, which must authenticate against WAS. Depending on the configuration in the sas.client.props file, you may receive a popup window or a command line prompt asking for user identity and password. Enter the WAS user ID and password.

      If you have multiple properties to add, repeat all steps, except for the wp-la-install-ear task, until all new attributes are added.

  6. Stop and restart the appropriate servers to propagate the changes.

If you created clustered environment then performed the steps in this task, now run the update-jcr-admin task on the secondary node. See Enable LDAP security after cluster creation for instructions.


Parent

Adapt the attribute configuration


Previous

Query the defined attributes


Next topic

Mapping attributes on Solaris in a clustered environment


Related tasks


Start and stop servers, dmgrs, and node agents
Enable LDAP security after cluster creation

  Updated step 1.


+

Search Tips   |   Advanced Search