Sunday, May 12, 2013

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 ( and locate the ServiceInstall- file.
3.       Install the Connector Server by running the ServiceInstall- 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="" />
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.
  2. cd WL_HOME/server/lib
  3.  Use the following command to create wlfullclient.jar in the server/lib directory:
  4. java -jar wljarbuilder.jar
  5.  You can now copy and bundle the wlfullclient.jar with client applications.
  6.  Add the wlfullclient.jar to the client application’s classpath.

Wednesday, May 8, 2013

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

Oracle SOA 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 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.

Oracle Customer Care and Billing 2.6 IWS Services to be accessed from SOA 11g running JDK 1.6

Oracle Customer Care and Billing 2.6 is deployed on WebLogic 12c. Web l ogic 12c uses JDK 1.8, which uses TLS1.2 for Transport Level Sec...