Using / Running / Setting JDeveloper 11.1.1.6 to use 64 bit and 32 bit JVM / JDK

Tired of memory issues while working with JDeveloper because you are running on 32 bit JVM. Switch you JDeveloper to point to 64 bit JVM.This will allow you to use multi Gig memory usage while working with JDeveloper IDE.

Prerequisites: 64 bit Machine, 64 bit OS and 64 bit Jdk Installation. JAVA_HOME should be set to appropriate 64 bit jdk installation directory for example 

JAVA_HOME = C:\Program Files\Java\jdk1.6.0_23
So your JAVA_HOME=C:\Program Files\Java\jdk1.6.0_23

JDeveloper's Settings:

1.  C:\Oracle\Middleware\jdeveloper\ide\bin\ide.conf

• AddVMOption  -Xmx4192M
• AddVMOption  -Xms512M 

Above setting will allows to user 4 GB of RAM.

 

 2. C:\Oracle\Middleware\jdeveloper\jdev\bin\jdev.conf

• Point JDeveloper to use 64 bit Java Version
•  SetJavaHome C:\Program Files\Java\jdk1.6.0_23
• AddVMOption  -XX:MaxPermSize=1024M

Namespace prefix "oraext" qualifying cannot be resolved while Designing BPEL processes in Oracle SOA Suite 11g

SOA Developers mainly encounters this issue while using Oracle Extension functions in the Assign or Transform activities.

This error occurs when namespace is not defined in your BPEL process. check two points here.
1. Is namespace : http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc is already defined in BPEL process or not ? if not, Define it as below.
xmlns:oraext="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"

2. If namespace is already defined in the BPEL process then you need verify the prefix value here.for example below is the entry found in BPEL process.
 xmlns:ns4="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"

here you need rename the prefix values "ns4" to "oraext".  OR

modify the function name prefix in Transformation with "ns4"

Generate Webservice / deploy / redeploy buttons not visible in Oracle E Business Suite (EBS)

Oracle E-Business Suite Integrated SOA Gateway (ISG) provides robust communication and Infrastructure for Integration with E-Business Suite (EBS) Applications. Oracle E-Business Suite Integrated SOA Gateway is build on top of Oracle Fusion Middleware & Service Oriented Architecture (SOA) technology.

As a Integration Architect / Designer you will require to route your integration requests through Integrated SOA gateway to EBS for more standardize Integratiion approch. Oracle provide all Integration Interfaces detail at common location that is Integration Repository. You can create web service for supported Interface types using Integration repository. However to generate web services for respective Interface type you have to have appropriate roles and responsibilities assigned to your user.

Integrated SOA Gateway implements Role Based Access Control security for secure access to Interfaces.There are 3 different roles to provide different access to Integrated SOA Gateway.

• Integration Repository Administrator
• System Integration Developer
• System Integration Analyst

Below table show each role and access to the features for respective roles. This roles have to be manually assigned to each user when required except for SYSADMIN.

This is most common issue while performing EBS Integration. You have to follow below steps for assigning appropriate role to the user and then user should be able see Generate WSDL button or SOA provider section is web services are already generated.

Option 1 :

user SYSADMIN user which is by default having appropriate roles assigned and you should be able to see Generate WSDL buttion.

Option 2:
Get the appropriate role assigned by requesting your system administrator. Below are the steps system Administrator need to follow to assign correct role for the user. So that user can have access to Generate WSDL / deploy / redeploy access.

1. Log into Oracle Applications using sysadmin/.
2. Select the User Management responsibility in the Navigator.
3. Click the Users link from the navigation menu to open the User Maintenance window.
4. Locate the user trying to use.
5. Assign the role and select the "Irep Administrator" role.
6. Bounce the middle tier because after assigning roles they don't take affect unless the cache is cleared and bounce middle tier.
7. Now log in as the user and access the " Integrated SOA Gateway" responsibility ->Integration Repository and should see the Generate WSDL button