Wednesday, November 28, 2012

Set up for OAF pages development

This post helps you in setting up the OAF page development environment.

Pre-Requisites to Setup OAF development environment
-------------------------------------------------------------------------------
1) download Jdeveloper OAF Patch for respective Oracle eBiz Instance.
2) download dbc files from unix server for respective Oracle eBiz Instance you are going to work with.

Detailed instructions
----------------------------------
1) Find your Oracle eBiz Version by logging into your apps -- Click About this page link at bottom of the page -- Click Technology components tab -- you will see the screen below



Note down your OA Framework version. In my case it is 12.1.3.

So i need to download the Jdeveloper OAF patch for this version(12.1.3) in the below link.
How to find the correct version of JDeveloper to use with eBusiness Suite 11i or Release 12.x (Doc ID 416708.1)

you will find the table like below shown



click the respective patch and download it.

Extract the downloaded .zip file into any location.
C:\p7523554_R12_GENERIC

you will find 3 folders. (jdevbin, jdevdoc, jdevhome)

Set the JDEV_USER_HOME environment variable
----------------------------------------------------
Right click my computer -> Properties -> Advanced Tab -> Environment variables



Variable name : JDEV_USER_HOME
Variable value will be DRIVE_LOCATION:\PATCH_NAME\jdevhome\jdev


You have almost completed the setup.

Downloading dbc(database connectivity file) 
-----------------------------------------------
This file used to connect the Jdeveloper to your Oracle eBiz Instance.
This file will be available with your DBA's or $FND_SECURE top.

FTP the .dbc file to "C:\p7523554_R12_GENERIC\jdevhome\jdev\dbc_files\secure"

dbc file contains information like below


#DB Settings
#Mon May 02 18:26:56 IST 2012
GUEST_USER_PWD=GUEST/ORACLE
APPL_SERVER_ID=A1E590D05E00456FE04400000000000021673182782189486806263446144422
FND_JDBC_BUFFER_DECAY_INTERVAL=300
APPS_JDBC_DRIVER_TYPE=THIN
FND_JDBC_BUFFER_MIN=1
GWYUID=APPLSYSPUB/PUB
FND_JDBC_BUFFER_MAX=5
APPS_JDBC_URL=
FND_JDBC_STMT_CACHE_SIZE=100
TWO_TASK=POC12
JDBC\:oracle.jdbc.maxCachedBufferSize=358400
JDBC\:processEscapes=true
FND_MAX_JDBC_CONNECTIONS=500
FND_JDBC_USABLE_CHECK=false
FNDNAM=APPS
FND_JDBC_PLSQL_RESET=false
DB_PORT=1553
FND_JDBC_CONTEXT_CHECK=true
FND_JDBC_BUFFER_DECAY_SIZE=5


Now start your OAF page development.

Sunday, September 30, 2012

Terminologies We Should Know

As a Oracle apps Technical Consultant, These terminologies are often used by everyone.
Listing the terminologies over here

MIDDLEWARE:
Software provides services beyond those provided by OS.
It is integral modern information technology based on XML,SOAP,Web Services and SOA.
Middleware sits "in the middle" between application software . Middleware enables interoperability between applications that run on different OS.
example : EAI

EAI : Enterprise Application Integration
SCM, CRM, BI and other type of applications cannot communicate with one another in order to shared data or business rules.EAI is the process of linking such applications within single organization together in order to simplify and automate business process.
for 'N' application
N*(N-1)
------    connections are required.
  2   

EDI: Electronic Data Interchange
Structured transmission of data between organizations by electronic means. It is used to transfer electronic documents or business data from one computer system to another computer system, i.e. from one trading partner to another trading partner without human intervention.

TIBCO:
People tell TIBCO is a Software/Company name/Middleware. Which one is correct?
Everything is correct.They are leading provider of business integration solutions delivering infrastructure software that enables to seamlessly integrate business systems in real time.
They call the technology as "Information Bus" or TIB middleware.

SOAP: Simple Object Access Protocol
A better way to communicate in internet is using HTTP becoz HTTP is supported by all browsers and servers.SOAP provides a way to communicate between applications running on different operating systems, with different technologies and programming languages in distributed systems.

SOAP Message Structure
A SOAP message is an ordinary XML document containing the following elements
<?xml version="1.0"?>
<soap:Envelope
xmlns:soap="http://www.w3.org/2001/12/soap-envelope"
soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding">

<soap:Header>
...
</soap:Header>

<soap:Body>
...
  <soap:Fault>
  ...
  </soap:Fault>
</soap:Body>

</soap:Envelope>

Yet to update this post.