OIM 11g Release 2 (11.1.2) Download, Installation, and Configuration- Part 2 Repository Creation Utility

OIM 11g Release 2 (11.1.2) Download, Installation, and Configuration- Part 2 Repository Creation Utility

• Please view the Part 1 of this thread. Installation of JDK and Weblogic Server 
• Download Oracle Fusion Middleware Repository Creation Utility 11g (11.1.2.1.0) for Microsoft Windows (32-bit)
• Unzip the downloaded RCU file. Navigate to RCU_HOME/bin directory and run utility

• Launch of rcu will bring the following screen. Click Next.

• Choose the option to Create

• Enter Database Information Host, Port, Service Name, Username and Password.

• Click OK on Checking Prerequisites window.

• Choose the Components to be created. Press Next 

• Enter the password for all schemas and press Next

• Press Create

• Press Close when done.

OIM 11.1.2 R2: Install AD connector on Connector Server

OIM 11.1.2 R2: Install AD connector on Connector Server

Prior to installing the AD connector on the connector server, please ensure that the connector server is installed is installed. Please click here for more details on installation of connector server.

1.       Stop the Connector Server.

2.       From the installation media, copy the ActiveDirectory.Connector-1.1.0.6380.zip file from the bundle directory to the CONNECTOR_SERVER_HOME directory. For Example: C:\Program Files\Identity Connectors\Connector Server. And unzip the ActiveDirectory.Connector-1.1.0.6380.zip file there. The contents of zip file should be directly in Connector Server directory.

3.       Delete the zip file and start the Connector Server Service for the connector bundle to be picked up by the Connector Server.

OIM 11g Release 2 (11.1.2) Download, Installation, and Configuration- Part 6 Configure Oracle Identity Manager Server.

OIM 11g Release 2 (11.1.2) Download, Installation, and Configuration- Part 6 Configure Oracle Identity Manager Server.

• Please view the Part 1 of this thread. Installation of JDK and Weblogic Server 
• Please view the Part 2 of this thread Installation of Repository using RCU
• Please view the Part 3 of this thread  Installation of SOA 11.1.1.6
• Please ensure that OIM 11.1.2.1 is installed
• Please view the Part 4 of this thread  Creating a new WebLogic Domain for Oracle Identity Manager and SOA

• Please view the Part 5 Configuring Database Security Store for an Oracle Identity and Access Management Domain

• Start the Administrator server $FM_HOME\user_projects\domains\base_domain\startWeblogic.cmd
• To start the Oracle Identity Manager 11g Configuration Wizard, execute the <IAM_Home>/bin/config.sh script (on UNIX) on the machine where the Administration Server is running. (<IAM_Home>\bin\config.bat on Windows). The Oracle Identity Manager 11g Configuration Wizard starts, and the Welcome Screen appears.

• Select OIM Server, Design console and Remote Manager

• Enter Connection string and Infrastructure Information, press Next

• Enter Weblogic Server URL, Username and Password

• 
  

OIM 11.1.2.2 : Deploying the SPML-DSML Service

OIM 11.1.2.2 : Deploying the SPML-DSML Service

1. Log in to the Oracle WebLogic Server Administration Console.


2. In the Change Center region, click Lock & Edit to enable modification to the settings on the page.

3. In the Domain Structure region, click Deployments.

4. On the right pane, click Install.

5. On the Locate deployment to install and prepare for deployment page, in the Path field, enter      
    OIM_HOME\server\apps. 




6. In the region following the Current Location field, select spml-dsml.ear and then click Next.

7. On the Choose targeting style page, click Next to accept the default selection and proceed with            installation.

8. On the Select deployment targets page, in the Available targets for spml-dsml region, select oim_server1 if Oracle Identity Manager is installed in a nonclustered environment. Otherwise, select oim_cluster.

9. Click Next.

10. On the Optional Settings page, in the Source accessibility region, select I will make the deployment accessible from the following location, and then click Next.

11. On the Review your choices and click Finish page, verify the data that you have provided, and then click Finish.

12. On the Settings for spml-dsml page, review the configuration information of the deployed SPML-DSML Service, and then click Save.

13. In the Change Center region, click Activate Changes for the changes to take effect.

14. On the left pane, in the Domain Structure region, click Deployments. 

