Deploying Fusion Order Demo on 11.1.1.6 by Antony Reynolds

Description of Figure 3-1 followsDo you need to build a demo for a customer? Why not to use Fusion Order Demo (FOD) and modify it to do some extra things. Great idea, let me install it on one of my Linux servers I said "Turns out there are a few gotchas, so here is how I installed it on a Linux server with JDeveloper on my Windows desktop."

Task 1: Install Oracle JDeveloper Studio

I already had JDeveloper 11.1.1.6 with SOA extensions installed so this was easy.

Task 2: Install the Fusion Order Demo Application

First thing to do is to obtain the latest version of the demo from OTN, I obtained the R1 PS5 release.
Gotcha #1 – my winzip wouldn’t unzip the file, I had to use 7-Zip.

Task 3: Install Oracle SOA Suite

On the domain modify the setDomainEnv script by adding “-Djps.app.credential.overwrite.allowed=true” to JAVA_PROPERTIES and restarting the Admin Server. Also set the JAVA_HOME variable and add Ant to the path.

I created a domain with separate SOA and BAM servers and also set up the Node Manager to make it easier to stop and start components. Read the full blog post by Antony.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit  www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum

Comments:

I am following the Oracle Fusion Order Demo from http://docs.oracle.com/cd/E12839_01/integration.1111/e10275.pdf

I have made all the deployments and reached page 30 of http://docs.oracle.com/cd/E12839_01/integration.1111/e10275.pdf

http://hostname:port/StoreFrontModule/faces/home.jspx to run the store front module for placing two orders in the store

I am unable to get demo page.

I get the error

Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

I have disabled the windows fire wall. My SOA version is 11.1.1.7.0

The application is active. and deployments are proper. the log files does not show any exception at all.
Kindly help me...!

--
Lammeki Andrew Diengdoh

Posted by Lammeki Andrew Diengdoh on August 28, 2013 at 01:13 PM CEST #

Post a Comment:
  • HTML Syntax: NOT allowed
About





Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
15
20
21
22
23
24
25
26
27
28
29
30
   
       
Today