Error 503 when Launching Enterprise Manager

I have recently faced an issue on a domain migration where, when accessing the Enterprise Manager console, the following error was shown: "Error 503-Service Unavailable".

In fact, after some investigation I noticed that the EM application was running and configured properly on the Weblogic.

By reading the Doc ID 1297193.1 on My Oracle Support I was able to figure out that the actual missing configuration was on the targets.xml file that holds the information of the Farm Domain the EM shall be targeting.

This targets.xml file is located under:
MW_HOME/user_projects/domains/<your_domain>/sysman/state

and has the following information details:
<Target TYPE="oracle_ias_farm" NAME="Farm_%DOMAIN-NAME%" DISPLAY_NAME="Farm_%DOMAIN-NAME%">
<Property NAME="MachineName" VALUE="%ADMINSERVER-HOST-NAME%"/>
<Property NAME="Port" VALUE="%ADMINSERVER-PORT%"/>
<Property NAME="Protocol" VALUE="%JMX-PROTOCOL%"/>
<Property NAME="isLocal" VALUE="true"/>
<Property NAME="serviceURL" VALUE="%SERVICE-URL%"/>
<Property NAME="WebLogicHome" VALUE="%WEBLOGIC-HOME%"/>
<Property NAME="DomainHome" VALUE="%DOMAIN-HOME%"/>
</Target>


On my case, this file was empty so I had to add the necessary information for the EM application to connect to my target Farm:
<Targets>
<Target TYPE="oracle_ias_farm" NAME="Farm_soa_domain" DISPLAY_NAME="Farm_soa_domain">
<Property NAME="MachineName" VALUE="myhostname.com"/>
<Property NAME="Port" VALUE="7001"/>
<Property NAME="isLocal" VALUE="true"/>
<Property NAME="Protocol" VALUE="t3"/>
<Property NAME="serviceURL" VALUE="service:jmx:t3://myhostname.com:7001/jndi/weblogic.management.mbeanservers.domainruntime"/>
<Property NAME="WebLogicHome" VALUE="/u01/app/oracle/Middleware/wlserver_10.3"/>
<Property NAME="DomainHome" VALUE="/u01/app/oracle/Middleware/user_projects/domains/soa_domain"/>
</Target>
</Targets>

More information on this issue on My Oracle Support.

eProseed has accomplished it's first go-live with 12c technology

We are pleased to announce that eProseed has accomplished its first go-live with 12c technology working with CFL - The Luxembourgish National Railway Company.

With this implementation, CFL accomplished a high-reliable, agile and flexible integration platform across various heterogeneous application - existent in and off-premises - empowering CFL monitoring and control capabilities in addition to a faster customer on-boarding.

eProseed team’s expertise enhanced the new SOA Suite 12c capabilities enabling to deliver a short time-to-market solution based in standards and best practices that lays a solid foundation for future coming projects.

This first phase is cornerstone of a broader IT transformational project where CFL wants to put in place a full SOA platform capable of handling all the communications between its internal applications and their partners.

The synergies between the SOA 12c components, namely B2B and OSB products, are key for building a solid and flexible integration layer to implement a variety of interfaces that enable CFL to communicate easily and efficiently with all of their partners.

Installation of Oracle B2B 12c

In this post I will quickly go through the steps that are necessary in order to install Oracle B2B and create a SOA domain that you can use.

I will consider that the installation will be used for a development environment and that it is done on the Linux machine.

Note that prior to the installation of B2B you will need to have machine running a Database and perform the installation of Oracle Fusion Middleware 12c Infrastructure and of the Oracle Fusion Middleware 12c SOA Suite and Business Process Management on the same machine where you will be installing B2B. You will also need to have the latest Oracle JDK 7 Update installed on that same machine.

The necessary software can be downloaded using Oracle eDelivery:

• V44959-01.zip – Latest Oracle JDK 7 Update for Linux x86-64 (Prerequisite)
• V44416-01.zip – Oracle Fusion Middleware 12c (12.1.3.0.0) Infrastructure (Prerequisite)
• V44420-01.zip – Oracle Fusion Middleware 12c (12.1.3.0.0) SOA Suite and Business Process Management (Prerequisite)
• V44421-01.zip – Oracle Fusion Middleware 12c (12.1.3.0.0) B2B and Healthcare

To install Oracle Fusion Middleware 12c Infrastructure please refer to:
Oracle Fusion Middleware Installing and Configuring the Oracle Fusion Middleware Infrastructure

To install Oracle Fusion Middleware 12c SOA Suite and Business Process Management please refer to:
Oracle Fusion Middleware Installing and Configuring Oracle SOA Suite and Business Process Management

I'm considering that a new domain will be configured from scratch. If a SOA domain was already created previously a few of the next steps can be ignored and the existing domain can be extend to include B2B. If that is the case, for the next steps, remember to shutdown any running instances of Weblogic Server.

     1. The first part of the installation will be to install the software:

After you have downloaded the V44421-01.zip file unzip it:

[oracle@linuxMachine stage]$ unzip V44421-01.zip

and you will obtain a file: fmw_12.1.3.0.0_b2bhealthcare.jar. Run this file:

[oracle@linuxMachine stage]$ java -jar fmw_12.1.3.0.0_b2bhealthcare.jar

and you will be presented with the Oracle Universal Installer. Follow the onscreen instructions:

     2. The second part of the installation is to run the Repository Creation Utility (RCU) to create the necessary schemas.

Note: If you have executed the RCU previously to create a SOA domain you can skip this step.

Navigate to ORACLE_HOME/oracle_common/bin 

and execute RCU:

[oracle@linuxMachine bin]$ ./rcu

Follow the onscreen instructions. 

A special note for the Custom Variables - Step 5 of 8 screen:

Since I'm installing a development environment I will chose a SMALL database profile. I also chose not to install the Healthcare on the software installation so I chose NO on the Custom Variables screen.

   3. The third part of the installation is to create and configure your domain.

Navigate to ORACLE_HOME/oracle_common/common/bin 
and execute the domain configuration application:

[oracle@linuxMachine bin]$ ./config.sh

Follow the onscreen instructions. 

Note: if you already have a SOA domain created you can follow the similar steps by selecting to Update an existing domain and adding Oracle B2B - 12.1.3.0 [soa] on the second screen of the configuration wizard.

Note: If you are extending the domain and you have custom data sources that were created before the extension, a new screen will show up before this screen. Check the Datasources row and click Next. The test data source screen will verify its validity. Click Next.

After these 3 steps your SOA Domain will now be configured and enabled for B2B. Start your Admin and SOA servers and navigate to: http://<server_ip>:<soa_server_port>/b2bconsole and you're all set to start using B2B!

Additional information can be found at: Oracle Fusion Middleware Installing and Configuring Oracle B2B and Healthcare