15. On the right pane, in the Deployments table, select spml-dsml, and then from the Start list, select Servicing all requests. The SPML-DSML Service is started.

16 For Oracle WebLogic Server:
http://IP ADDRESS:NON-SSL PORT NUMBER/spmlws/OIMProvisioning

https://IP ADDRESS:SSL PORT NUMBER/spmlws/OIMProvisioning

OIM 11.1.2 R2: Installation of Connector Server

OIM 11.1.2 R2: Installation of Connector Server

The connector server is the Windows server. Before installing the Connector Server, ensure that .NET Framework 3.5 or above is installed on the same server where we are installing the Connector Server.

1.       Login on the Windows server (as referred as Dot Net Connector server)

2.       Extract the contents of the Connector Server package (Connector_Server_111210.zip) and locate the ServiceInstall-1.4.0.0.msi file.

3.       Install the Connector Server by running the ServiceInstall-1.4.0.0.msi file and following the wizard. The wizard takes you through the installation process step-by-step. After completion, the .NET Connector Server is registered as a Windows service.

4.  Start the Microsoft Services Console.

5.       If the .NET Connector Server is running, stop it by stopping the Windows service named Connector Server.

6.       To set a custom key for the .NET Connector Server, use the /setkey command-line argument, as follows:

a.       Change to the directory where the .NET Connector Server was installed. The default directory is:

C:\Program Files\Identity Connectors\Connector Server

b.      Run the following command:

ConnectorServer.exe /setkey NEW_KEY

In this command, NEW_KEY is the value for the new key. This key is required by any client that connects to this .NET Connector Server.

7.       Check the settings in the .NET Connector Server configuration file (ConnectorServer.exe.config). These settings are in the element named AppSettings. For example:

<add key="connectorserver.port" value="8759" />

<add key="connectorserver.usessl" value="false" />

<add key="connectorserver.certificatestorename" value="ConnectorServerSSLCertificate" />

<add key="connectorserver.ifaddress" value="0.0.0.0" />

Note: The most common settings you might want to change are:

ü  Port number: To change the port, set connectorserver.port to a value other than 8759 (If require in Production. For example: port enablement or Firewall issue).

Note: This port should be accessible from OIM server (Firewall opened)

ü  SSL settings: To use SSL, set connectorserver.usessl to true and then set connectorserver.certificatestorename to your certificate store name. (If the SSL is implemented)

8.       Save the following configuration information from the .NET Connector Server installation. This information must be specified while configuring the IT resource for the Connector Server:

ü  Host name or IP address

ü  Connector Server port

ü  Connector Server key values

ü  Whether SSL is enabled

9.       Restart Connector Server by restarting the Windows service.

Creating a wlfullclient.jar for JDK 1.6 client applications

Creating a wlfullclient.jar for JDK 1.6 client applications

Use the following steps to create a wlfullclient.jar file for a JDK 1.6 client application:

1.  Change directories to the server/lib directory.

cd WL_HOME/server/lib

2.  Use the following command to create wlfullclient.jar in the server/lib directory:

java -jar wljarbuilder.jar

3.  You can now copy and bundle the wlfullclient.jar with client applications.
4.  Add the wlfullclient.jar to the client application’s classpath.

Oracle SOA 11.1.1.6 Create RMA (Return Merchandise Authorization) using Oracle SOA B2B on AS2 Part 2

Oracle SOA 11.1.1.6 Create RMA (Return Merchandise Authorization) using Oracle SOA B2B on AS2 Part 2

Please refer to my earlier post on Generation of 180 B2B artifacts by navigating to the thread
Oracle SOA 11.1.1.6 Create RMA (Return Merchandise Authorization) using Oracle SOA B2B on AS2 Part 1

This thread discuss configuration of the AS2 communication channel using B2B console. To navigate to the SOA B2B console , please use the URL http://hostname:port/b2bconsole where hotname is the name of the host where Oracle SOA stack with b2B is installed, port is the port where the SOA Managed Server is listening.

1.) Click on administration.

2.) Click on document.

3.) Click on Document Types (EDI X12)

4.) Create a Version Type. (4010)

5.) Create a Document Type 180.

6.) Create Document Definition  by using the XSD and ECS file that were created using document Editor.