Deploying the connector involves the following steps:
Section 2.1, "Files and Directories on the Installation Media"
Section 2.2, "Determining the Release Number of the Connector"
Depending on the release of Oracle Identity Manager that you use, perform the procedures described in one of the following sections:
Section 2.5, "Configuring the Oracle Identity Manager Server"
Section 2.6, "Installation and Configuration on the Target System"
Table 2-1 lists the files and directories on the installation media.
Table 2-1 Files and Directories On the Connector Installation Media
| File in the Installation Media Directory | Description |
|---|---|
|
Files in the DataSets directory |
These XML files specify the information to be submitted by the requester during a request-based provisioning operation. Note: These files are applicable to Oracle Identity Manager releases prior to 11.1.2. |
|
lib/xliGroupWise65.jar |
This JAR file contains the class files required for provisioning. During connector installation, this file is copied to the following location:
|
|
lib/xliGroupWiseRecon.jar |
This JAR file contains the class files required for reconciliation. During connector installation, this file is copied to the following location:
|
|
lib/tcGroupWise65.dll |
This DLL file contains the native code required to communicate with the Novell GroupWise client. |
|
Files in the resources directory |
Each of these resource bundles contains language-specific information that is used by the connector. During connector installation, these resource bundles are copied to the following location:
Note: A resource bundle is a file containing localized versions of the text strings that are displayed on the Administrative and User Console. These text strings include GUI element labels and messages. |
|
test/troubleshoot/tcGroupWise65.dll |
This file contains the native code required to interface with Novell GroupWise. |
|
test/troubleshoot/tstGroupWise65.jar |
This file contains the wrapper files and the test utility class. |
|
test/troubleshoot/testcreate.bat test/troubleshoot/testmodify.bat test/troubleshoot/testdelete.bat |
These batch files are used to run specific tests on the connector. They call the appropriate method in the test utility class. |
|
test/troubleshoot/config.properties |
In this configuration file, connection information about Novell eDirectory and Novell GroupWise and other related parameters are specified. |
|
test/troubleshoot/log4j.properties |
This file is used to specify the directory in which the log file is to be created when you run the testing utility. |
|
xml/xliGroupwiseResourceObject.xml |
This file contains definitions for the following components of the connector:
|
|
xml/ GroupwiseXLResourceObject.xml |
This XML file contains the configuration for the Xellerate User. You must import this file only if you plan to use the connector in trusted source reconciliation mode. |
Note:
The files in the test directory are used only to run tests on the connector.Note:
If you are using Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x, then the procedure described in this section is optional.If you are using Oracle Identity Manager release 11.1.x, then skip this section.
You might have a deployment of an earlier release of the connector. While deploying the latest release, you might want to know the release number of the earlier release. To determine the release number of the connector that has already been deployed:
In a temporary directory, extract the contents of the following JAR file:
OIM_HOME/xellerate/JavaTasks/xliGroupWise65.jar
Open the manifest.mf file in a text editor. The manifest.mf file is one of the files bundled inside the xliGroupWise65.jar file.
In the manifest.mf file, the release number of the connector is displayed as the value of the Version property.
Note:
In this guide, the term Connector Installer has been used to refer to the Connector Installer feature of the Oracle Identity Manager Administrative and User Console.Installing the connector on Oracle Identity Manager release 9.1.0.x or release 11.1.x involves the following procedure:
To run the Connector Installer:
Copy the contents of the connector installation media directory into the following directory:
Note:
In an Oracle Identity Manager cluster, copy this JAR file to each node of the cluster.For Oracle Identity Manager release 9.1.0.x: OIM_HOME/xellerate/ConnectorDefaultDirectory
For Oracle Identity Manager release 11.1.x: OIM_HOME/server/ConnectorDefaultDirectory
Log in to the Administrative and User Console by using the user account described in the "Creating the User Account for Installing Connectors" section of the following guide:
For Oracle Identity Manager release 9.1.0.x:
Oracle Identity Manager Administrative and User Console Guide
For Oracle Identity Manager release 11.1.x:
Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
For Oracle Identity Manager release 9.1.0.x:
Click Deployment Management, and then click Install Connector.
For Oracle Identity Manager release 11.1.1:
On the Welcome to Identity Manager Advanced Administration page, in the System Management region, click Install Connector.
For Oracle Identity Manager release 11.1.2:
In the left pane, under System Management, click Manage Connector. In the Manage Connector page, click Install.
From the Connector List list, select Novell GroupWise RELEASE_NUMBER. This list displays the names and release numbers of connectors whose installation files you copy into the default connector installation directory in Step 1.
If you have copied the installation files into a different directory, then:
In the Alternative Directory field, enter the full path and name of that directory.
To repopulate the list of connectors in the Connector List list, click Refresh.
From the Connector List list, select Novell GroupWise RELEASE_NUMBER.
Click Load.
To start the installation process, click Continue.
The following tasks are performed in sequence:
Configuration of connector libraries
Import of the connector Target Resource user configuration XML file (by using the Deployment Manager). If you want to import the target system as a trusted source for reconciliation, then see Section 2.5.3, "Configuring Trusted Source Reconciliation"or more information.
Compilation of adapters
On successful completion of a task, a check mark is displayed for the task. If a task fails, then an X mark and a message stating the reason for failure are displayed. Depending on the reason for the failure, make the required correction and then perform one of the following steps:
Retry the installation by clicking Retry.
Cancel the installation and begin again from Step 1.
If all three tasks of the connector installation process are successful, then a message indicating successful installation is displayed. In addition, a list of the steps that you must perform after the installation is displayed. These steps are as follows:
Ensuring that the prerequisites for using the connector are addressed
Note:
At this stage, run the Oracle Identity Manager PurgeCache utility to load the server cache with content from the connector resource bundle in order to view the list of prerequisites. See Section 2.5.6, "Clearing Content Related to Connector Resource Bundles from the Server Cache" for information about running the PurgeCache utility.There are no prerequisites for some predefined connectors.
Configuring the IT resource for the connector
Record the name of the IT resource displayed on this page. The procedure to configure the IT resource is described later in this guide.
Configuring the scheduled tasks that are created when you installed the connector
Record the names of the scheduled tasks displayed on this page. The procedure to configure these scheduled tasks is described later in this guide.
When you run the Connector Installer, it copies the connector files and external code files to destination directories on the Oracle Identity Manager host computer. These files are listed in Table 2-1.
Installing the Connector in an Oracle Identity Manager Cluster
While installing Oracle Identity Manager in a clustered environment, you must copy all the JAR files and the contents of the connectorResources directory into the corresponding directories on each node of the cluster. See Section 2.1, "Files and Directories on the Installation Media" for information about the files that you must copy and their destination locations on the Oracle Identity Manager server.
You must specify values for the parameters of the GroupWise XRM, eDirectory IT Resource, and GroupWise IT Resource IT resource as follows:
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
For Oracle Identity Manager release 9.x or 11.1.1:
Log in to the Administrative and User Console
For Oracle Identity Manager release 11.1.2:
Log in to Oracle Identity System Administration
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
If you are using Oracle Identity Manager release 9.x, expand Resource Management, and then click Manage IT Resource.
If you are using Oracle Identity Manager release 11.1.1, then:
On the Welcome to Oracle Identity Manager Self Service page, click Advanced.
On the Welcome to Oracle Identity Manager Advanced Administration page, in the Configuration region, click Manage IT Resource.
If you are using Oracle Identity Manager release 11.1.2, then in the left pane under Configuration, click IT Resource.
In the IT Resource Name field on the Manage IT Resource page, enter GroupWise IT Resource and then click Search.
Click the edit icon for the IT resource.
From the list at the top of the page, select Details and Parameters.
Specify values for the parameters of the GroupWise IT Resource IT resource. See Section 2.3.2.1, "Specifying Values for IT Resource Parameters" for information about the parameters of the IT resource and the values to be specified.
To save the values, click Update.
On the View IT Resource Details and Parameters page, click Back to Search Results.
Repeat Steps 3 through 8 for the GroupWise XRM and eDirectory IT Resource IT resources.
This section provides information about the parameters for the following IT resources:
You must specify values for the Groupwise XRM IT resource parameters listed in the following table.
| Parameter | Description |
|---|---|
| Service Name | Name of the remote manager
Default value: |
| URL | Host name or IP address of the server hosting the remote manager
Sample value: |
After you specify values for these IT resource parameters, proceed to Step 7 of the procedure to configure IT resources.
You must specify values for the eDirectory IT Resource IT resource parameters listed in the following table.
| Parameter | Description |
|---|---|
| Admin Id | DN of the user who has administrator rights on the target LDAP
If this administrator has read/search rights, then that would be sufficient because this administrator is used only to search for existing users and no modification is done in Novell eDirectory. Sample value: |
| Admin Password | Password of the administrator
Sample value: |
| Server Address | Host name or IP address of the server hosting Novell eDirectory |
| Root DN | Base DN from where the search for the user starts
Sample value: |
| Port | Port number of the Novell eDirectory server
Sample value: |
| SSL | Specifies whether or not SSL is to be used to secure communication between Oracle Identity Manager and Novell GroupWise
The value can be Note: It is recommended that you enable SSL to secure communication with the target system. |
| Last Recon TimeStamp | For the first reconciliation run, the time stamp value is not set. For subsequent rounds of reconciliation, the time at which the previous round of reconciliation was completed is stored in this parameter.
Sample value: |
| Prov Attribute Lookup Code | Name of the lookup definition that has the target attribute mappings required for provisioning
The value must be |
| Recon Attribute Lookup Code | Name of the lookup definition that has the target attribute mappings required for reconciliation
The value must be |
| Use XL Org Structure | If set to true, then the Oracle Identity Manager Organization structure is used during provisioning and reconciliation.
If set to |
After you specify values for these IT resource parameters, proceed to Step 7 of the procedure to configure IT resources.
You must specify values for the GroupWise IT Resource IT resource parameters listed in the following table.
| Parameter | Description |
|---|---|
| GroupWise Domain DN or Path | See the "GroupWise Domain DN or Path" section for detailed information about this parameter. |
| Admin User ID | DN of the user who has administrator rights on the target Novell GroupWise server
This administrator must have read/write access to the Novell GroupWise system/domain database. Ensure that this DN is entered in the dot format and not in the comma format. For example:
|
| Admin Password | Password of the administrator |
| eDir Context | The Novell eDirectory context below which the administrator is present. The administrator ID plus this context should be the complete DN of the administrator. This context is usually one level below the eDirectory tree.
For example: Suppose the DN of the administrator is as follows: cn=admin.ou=admgrp.o=marketing Then, the value of this parameter can be either |
| eDir Server Address | Host name or IP address of the server hosting Novell eDirectory |
| eDir Tree | Name of the Novell eDirectory tree under which the Novell GroupWise domain and the administrator are present
This is the topmost level in Novell eDirectory. Sample value: |
| UseEDirAuth | Specifies whether the target Novell GroupWise uses the Novell eDirectory password or the Novell GroupWise password for authentication.
If it is set to |
| Last Recon TimeStamp | The value is empty for the first reconciliation run. After that, the time at which the last reconciliation run was completed is stored in this parameter. |
| Recon Attribute Lookup Code | Contains the target attributes to be reconciled
Sample lookup definition: AttrName.Recon.Map.GW |
| CustomizedReconQuery | Query condition on which reconciliation must be based
If you specify a query condition for this parameter, then the target system records are searched based on the query condition. If you want to reconcile all the target system records, then do not specify a value for this parameter. The query can be composed with the Sample value: For more information about this parameter, refer to the "Limited Reconciliation" section. |
The complete DN of the Novell GroupWise domain or the path of the domain folder must be specified in one of the following ways:
Local System Path
The local system path can be specified in any one of the following ways:
By using the Domain DN path as follows:
Domain DN: 'cn=GWdomain.ou=org_unit_name.dc=companyname.dc=com.o=org_name'
For example:
Domain DN: 'cn=MyGWdomain.ou=MyDomains.dc=ExampleWidgets.dc=com.o=EXAMPLE'
Note:
Use dots (not commas) to separate the object classes as shown in the preceding example.By using the local directory path as follows:
drive:\\domain_directory_path
For example:
f:\\groupwise\\testdomain
UNC Path
The UNC path can be specified in any one of the following ways:
By using the host name as follows
\\hostname\share\\domainfolder
For example
\\testsvr\\myshare\\testdomain
By using the IP address as follows:
\\IPaddress\\share_name\\domain_name
For example:
\\10.0.0.1\\myshare\\testdomain
The recommended method is to use the DN or the local directory path. If the domain is on a different computer, then map that folder locally and mention the local path. Use this method if you are not able to connect to the domain by using the DN.
After you specify values for these IT resource parameters, proceed to Step 7 of the procedure to configure IT resources.
Installing the connector on any Oracle Identity Manager release between release 8.5.3.1 through 9.0.3.x involves the following procedures:
The connector files to be copied and the directories to which you must copy them are given in the following table.
Note:
See Section 2.1, "Files and Directories on the Installation Media" for more information about these files.To copy the ldap.jar file into the required directory:
Log on to the Novell Web site at
http://developer.novell.com/wiki/index.php/Special:Downloads/jldap/builds/netware_windows/
Download the following file from the Novell Web site:
novell-jldap-devel-2005.10.03-1netware_windows.zip
The size of the file is 11.1 MB.
Extract the contents of the file that you downloaded in Step 2.
Copy the ldap.jar file from the novell-jldap-devel-2005.10.03-1netware_windows\jldap_2005.10.03\lib directory to the OIM_HOME\xellerate\ThirdParty directory on the Oracle Identity Manager server.
To copy the ldapbp.jar file into the required directory:
Log on the following Web site:
Click the Download JNDI 1.2.1 & More button.
From the table on the page that is displayed, select the LDAP Service Provider 1.2.4 check box and download the ldap-1_2_4.zip file.
Extract the ldapbp.jar file from the ldap-1_2_4.zip file.
Copy the ldapbp.jar file into the OIM_HOME/xellerate/ThirdParty directory on the Oracle Identity Manager server.
Note:
While installing Oracle Identity Manager in a clustered environment, you copy the contents of the installation directory to each node of the cluster. Similarly, you must copy the contents of the connectorResources directory and the JAR files to the corresponding directories on each node of the cluster.Perform this procedure only if you are using Oracle Identity Manager release 9.x. As mentioned in Section 2.1, "Files and Directories on the Installation Media," the connector XML file contains definitions of the components of the connector. By importing the connector XML file, you create these components in Oracle Identity Manager.
To import the connector XML file into Oracle Identity Manager:
Open the Oracle Identity Manager Administrative and User Console.
Click the Deployment Management link on the left navigation bar.
Click the Import link under Deployment Management. A dialog box for opening files is displayed.
Locate and open the xliGroupwiseResourceObject.xml file, which is in the OIM_HOME/xellerate/groupwise/xml directory. Details of this XML file are shown on the File Preview page.
Click Add File. The Substitutions page is displayed.
Click Next. The Confirmation page is displayed.
Click Next. The Provide IT Resource Instance Data page for the GroupWise XRM IT resource is displayed.
Specify values for the parameters of the GroupWise IT Resource IT resource. See Section 2.3.2.1, "Specifying Values for IT Resource Parameters" for information about the values to be specified.
Click Next. The Provide IT Resource Instance Data page for a new instance of the Remote Manager resource type is displayed.
Repeat Steps 7, 8, and 9 for the GroupWise XRM and eDirectory IT Resource IT resources.
Click Skip to specify that you do not want to define another IT resource. The Confirmation page is displayed.
See Also:
If you want to define another IT resource, then see Oracle Identity Manager Administrative and User Console Guide for instructions.Click View Selections.
The contents of the XML file are displayed on the Import page. You may see a cross-shaped icon along with some nodes. These nodes represent Oracle Identity Manager entities that are redundant. Before you import the connector XML file, you must remove these entities by right-clicking each node and then selecting Remove.
Click Import. The connector file is imported into Oracle Identity Manager.
Note:
Perform the procedure described in this section only if you want to use the provisioning features of Oracle Identity Manager for this target system.Adapters are used to implement provisioning functions. The following adapters are imported into Oracle Identity Manager when you import the connector XML file:
See Also:
Section 1.6.6, "Provisioning Functions" for a listing of the provisioning functions that are available with this connectorNGW Create Mailbox
NGW Delete Mailbox
NGW Disable Mailbox
NGW Enable Mailbox
NGW Move User to PostOffice
NGW Add User to Distribution List
NGW Remove User from Distribution List
NGW Add Nickname to User
NGW Reset Password
NGW Change User Password
NGW PP String
NGW Delete Nickname of User
You must compile these adapters before they can be used in provisioning operations.
To compile adapters by using the Adapter Manager form:
Open the Adapter Manager form.
To compile all the adapters that you import into the current database, select Compile All.
To compile multiple (but not all) adapters, select the adapters you want to compile. Then, select Compile Selected.
Note:
Click Compile Previously Failed to recompile only those adapters that were not compiled successfully. Such adapters do not have anOK compilation status.Click Start. Oracle Identity Manager compiles the selected adapters.
If Oracle Identity Manager is installed in a clustered environment, then copy the compiled adapters from the OIM_HOME/xellerate/Adapter directory to the same directory on each of the other nodes of the cluster. If required, overwrite the adapter files on the other nodes.
If you want to compile one adapter at a time, then use the Adapter Factory form.
See Also:
For information about using the Adapter Factory and Adapter Manager forms, see one of the following guides:For Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x:
Oracle Identity Manager Tools Reference Guide
For Oracle Identity Manager release 11.1.x:
Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager
To view detailed information about an adapter:
Highlight the adapter in the Adapter Manager form.
Double-click the row header of the adapter, or right-click the adapter.
Select Launch Adapter from the shortcut menu that is displayed. Details of the adapter are displayed.
Configuring the Oracle Identity Manager server involves performing the following procedures:
Section 2.5.1, "Configuring Oracle Identity Manager 11.1.2 or Later"
Section 2.5.6, "Clearing Content Related to Connector Resource Bundles from the Server Cache"
Section 2.5.8, "Configuring Oracle Identity Manager for Request-Based Provisioning"
If you are using Oracle Identity Manager release 11.1.2 or later, you must create additional metadata such as a UI form and an application instance. In addition, you must run entitlement and catalog synchronization jobs. These procedures are described in the following sections:
You must add properties to certain form fields. To do so:
Log in to Oracle Identity Manager Design Console.
Open User Distribution Lists form (UD_NGW_DIST).
Create a new form version.
In the Properties tab, for the Distribution List DN field, add Entitlement = true property.
Click Make Version Active.
Open Groupwise parent form (UD_NGWS_USR).
Create a new form version.
In the Properties tab, add the following properties:
For the GroupWise Server field, add ITResource = true property.
For the User ID field, add AccountName = true property.
For the User ID field, add AccountId = true property.
Click Make Version Active.
Create and activate a sandbox as follows. For detailed instructions, see the "Managing Sandboxes" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager.
On the upper navigation bar, click Sandboxes. The Manage Sandboxes page is displayed.
On the toolbar, click Create Sandbox. The Create Sandbox dialog box is displayed.
In the Sandbox Name field, enter a name for the sandbox. This is a mandatory field.
In the Sandbox Description field, enter a description of the sandbox. This is an optional field.
Click Save and Close. A message is displayed with the sandbox name and creation label.
Click OK. The sandbox is displayed in the Available Sandboxes section of the Manage Sandboxes page.
Select the sandbox that you created.
From the table showing the available sandboxes in the Manage Sandboxes page, select the newly created sandbox that you want to activate.
On the toolbar, click Activate Sandbox.
The sandbox is activated.
Create a new UI form as follows. For detailed instructions, see the "Managing Forms" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager.
In the left pane, under Configuration, click Form Designer.
Under Search Results, click Create.
Select the resource type for which you want to create the form, for example, GroupWise IT resource.
Enter a form name and click Create.
Create an application instance as follows. For detailed instructions, see the "Managing Application Instances" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager.
In the System Administration page, under Configuration in the left pane, click Application Instances.
Under Search Results, click Create.
Enter appropriate values for the fields displayed on the Attributes form and click Save.
In the Form drop-down list, select the newly created form and click Apply.
Publish the application instance for a particular organization.
To publish the sandbox that you created in Section 2.5.1.2, "Creating and Activating a Sandbox":
Close all the open tabs and pages.
From the table showing the available sandboxes in the Manage Sandboxes page, select the sandbox that you created in Section 2.5.1.2, "Creating and Activating a Sandbox."
On the toolbar, click Publish Sandbox. A message is displayed asking for confirmation.
Click Yes to confirm. The sandbox is published and the customizations it contained are merged with the main line.
To harvest entitlements and sync catalog:
Run the scheduled jobs for lookup field synchronization listed in Section 3.2, "Scheduled Task for Lookup Field Synchronization."
Run the Entitlement List scheduled job to populate Entitlement Assignment schema from child process form table. See the "Predefined Scheduled Tasks" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager for more information about this scheduled job.
Run the Catalog Synchronization Job scheduled job. See the "Predefined Scheduled Tasks" section in the Oracle Fusion Middleware Administrator's Guide for Oracle Identity Manager for more information about this scheduled job.
For any changes you do in the Form Designer, you must create a new UI form and update the changes in an application instance. To update an existing application instance with a new form:
Create a sandbox and activate it as described in Section 2.5.1.2, "Creating and Activating a Sandbox."
Create a new UI form for the resource as described in Section 2.5.1.3, "Creating a New UI Form."
Open the existing application instance.
In the Form field, select the new UI form that you created.
Save the application instance.
Publish the sandbox as described in Section 2.5.1.5, "Publishing a Sandbox."
Note:
If you are using Oracle Identity Manager 11g Release 2 (11.1.2.0.4) or later, then you must perform the steps mentioned in MetaLink note 1535369.1 to ensure provisioning operations work as expected.See the Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager for the procedure to display the user-defined fields (UDFs), such as eDirectory Connector Version, GroupWise Connector Version, and GUID, on the user interface (UI).
Note:
Perform the procedure described in this section only if you are using Oracle Identity Manager release 11.1.2 or later and you want to localize UI form field labels.To localize field label that you add to in UI forms:
Log in to Oracle Enterprise Manager.
In the left pane, expand Application Deployments and then select oracle.iam.console.identity.sysadmin.ear.
In the right pane, from the Application Deployment list, select MDS Configuration.
On the MDS Configuration page, click Export and save the archive to the local computer.
Extract the contents of the archive, and open the following file in a text editor:
SAVED_LOCATION\xliffBundles\oracle\iam\ui\runtime\BizEditorBundle.xlf
Edit the BizEditorBundle.xlf file in the following manner:
Search for the following text:
<file source-language="en" original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf" datatype="x-oracle-adf">
Replace with the following text:
<file source-language="en" target-language="LANG_CODE"
original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf"
datatype="x-oracle-adf">
In this text, replace LANG_CODE with the code of the language that you want to localize the form field labels. The following is a sample value for localizing the form field labels in Japanese:
<file source-language="en" target-language="ja" original="/xliffBundles/oracle/iam/ui/runtime/BizEditorBundle.xlf" datatype="x-oracle-adf">
Search for the application instance code. This procedure shows a sample edit for Novell GroupWise application instance. The original code is:
<trans-unit id="${adfBundle['oracle.adf.businesseditor.model.util.BaseRuntimeResourceBundle']['persdef.sessiondef.oracle.iam.ui.runtime.form.model.user.entity.userEO.UD_NGWS_USR_GATEWAY_ACCESS__c_description']}">
<source>Gateway Access</source>
<target/>
</trans-unit>
<trans-unit id="sessiondef.oracle.iam.ui.runtime.form.model.GRPFORM.entity.GRPFORMEO.UD_NGWS_USR_GATEWAY_ACCESS__c_LABEL">
<source>Gateway Access</source>
<target/>
</trans-unit>
Open the resource file from the connector package, for example GroupWise_ja.properties, and get the value of the attribute from the file, for example, global.udf.UD_NGWS_USR_GATEWAY_ACCESS=\u30B2\u30FC\u30C8\u30A6\u30A7\u30A4\u30FB\u30A2\u30AF\u30BB\u30B9.
Replace the original code shown in Step 6.c with the following:
<trans-unit id="${adfBundle['oracle.adf.businesseditor.model.util.BaseRuntimeResourceBundle']['persdef.sessiondef.oracle.iam.ui.runtime.form.model.user.entity.userEO.UD_NGWS_USR_GATEWAY_ACCESS__c_description']}">
<source>Gateway Access</source>
<target>\u30B2\u30FC\u30C8\u30A6\u30A7\u30A4\u30FB\u30A2\u30AF\u30BB\u30B9</target>
</trans-unit>
<trans-unit id="sessiondef.oracle.iam.ui.runtime.form.model.GRPFORM.entity.GRPFORMEO.UD_NGWS_USR_GATEWAY_ACCESS__c_LABEL">
<source>Gateway Access</source>
<target>\u30B2\u30FC\u30C8\u30A6\u30A7\u30A4\u30FB\u30A2\u30AF\u30BB\u30B9</target>
</trans-unit>
Repeat Steps 6.a through 6.d for all attributes of the process form.
Save the file as BizEditorBundle_LANG_CODE.xlf. In this file name, replace LANG_CODE with the code of the language to which you are localizing.
Sample file name: BizEditorBundle_ja.xlf.
Repackage the ZIP file and import it into MDS.
See Also:
The "Deploying and Undeploying Customizations" chapter in the Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager, for more information about exporting and importing metadata filesLog out of and log in to Oracle Identity Manager.
While configuring the connector, the target system can be designated as a trusted source or target resource. If you designate the target system as a trusted source, then both newly created and modified user accounts are reconciled in Oracle Identity Manager. If you designate the target system as a target resource, then only modified user accounts are reconciled in Oracle Identity Manager.
Note:
You can skip this section if you do not want to designate the target system as a trusted source for reconciliation.Configuring trusted source reconciliation involves the following steps:
Import the XML file for trusted source reconciliation, GroupwiseXLResourceObject.xml, by using the Deployment Manager. This section describes the procedure to import the XML file.
Note:
Only one target system can be designated as a trusted source. If you import the GroupwiseXLResourceObject.xml file while you have another trusted source configured, then both connector reconciliations would stop working.Set the TrustedSource scheduled task attribute to True. You specify a value for this attribute while configuring the user reconciliation scheduled task, which is described later in this guide.
To import the XML file for trusted source reconciliation:
Open the Oracle Identity Manager Administrative and User Console.
If you are using Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x, then:
Click the Deployment Management link on the left navigation bar.
Click the Import link under Deployment Management. A dialog box for opening files is displayed.
If you are using Oracle Identity Manager release 11.1.x, then:
On the Welcome page, click Advanced in the upper-right corner.
On the Welcome to Oracle Identity Manager Advanced Administration page, in the System Management region, click Import Deployment Manager File. A dialog box for opening files is displayed.
Locate and open the GroupwiseXLResourceObject.xml file, which is in the following directory:
For Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x:
OIM_HOME/xellerate/ConnectorDefaultDirectory/GroupWise_904120/xml
For Oracle Identity Manager release 11.1.x:
OIM_HOME/server/ConnectorDefaultDirectory/GroupWise_904120/xml
Click Add File. The Substitutions page is displayed.
Click Next. The Confirmation page is displayed.
Click Import.
In the message that is displayed, click Import to confirm that you want to import the XML file and then click OK.
After you import the XML file for trusted source reconciliation, you must set the value of the TrustedSource reconciliation scheduled task attribute to True. This procedure is described in Section 3.4, "Configuring Scheduled Tasks."
Depending on the Oracle Identity Manager release you are using, perform the instructions in one of the following sections:
Note:
In an Oracle Identity Manager cluster, you must perform this step on each node of the cluster. Then, restart each node.To configure the date format on Oracle Identity Manager:
To configure the date format on Oracle Identity Manager:
Open the Oracle Identity Manager Administrative and User Console.
On the Welcome page, click Advanced in the upper-right corner.
On the Welcome to Oracle Identity Manager Advanced Administration page, in the System Management region, click Search System Properties. Alternatively, you can click the System Management tab, and then click System Configuration.
On the left pane, search and open for the Default date format system property.
On the System Property Detail page, enter values for the following fields:
Property Name: Default Date Format
Keyword: XL.DefaultDateFormat
Value: yyyy/MM/dd hh : mm : ss z
Click Save to save the changes made.
A message confirming that the system property has been modified is displayed.
Note:
In an Oracle Identity Manager cluster, you must perform this step on each node of the cluster. Then, restart each node.Changing to the required input locale (language and country setting) involves installing the required fonts and setting the required input locale.
You may require the assistance of the system administrator to change to the required input locale.
Note:
In an Oracle Identity Manager cluster, you must perform this step on each node of the cluster. Then, restart each node.When you deploy the connector, the resource bundles are copied from the resources directory on the installation media into the OIM_HOME/xellerate/connectorResources directory for Oracle Identity Manager release 9.0.1 through 9.0.3.x and release 9.1.0.x, and Oracle Identity Manager database for Oracle Identity Manager release 11.1.x. Whenever you add a new resource bundle to the connectorResources directory or make a change in an existing resource bundle, you must clear content related to connector resource bundles from the server cache.
To clear content related to connector resource bundles from the server cache:
In a command window, perform one of the following steps:
If you are using Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x, then switch to the OIM_HOME/xellerate/bin directory.
If you are using Oracle Identity Manager release 11.1.x, then switch to the OIM_HOME/server/bin directory.
Note:
You must perform Step 1 before you perform Step 2. An exception is thrown if you run the command described in Step 2 as follows:For Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x:
OIM_HOME/xellerate/bin/SCRIPT_FILE_NAME
For Oracle Identity Manager release 11.1.x:
OIM_HOME/server/bin/SCRIPT_FILE_NAME
Enter one of the following commands:
Note:
You can use the PurgeCache utility to purge the cache for any content category. RunPurgeCache.bat CATEGORY_NAME on Microsoft Windows or PurgeCache.sh CATEGORY_NAME on UNIX. The CATEGORY_NAME argument represents the name of the content category that must be purged.
For example, the following commands purge Metadata entries from the server cache:
PurgeCache.bat MetaData
PurgeCache.sh MetaData
For Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x:
On Microsoft Windows: PurgeCache.bat ConnectorResourceBundle
On UNIX: PurgeCache.sh ConnectorResourceBundle
Note:
You can ignore the exception that is thrown when you perform Step 2. This exception is different from the one mentioned in Step 1.In this command, ConnectorResourceBundle is one of the content categories that you can delete from the server cache. See the following file for information about the other content categories:
OIM_HOME/xellerate/config/xlconfig.xml
For Oracle Identity Manager release 11.1.x:
On Microsoft Windows: PurgeCache.bat All
On UNIX: PurgeCache.sh All
When prompted, enter the user name and password of an account belonging to the SYSTEM ADMINISTRATORS group. In addition, you are prompted to enter the service URL in the following format:
t3://OIM_HOST_NAME:OIM_PORT_NUMBER
In this format:
Replace OIM_HOST_NAME with the host name or IP address of the Oracle Identity Manager host computer.
Replace OIM_PORT_NUMBER with the port on which Oracle Identity Manager is listening.
See Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager for more information about the PurgeCache utility.
Depending on the Oracle Identity Manager release you are using, perform the procedure described in one of the following sections:
Note:
In an Oracle Identity Manager cluster, perform this procedure on each node of the cluster. Then, restart each node.When you enable logging, Oracle Identity Manager automatically stores in a log file information about events that occur during the course of provisioning and reconciliation operations. To specify the type of event for which you want logging to take place, you can set the log level to one of the following:
ALL
This level enables logging for all events.
DEBUG
This level enables logging of information about fine-grained events that are useful for debugging.
INFO
This level enables logging of messages that highlight the progress of the application at a coarse-grained level.
WARN
This level enables logging of information about potentially harmful situations.
ERROR
This level enables logging of information about error events that might allow the application to continue running.
FATAL
This level enables logging of information about very severe error events that could cause the application to stop functioning.
OFF
This level disables logging for all events.
The file in which you set the log level and the log file path depend on the application server that you use:
Oracle WebLogic Server
To enable logging:
Add the following lines in the OIM_HOME/xellerate/config/log.properties file:
log4j.logger.XELLERATE=log_level log4j.logger.XL_INTG.GROUPWISE=log_level
In these lines, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO log4j.logger.XL_INTG.GROUPWISE=INFO
After you enable logging, the log information is written to the following file:
WebLogic_home/user_projects/domains/domain_name/server_name/server_name.log
IBM WebSphere Application Server
To enable logging:
Add the following lines in the OIM_HOME/xellerate/config/log.properties file:
log4j.logger.XELLERATE=log_level log4j.logger.XL_INTG.GROUPWISE=log_level
In these lines, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO log4j.logger.XL_INTG.GROUPWISE=INFO
After you enable logging, the log information is written to the following file:
WebSphere_home/AppServer/logs/server_name/startServer.log
JBoss Application Server
To enable logging:
In the JBOSS_HOME/server/default/conf/log4j.xml file, locate or add the following lines:
<category name="XELLERATE">
<priority value="log_level"/>
</category>
<category name="XL_INTG.GROUPWISE">
<priority value="log_level"/>
</category>
In the second XML code line of each set, replace log_level with the log level that you want to set. For example:
<category name="XELLERATE"> <priority value="INFO"/> </category>
<category name="XL_INTG.GROUPWISE"> <priority value="INFO"/> </category>
After you enable logging, the log information is written to the following file:
JBoss_home/server/default/log/server.log
Oracle Application Server
To enable logging:
Add the following lines in the OIM_HOME/xellerate/config/log.properties file:
log4j.logger.XELLERATE=log_level log4j.logger.XL_INTG.GROUPWISE=log_level
In these lines, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO log4j.logger.XL_INTG.GROUPWISE=INFO
After you enable logging, the log information is written to the following file:
OC4J_home/opmn/logs/default_group~home~default_group~1.log
Note:
In an Oracle Identity Manager cluster, perform this procedure on each node of the cluster. Then, restart each node.Oracle Identity Manager release 11.1.x uses Oracle Java Diagnostic Logging (OJDL) for logging. OJDL is based on java.util.logger. To specify the type of event for which you want logging to take place, you can set the log level to one of the following:
SEVERE.intValue()+100
This level enables logging of information about fatal errors.
SEVERE
This level enables logging of information about errors that might allow Oracle Identity Manager to continue running.
WARNING
This level enables logging of information about potentially harmful situations.
INFO
This level enables logging of messages that highlight the progress of the application.
CONFIG
This level enables logging of information about fine-grained events that are useful for debugging.
FINE, FINER, FINEST
These levels enable logging of information about fine-grained events, where FINEST logs information about all events.
These log levels are mapped to ODL message type and level combinations as shown in Table 2-2.
Table 2-2 Log Levels and ODL Message Type:Level Combinations
| Log Level | ODL Message Type:Level |
|---|---|
|
SEVERE.intValue()+100 |
INCIDENT_ERROR:1 |
|
SEVERE |
ERROR:1 |
|
WARNING |
WARNING:1 |
|
INFO |
NOTIFICATION:1 |
|
CONFIG |
NOTIFICATION:16 |
|
FINE |
TRACE:1 |
|
FINER |
TRACE:16 |
|
FINEST |
TRACE:32 |
The configuration file for OJDL is logging.xml, which is located at the following path:
DOMAIN_HOME/config/fmwconfig/servers/OIM_SERVER/logging.xml
Here, DOMAIN_HOME and OIM_SERVER are the domain name and server name specified during the installation of Oracle Identity Manager.
To enable logging in Oracle WebLogic Server:
Edit the logging.xml file as follows:
Add the following blocks in the file:
<log_handler name='groupwise-handler' level='[LOG_LEVEL]' class='oracle.core.ojdl.logging.ODLHandlerFactory'> <property name='logreader:' value='off'/> <property name='path' value='[FILE_NAME]'/> <property name='format' value='ODL-Text'/> <property name='useThreadName' value='true'/> <property name='locale' value='en'/> <property name='maxFileSize' value='5242880'/> <property name='maxLogSize' value='52428800'/> <property name='encoding' value='UTF-8'/> </log_handler>
<logger name="XL_INTG.GROUPWISE" level="[LOG_LEVEL]" useParentHandlers="false">
<handler name="groupwise-handler"/>
<handler name="console-handler"/>
</logger>
Replace both occurrences of [LOG_LEVEL] with the ODL message type and level combination that you require. Table 2-2 lists the supported message type and level combinations.
Similarly, replace [FILE_NAME] with the full path and name of the log file in which you want log messages to be recorded.
The following blocks show sample values for [LOG_LEVEL] and [FILE_NAME] :
<log_handler name='groupwise-handler' level='NOTIFICATION:1' class='oracle.core.ojdl.logging.ODLHandlerFactory'> <property name='logreader:' value='off'/> <property name='path' value='F:\MyMachine\middleware\user_projects\domains\base_domain1\servers\oim_server1\logs\oim_server1-diagnostic-1.log'/> <property name='format' value='ODL-Text'/> <property name='useThreadName' value='true'/> <property name='locale' value='en'/> <property name='maxFileSize' value='5242880'/> <property name='maxLogSize' value='52428800'/> <property name='encoding' value='UTF-8'/> </log_handler> <logger name="XL_INTG.GROUPWISE" level="NOTIFICATION:1" useParentHandlers="false"> <handler name="groupwise-handler"/> <handler name="console-handler"/> </logger>
With these sample values, when you use Oracle Identity Manager, all messages generated for this connector that are of a log level equal to or higher than the NOTIFICATION:1 level are recorded in the specified file.
Save and close the file.
Set the following environment variable to redirect the server logs to a file:
For Microsoft Windows:
set WLS_REDIRECT_LOG=FILENAME
For UNIX:
export WLS_REDIRECT_LOG=FILENAME
Replace FILENAME with the location and name of the file to which you want to redirect the output.
Restart the application server.
Note:
Perform the procedure described in this section only if you are using Oracle Identity Manager release 11.1.1 and you want to configure request-based provisioning.In request-based provisioning, an end user creates a request for a resource by using the Administrative and User Console. Administrators or other users can also create requests for a particular user. Requests for a particular resource on the resource can be viewed and approved by approvers designated in Oracle Identity Manager.
The following are features of request-based provisioning:
A user can be provisioned only one resource (account) on the target system.
Note:
Direct provisioning allows the provisioning of multiple target system accounts on the target system.Direct provisioning cannot be used if you enable request-based provisioning.
To configure request-based provisioning, perform the following procedures:
A request dataset is an XML file that specifies the information to be submitted by the requester during a provisioning operation. Predefined request datasets are shipped with this connector. These request datasets specify information about the default set of attributes for which the requester must submit information during a request-based provisioning operation. The following are the predefined request datasets available in the DataSets directory on the installation media:
ProvisionResourceGroupwise User.xml
ModifyResourceGroupwise User.xml
Copy these files from the installation media to any directory on the Oracle Identity Manager host computer. It is recommended that you create a directory structure as follows:
/custom/connector/RESOURCE_NAME
For example:
E:\MyDatasets\custom\connector\GrpWise
Note:
Until you complete the procedure to configure request-based provisioning, ensure that there are no other files or directories inside the parent directory in which you create the directory structure. In the preceding example, ensure that there are no other files or directories inside the E:\MyDatasets directory.The directory structure to which you copy the dataset files is the MDS location into which these files are imported after you run the Oracle Identity Manager MDS Import utility. The procedure to import dataset files is described in the next section.
Depending on your requirement, you can modify the file names of the request datasets. In addition, you can modify the information in the request datasets. See Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager for information on modifying request datasets.
All request datasets must be imported into the metadata store (MDS), which can be done by using the Oracle Identity Manager MDS Import utility.
To import a request dataset definition into MDS:
Ensure that you have set the environment for running the MDS Import utility. See Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager for detailed information about setting up the environment for MDS utilities.
Note:
While setting up the properties in the weblogic.properties file, ensure that the value of the metadata_from_loc property is the parent directory of the /custom/connector/RESOURCE_NAME directory. For example, while performing the procedure in Section 2.5.8.1, "Copying Predefined Request Datasets," if you copy the files to the E:\MyDatasets\custom\connector\GrpWise directory, then set the value of the metada_from_loc property toE:\MyDatasets.In a command window, change to the OIM_HOME\server\bin directory.
Run one of the following commands:
On Microsoft Windows
weblogicImportMetadata.bat
On UNIX
weblogicImportMetadata.sh
When prompted, enter the following values:
Please enter your username [weblogic]
Enter the username used to log in to the WebLogic server
Sample value: WL_User
Please enter your password [weblogic]
Enter the password used to log in to the WebLogic server.
Please enter your server URL [t3://localhost:7001]
Enter the URL of the application server in the following format:
t3://HOST_NAME_IP_ADDRESS:PORT
In this format, replace:
HOST_NAME_IP_ADDRESS with the host name or IP address of the computer on which Oracle Identity Manager is installed.
PORT with the port on which Oracle Identity Manager is listening.
The request dataset is imported into MDS.
To enable the Auto Save Form feature:
Log in to the Design Console.
Expand Process Management, and then double-click Process Definition.
Search for and open the Groupwise User process definition.
Select the Auto Save Form check box.
Click the Save icon.
Run the PurgeCache utility to clear content belonging to the Metadata category from the server cache. See Section 2.5.6, "Clearing Content Related to Connector Resource Bundles from the Server Cache" for instructions.
The procedure to configure request-based provisioning ends with this step.
This section discusses the following topics:
The Remote Manager enables mailbox provisioning operations on Novell GroupWise.
Note:
In this guide, the directory in which you install the Remote Manager is referred to as RM_HOME.The following are the prerequisites for installing the Remote Manager:
For Oracle Identity Manager release 9.1.0.x
If Novell GroupWise is running on 64-bit Microsoft Windows Server, then you must install the 64-bit version of JDK 1.5 or later before you install the Remote Manager.
For Oracle Identity Manager release 11.1.x
If Novell GroupWise is running on 64-bit Microsoft Windows Server, then before you install the Remote Manager, you must install Oracle WebLogic Application Server on the Remote Manager host computer. While installing the application server, do not select the JDK bundled with the application server. Instead, select an installed instance of a 64-bit version of JDK.
Note:
During the mailbox provisioning operations on Novell GroupWise, the Remote Manager may throw the following type of error:Get-ItemProperty: Cannot find path
To prevent such errors, you must ensure that the Remote Manager uses an installed instance of a 64-bit version of JDK.
To enable client-side authentication for the Remote Manager:
Open one of the following files in a text editor:
For Oracle Identity Manager release 9.1.0.x:
RM_HOME/xlremote/config/xlconfig.xml
For Oracle Identity Manager release 11.1.x:
OIM_HOME/remote_manager/config/xlconfig.xml
Set the ClientAuth property to true as follows:
<ClientAuth>true</ClientAuth>
If you are using Oracle Identity Manager release 9.1.0.x, then ensure that the RMIOverSSL property is set to true as follows:
<RMIOverSSL>true</RMIOverSSL>
Save and close the file.
If you are using Oracle Identity Manager release 9.1.0.x, then perform Steps 2 through 4 in the OIM_HOME/config/xlconfig.xml file.
The Remote Manager installation files are shipped along with the Oracle Identity Manager installation files. You can install the Remote Manager on any computer that is a part of the domain.
If you are using Oracle Identity Manager release 11.1.x, then see the Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager guide for instructions of installing the Remote Manager.
If you are using Oracle Identity Manager release 9.1.0.x, then depending on the application server that you use, perform the procedure to install the Remote Manager by following the instructions given in one of the following guides:
Oracle Identity Manager Installation and Configuration Guide for Oracle WebLogic Server
Oracle Identity Manager Installation and Configuration Guide for Oracle Application Server
Oracle Identity Manager Installation and Configuration Guide for JBoss Application Server
Oracle Identity Manager Installation and Configuration Guide for IBM WebSphere Application Server
If you are using Oracle Identity Manager release 9.1.0.x, then copy the following JAR files into the RM_HOME\xlremote\JavaTasks directory:
OIM_HOME/xellerate/lib/xlVO.jar
OIM_HOME/xellerate/lib/xlScheduler.jar
OIM_HOME/xellerate/lib/xlAPI.jar
INSTALL_MEDIA/lib/tcGroupWise65.dll
INSTALL_MEDIA/lib/xliGroupWiseRecon.jar
INSTALL_MEDIA/lib/xliGroupWise65.jar
If you are using Oracle Identity Manager release 11.1.x, then copy the following JAR files into the RM_HOME\xlremote\JavaTasks directory:
OIM_HOME/server/lib/xlVO.jar
OIM_HOME/server/lib/xlScheduler.jar
OIM_HOME/server/lib/xlAPI.jar
OIM_HOME/server/lib/xlUtils.jar
OIM_HOME/server/lib/xlRemoteManager.jar
OIM_HOME/server/lib/xlLogger.jar
Note:
In this guide, the connector installation media is referred to as INSTALL_MEDIA:INSTALL_MEDIA/lib/xliGroupWise65.jar
INSTALL_MEDIA/lib/xliGroupWiseRecon.jar
INSTALL_MEDIA/lib/tcGroupWise65.dll
Note:
To enable logging in the Remote Manager, create a log directory and file inside the RM_HOME directory. For example:RM_HOME/Log/Report.log
Specify the name of the Remote Manager as the value of the Remote Manager IT resource parameter. This parameter is described in Section 2.3.2.1, "Specifying Values for IT Resource Parameters."
See one of the following guides for information about modifying the value of an IT resource parameter:
For Oracle Identity Manager release 9.1.0.x:
Oracle Identity Manager Administrative and User Console Guide
For Oracle Identity Manager release 11.1.x:
Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager
You must install the Novell GroupWise Client for provisioning to work as per the troubleshooting step "GW_FAILED_TO_CREATE_INSTANCE".
To set up SSL connectivity between Oracle Identity Manager and the Novell GroupWise server:
Import the certificate from the target system into the JSDK (the JSDK that is used during installation of Oracle Identity Manager) cacerts keystore as follows:
keytool -import –alias alias_name -file certificate_file_name_with_complete_path –keystore JAVA_HOME/jre/lib/security/cacerts
Here, JAVA_HOME is the JDK directory used for Oracle Identity Manager.
Restart Oracle Identity Manager.
In the eDirectory IT Resource IT resource:
Set the SSL parameter value to true.
Set the Port parameter value to the SSL port number. Typically, this number is 636.