Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

Exclusive offer: get 50% off this eBook here
Getting Started With Oracle SOA Suite 11g R1 – A Hands-On Tutorial

Getting Started With Oracle SOA Suite 11g R1 – A Hands-On Tutorial — Save 50%

Fast track your SOA adoption – Build a service-oriented composite application in just hours with this Oracle SOA book and eBook!

$35.99    $18.00
by Heidi Buelow Manas Deb Jayaram Kasi Demed L'Her Prasen Palvankar | October 2009 | Oracle

Read Part One of Installation and Configuration of Oracle SOA Suite 11g R1 here.

Additional actions

In the following section, you will be performing additional configuration that is optional but will greatly improve performance and usability in the context of the development work you are about to start.

Setting memory limits

Review the memory settings. This value is dependent on your machine resources and may need to be adjusted for your machine. Allocating less memory for startup will give you better performance on a machine with less memory available. This value is appropriate for a 3 GB memory machine or less.

  1. Edit the SOA domain environment file found here (make sure you have the SOA Domain environment file):
    C:OracleMiddlewarehome_11gR1user_projectsdomains domain1
    binsetSOADomainEnv.cmd
  2. Set memory values:
    set DEFAULT_MEM_ARGS=-Xms512m -Xmx512m

Starting and stopping

Now it's time to start your servers. You can start them using the provided script or you can start them separately. Instructions for both methods are included.

Starting

First set boot.properties and then start the servers.

  1. Before you start, set the boot properties so you are not prompted to log in during server startup. Copy C:pobinboot.properties to C:OracleMiddlewarehome_11gR1user_projectsdomainsdomain1.
  2. Edit the copied file to reflect the password for your configuration (entered during domain configuration). The first time the server is started this file is encrypted and copied to the server locations.
    You can start the servers one at a time or you can use the start_all script to start the admin and SOA managed servers (not BAM). To start them one at a time instead, skip to step 6.
  3. Copy the startup script to the Oracle directory:
    C:pobinstart_all.cmd to
    C:OracleMiddleware
  4. Edit the copied file to reflect your environment.
  5. Open a command window and start your servers as shown. You must specify how many seconds to wait after starting the admin server before starting the managed server. The admin server must be in the RUNNING state before the managed server starts (see the following screenshot). Try 180 seconds and adjust as necessary. You will need more time the first time you start after a machine reboot than for subsequent restarts:
    cd C:OracleMiddleware
    start_all.cmd 180

    Your servers are now starting automatically so you can skip steps 6-10. Jump to step 12 to continue.

    To start the servers manually, continue with the following steps.

  6. Open three command windows, one for the WebLogic admin server, one for the SOA managed server, and one for the BAM managed server (only start BAM when you need it for a BAM lab).
  7. Start the Admin Server first:
    cd C:OracleMiddlewarehome_11gR1user_projectsdomainsdomain1
    startWebLogic.cmd
  8. Wait for the Admin Server to finish starting up. It takes a few minutes—watch for status RUNNING in the log console window:

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  9. Start the SOA managed server in the second command window. This start script is in the bin directory. You can also run it directly from the bin directory:
    cd C:OracleMiddlewarehome_11gR1user_projectsdomainsdomain1
    binstartManagedWebLogic.cmd soa_server1
  10. When prompted, enter the username weblogic and password welcome1. If you did step 1 and set boot.properties, you will not be prompted. The server is started when you see the message, INFO: FabricProviderServlet.stateChanged SOA Platform is running and accepting requests.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  11. Start the BAM managed server in the third command window—do this only when needed for the BAM lab:
    cd C:OracleMiddlewarehome_11gR1user_projectsdomainsdomain1
    binstartManagedWebLogic.cmd bam_server1
  12. When prompted, enter the user name weblogic and password welcome1. If you did step 1 and set boot.properties, you will not be prompted. Watch for the RUNNING status.

Console URLs

Log in with weblogic/welcome1 for all consoles:

  • Weblogic console: http://localhost:7001/console
  • Enterprise Manager console: http://localhost:7001/em
  • SOA worklist: http://localhost:8001/integration/worklistapp
  • B2B console: http://localhost:8001/b2b
  • BAM (must use IE browser): http://localhost:9001/OracleBAM

Stopping servers

Whenever you need to stop the servers complete the following:

  1. Stop the managed servers first by entering Ctrl+C in the command window. Wait until stopped.
  2. Stop the admin server by entering Ctrl+C in the command window.

WebLogic Server console settings

There are two suggested changes to make in the WebLogic Server console.

First, you will be viewing application deployments often using the WebLogic server console. This is a lot more convenient if you change the settings not to show libraries as this makes the list a lot shorter and you can find what you need more quickly.

  1. Start the WebLogic Admin Server (WLS) if it is not already running.
  2. Log in to the WLS console http://localhost:7001/console.
  3. Click on Deployments in the left navigation bar.
  4. Click on Customize this table at the top of the Deployments table.
  5. Change the number of rows per page to 100 (there are only about 30).
  6. Select the checkbox to exclude libraries and click on Apply.

Second, when the server is started, internal applications like the WLS console are not deployed completely and you see a slight delay when you first access the console. You saw this delay just now when you first accessed the console URL. You can change this behavior to deploy internal applications at startup instead and then you don't get the delay when you access the console. This is convenient for demos (if you want to show the console) and also if you tend to use the console each time you start up the server.

  1. Click on domain1 in the left navigation bar in the WLS console.
  2. Click on Configuration | General tab.
  3. Deselect Enable on-demand deployment of internal applications checkbox.
  4. Click on the Save button.

EM settings for development

The Enterprise Manager can provide different levels of information about composite runtime instances based on a property setting. During development, it is helpful to have a higher setting. These settings are not used on production machines except when specifically needed for debugging purposes as there is a performance cost.

  1. Start your servers if they are not already running.
  2. Log in to the EM console at http://localhost:7001/em.
  3. Right-click on the soa-infra (soa_server1) in the left navigation bar to open the SOA menu and select SOA Administration | Common Properties.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  4. Select Audit Level: Development and select the checkbox for Capture Composite Instance State.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  5. Click on Apply and click on Yes.

If you need to uninstall JDeveloper and servers

If you need to uninstall everything, complete the following:

  1. First save anything from C:OracleMiddlewarejdev_11gR1jdevelopermywork that you want to keep as this directory will be deleted.
  2. Run Uninstall from the program menu to completion for both JDeveloper and WLS.
  3. Delete C:OracleMiddlewarejdev_11gR1 and C:OracleMiddlewarehome_11gR1. If you get an error message about not being able to delete because a name or path is too long, change the names of the composite directories within home_ 11gR1user_projectsdomainsdomain1deployed-composites to abcd and try deleting again.
  4. Delete program groups from C:Documents and SettingsAll UsersStart MenuPrograms:
    • Oracle Fusion Middleware 11.1.1.1.0
    • Oracle SOA 11g - Home1
    • Oracle WebLogic
  5. Complete the Dropping existing schema section earlier in this article to clean up the database.
Getting Started With Oracle SOA Suite 11g R1 – A Hands-On Tutorial Fast track your SOA adoption – Build a service-oriented composite application in just hours with this Oracle SOA book and eBook!
Published: October 2009
eBook Price: $35.99
Book Price: $59.99
See more
Select your format and quantity:

Configuration

This section provides the instructions for creating database and JMS resources that are required by the tutorial. Start your database and WebLogic admin servers and complete the following configuration steps.

Installing the database schema

First, create a table in the database owned by the soademo user:

  1. Make sure your database is running.
  2. Create the soademo user using the following script. It is OK to run this script even if the soademo user already exists. From a command line, cd to the c:posql directory and run the following replacing pw with your own system user's password:
    cd c:posql
    sqlplus system/pw @create_soademo_user.sql
  3. Now, create the credit card info table. It is OK to run this script again even if the table already exists. Make sure that you run it with the soademo user for proper ownership:
    cd c:posql
    sqlplus soademo/soademo @create_creditrating_table.sql

Creating the JMS resources

Next you must create a JMS resource. You create this by using the WebLogic Server console. First you create the JMS queue and connection factory and then a connection pool for that connection factory.

  1. Make sure thatyour server has started using the instructions above. If it is not already open, open http://localhost:7001/console to start the Web Logic Server (WLS) console and log in using weblogic/welcome1. Replace the host and port and username/password to match your own configuration if necessary.

First add the JMS Queue:

  1. In the WLS console, on the left navigation bar, expand Services | Messaging and click on JMS Modules.
  2. Click on SOAJMSModule (click on the name, not the checkbox).

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  3. In the Summary of Resources table, click on New.
  4. Select the resource type: Queue and click on Next.
  5. Enter Name as demoFulfillmentQueue and JNDI Name as jms/demoFulfillmentQueue.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  6. Click on Next.
  7. From the Subdeployments list, select SOASubDeployment.
  8. From the JMS Servers list, select SOAJMSServer.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  9. Click on Finish.

Now add the Connection Factory.

  1. In the Summary of Resources table, click on New.
  2. Select the resource type: Connection Factory and click on Next.
  3. Enter Name as demoCF and JNDI name as jms/demoCF.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  4. Click on Next.
  5. Click on Finish.

You should see both the queue and the connection factory listed in the Summary of Resources as shown here:

Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

Now add the connection pool. The connection pool is configured in the JMSAdapter application and uses a Deployment Plan. First, create a directory to contain that plan.

  1. Create a directory here: C:OracleMiddlewarehome_11gR1Oracle_SOA1soaJMSPlan (adjust the path according to your installation).
  2. In the left navigation bar of the WLS console, click on Deployments.
  3. Click on JMSAdapter (click on the name, not the checkbox).
  4. Click the Configuration tab and then the Outbound Connection Pools tab.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  5. Click on New.
  6. Select the oracle.tip.adapter.jms.IJmsConnectionFactory factory.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  7. Click on Next.
  8. Enter eis/Queue/demo.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  9. Click on Finish.
  10. At this point, you are asked for the deployment plan location. Click on the path to the directory you created earlier and enter Plan.xml for the plan name.

    If you are not asked for the plan location at this time, it means you already have a plan for the JMS adapter from an existing configuration. That plan file will be used for this configuration. You can skip ahead to the next step to hook up the connection factory.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  11. Click on OK.
  12. Verify the plan name is set to Plan.xml in the JMSPlan directory.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

Go back to the new connection pool to hook up the connection factory:

  1. Click on the Configuration tab.
  2. Expand the group: oracle.tip.adapter.jms.IJmsConnectionFactory.
  3. Click on eis/Queue/demo.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  4. To change a property value you must enter the value and then press the Enter key and then click on the Save button. Do not use the Tab key after entering the value. Follow these instructions exactly:
    1. Select the cell on the far right for the property ConnectionFactoryLocation.
    2. An edit box appears. Type in the value jms/demoCF and press the Enter key.
    3. You must use the Enter key for the value to be entered in the field.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  5. Click on Save. You must use the Save button to save the value.
  6. Now the adapter must be redeployed. Click on Deployments in the left navigation bar.
  7. Select the checkbox next to JMSAdapter.
  8. Click on Update at the top of the Deployment table.
  9. Verify that the correct deployment plan is selected.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  10. Click on Next.
  11. Click on Finish.

Creating the database resource

The tutorial application requires a database data source. You create this using the WebLogic Server console. First you create the data source and then you create a connection pool for that data source.

  1. Make sure that your admin server is started using the instructions provided earlier. If it is not already open, open http://localhost:7001/console to open the Web Logic Server (WLS) console and log in using weblogic/welcome1. Replace the host and port and username/password to match your own configuration.
  2. On the left navigation bar, click on Services | JDBC | Data Sources.
  3. In the data source table, click on New.
  4. Enter the data source information:
    • Name: soademoDatabase
    • JNDI Name: jdbc/soademoDatabase
    • Database Type: Oracle
    • The Database driver defaults to the correct driver: Oracle's Driver (Thin XA) for Instance connections
  5. Click on Next, click on Next again.
  6. Enter the database information:
    • Database Name: XE (your database SID)
    • Host name: localhost (host where your database is running)
    • Port: 1521 (set according to your configuration)
    • Database user name: soademo (created in previous section)
    • Database user password: soademo

      Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  7. Click on Next.
  8. lick on Test Configuration. Confirm success message at the top of the page.
  9. Click on Next.
  10. Select the Target server where your SOA component is running: soa_server1.
  11. Click on Finish.

Now create the connection pool. You have to edit the database adapter application and it uses a Deployment Plan. First, create a directory to contain that plan.

  1. Create a directory here: C:OracleMiddlewarehome_11gR1Oracle_SOA1soaDBPlan (adjust the path according to your installation).
  2. In the left navigation bar, click on Deployments.
  3. Click on the DbAdapter application (click on the name, not the checkbox).
  4. Click on the Configuration tab, and then click on the Outbound Connection Pools tab.
  5. Click on New.
  6. Select the radio button for javax.resource.cci.ConnectionFactory and click on Next.
  7. .Enter the JNDI Name as: eis/DB/soademoDatabase.
  8. This is not the same value as in the previous step. It matches the value you enter in your database connection you create later when building your application using JDeveloper. Click on Finish.
  9. At this point, you are asked for the deployment plan location. Click on the path to the directory you created earlier and enter the deployment plan name Plan.xml.

    If you are not asked for the plan location at this time, it means you already have a plan for the DB adapter from an existing configuration. That plan file will be used for this configuration. You can skip ahead to the next step to hook up the connection factory.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  10. Click on OK.
  11. Confirm the name of the deployment plan.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  12. Now, edit the connection pool to reference the data source. Click on the Configuration tab, expand the connection factory and click on your new connection pool, eis/DB/soademoDatabase (click on the name, not the checkbox).
  13. To change a property value you must enter the value and then press the Enter key and then click on the Save button. Do not use the Tab key after entering the value. Follow these instructions exactly:
    1. In the Properties table, select the box to the far right of xADataSource.
    2. The edit box appears. Type in your data source name that you created above: jdbc/soademoDatabase.
    3. Press the Enter key to apply the value. You must use the Enter key for the value to be entered in the field.
  14. Select Save. You must use the Save button to save the value.
  15. Go back to the main Deployments page to update the DbAdapter as follows. Click on Deployments in the left navigation bar.
  16. Select the checkbox next to DbAdapter.
  17. Click on Update.
  18. Select Redeploy this application and confirm the deployment plan location.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  19. Click on Finish.
  20. Confirm that the connection pool is added by going back to the DbAdapter | Configuration | Outbound Connection Pools and expanding the connection factory listed there.
  21. Confirm the value of the xADataSource property that you entered previously. It should be jdbc/soademoDatabase. Look closely! This is the most common place where the configuration is in error.
  22. Go back to the JMSAdapter Outbound Connection Pools tab and review the connection factory property value for the eis/Queue/demo connection pool that you entered previously. It should be jms/demoCF. Look closely! This is the most common place where the configuration is in error.

When the two resources are added and confirmed, you are ready to start building the SOA composites. Continue with the next step to test your installation.

Testing your installation

This section shows you how to verify your installation and configuration.

After installing SOA Suite and JDeveloper, confirm that you have the correct 11.1.1.1.0 version.

You have three things to check:

  1. JDeveloper: Start J Developer and select from the toolbar, Help | About. You should see this build: JDEVADF_11.1.1.1.0_GENERIC_090615.0017.5407.
  2. SOA Composite Editor: Select the Version tab on the JDeveloper Help | About dialog. You should see this value: 11.1.1.0.0.52.19. It is OK that this includes 11.1.1.0.0 instead of 11.1.1.1.0.
  3. SOA Server: Run soaversion.cmd from C:OracleMiddlewarehome_11gR1Oracle_SOA1bin and you should see this build: PCBPEL_11.1.1.1.0_GENERIC_090618.1440.5219.

Now verify the database table you created for the credit card information. This table was created in the Configuration section earlier.

  1. Use SQLPlus to show the table. Be sure to connect using the soademo user.
    sqlplus soademo/soademo
    select * from creditcardinfo;

    Next, verify your database and JMS resources. These resources were created in the Configuration section earlier.

  2. In the WLS console, on the left navigation bar, expand Services | JDBC | Data Sources. It is OK if you have a newer version that matches the version from the Update Center.
  3. Confirm that you see the resource soademoDatabase.
  4. On the left navigation bar, expand Services | Messaging and click on JMS Modules.
  5. Click on SOAJMSModule (click on the name, not the checkbox).
  6. In the Summary of Resources, confirm you see the queue and the connection factory, demoFulfillmentQueue and demoCF.
  7. Confirm that the database connection pool is added by going to Deployments in the left navigation bar and clicking on DbAdapter | Configuration | Outbound Connection Pools and expanding the eis/DB/soademoDatabase connection factory listed there.
  8. Confirm the value of the xADataSource property that you entered previously. It should be jdbc/soademoDatabase.
  9. From DeploymentsJMSAdapter, then click the Outbound Connection Pools tab and review the connection factory property value for the eis/Queue/demo connection pool. It should be jms/demoCF.

Oracle Service Bus installation

The following steps are to be followed to install the Oracle Service Bus (OSB).

  1. Go to http://www.oracle.com/technology/products/integration/service-bus/index.html and download osb1031_wls103_win32.exe.
  2. Execute the program osb1031_wls103_win32.exe to start the installer.
  3. On the Welcome screen, click on Next.
  4. Select Create a new BEA Home.
  5. Enter the location where you would like to install the product.

    Make sure you do not specify the Middleware home of the SOA Suite Install. OSB will run on a different WebLogic domain than SOA Suite.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  6. Click on Next.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  7. Choose Custom and click on Next.
  8. There are two components unchecked, namely Server Examples and Service Bus Examples. Scroll down and check the Service Bus Examples. The lab requires the Service Bus Example server to be installed.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  9. Click on Next.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  10. Accept the default selections for the JDK and click on Next.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  11. Accept the default to Install Eclipse and click on Next.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  12. Accept the default directories for the installation and click on Next.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  13. Accept the default to skip the Windows Service installation and click on Next.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  14. Choose All Users to give all accounts access to the product shortcuts, then click on Next.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  15. The Installation Summary page is displayed. Click on Next. Installation begins.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  16. When installation is complete, uncheck Run Quickstart and click on Done.

Testing your OSB installation

Now verify that the installation was successful. You use the Example Server created during installation. This example server is the only server in an OSB Weblogic domain and serves the function of both an admin server and an OSB managed server.

  1. Launch the Oracle Service Bus Examples Server using the start menu that was created when you installed the product.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  2. The OSB web application automatically loads and displays a page similar to the one shown here. Load the examples by clicking on the Load the Examples button.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  3. Test the example code by executing any one of the use scenarios shown on the page. If any one of them is successful, the system has passed the smoke test.

Removing samples (optional)

The lab uses the Examples Server but not the examples themselves. You can remove the examples if desired.

  1. If the OSB examples server is not running, start it up by selecting the Start Examples Server menu choice.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  2. Log in to theOSB web console using this URL: http://localhost:7021/sbconsole. The username/password is weblogic/weblogic.
  3. In the Change Center on the top left, click on the Create button to start a change session.
  4. Project Explorer.
  5. Delete the Mortgage Broker project by clicking the trash can.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  6. Click on the Activate button to commit the OSB configuration change.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  7. Then click on the Submit button.

Uninstalling OSB

To uninstall the Oracle Service Bus, select Uninstall Oracle WebLogic from the start menu. Make sure that you are uninstalling WebLogic for OSB and not WebLogic for SOA Suite. Move your mouse over a file in the group menu to see the directories where the files are located to be sure you have the correct one.

Summary

At this point in time, you should have installed and configured all the software required to proceed ahead. We have tried to condense all installation steps in one single article so do not worry if you have lost track of what exactly you have installed! You now have a very extensive and capable set of tools at your disposal.

If you have read this article you may be interested to view :

Getting Started With Oracle SOA Suite 11g R1 – A Hands-On Tutorial Fast track your SOA adoption – Build a service-oriented composite application in just hours with this Oracle SOA book and eBook!
Published: October 2009
eBook Price: $35.99
Book Price: $59.99
See more
Select your format and quantity:

About the Author :


Heidi Buelow is a product manager with Oracle and is responsible for Oracle SOA Suite programs such as beta and technical previews. Heidi joined Oracle in 2006, after having spent the previous 10 years as Chief Application Architect with a startup developing a Business Process Management engine, developer toolset, and application framework. Heidi started her career as a software developer at Xerox, working on the Xerox Network Services and Star Workstation products where she first learned to appreciate object-oriented and services-oriented technologies. She holds a Bachelor of Science degree in Computer Science from the University of Southern California.

Manas Deb is a senior director in the Fusion Middleware/SOA, BPM, Governance Suites Product Group at Oracle HQ. He currently leads outbound product management and many strategic engagement initiatives for Oracle's SOA, BPM, and Governance solutions, worldwide. He is also responsible for Oracle/HQ-based SOA Methodology initiatives. Manas has worked in the software industry for over twenty years, most of which was spent in software product management/marketing and on architecting; he has also led a wide variety of enterprise-level application development and business integrations projects in a wide variety of industries. A graduate of The Indian Institute of Technology (KGP), Manas attended post-graduate studies at University of Texas at Austin. He received his PhD in an inter-disciplinary program comprising of Computer Science, Applied Mathematics, and Engineering. Manas also has an MBA with specialization in international business.

Jayaram Kasi is a product manager with Oracle, and focuses on SOA technologies. Before that, he had been a software architect for 20 years working on relational database kernels at HP, OLTP monitors based on DCE at HP, High Availability at HP, ECommerce Infrastructure at Commerce One, and Enterprise Service Bus at BEA. Jayaram has a Bachelor of Science degree in electrical engineering from the Indian Institute of Technology, and a Master of Science in electrical engineering from the University of Hawaii.

Demed L'Her is Director of Product Management at Oracle, where he is responsible for the Oracle SOA Suite. He has been with Oracle since 2006, focusing on ESB, JMS, and next-generation SOA platforms. Before joining Oracle, Demed spent eight years with TIBCO Software, a pioneer in electronic trading, message-oriented middleware and enterprise integration. He has been involved in some of the largest messaging and integration projects around the world, from trading floors in Tokyo to semiconductor manufacturing fabs in Arizona. Demed holds an Engineering Degree from the Ecole Nationale Supérieure des Télécommunications de Bretagne, a Bachelor of Science in Electrical Engineering from Université de Bretagne Occidentale and a Master of Science in Computer Science from Université de Rennes I.

Prasen Palvankar is a Director of Product Management at Oracle and is responsible for providing strategic support to Oracle's SOA Suite current and prospective customers. He is also responsible for outbound SOA Suite product related activities, including field and partner enablement and training. Prasen has over 20 years of experience in software development and has been working for Oracle since 1998. He was a Technical Director in the Advanced Technology Solutions group at Oracle Consulting, delivering large-scale integration projects before taking on his current role four years ago. Before joining Oracle, Prasen worked as a Principal Software Engineer at Digital Equipment Corporation.

Books From Packt

Oracle User Productivity Kit 3.5
Oracle User Productivity Kit 3.5

Oracle VM Manager 2.1.2
Oracle VM Manager 2.1.2

Oracle SQL Developer 2.1
Oracle SQL Developer 2.1

Oracle Application Express Forms Converter
Oracle Application Express Forms Converter

Processing XML documents with Oracle JDeveloper 11g
Processing XML documents with Oracle JDeveloper 11g

Oracle 10g/11g Data and Database Management Utilities
Oracle 10g/11g Data and Database Management Utilities

Oracle Application Express 3.2 – The Essentials and More
Oracle Application Express 3.2 – The Essentials and More

Middleware Management with Oracle Enterprise Manager Grid Control 10g R5
Middleware Management with Oracle Enterprise Manager Grid Control 10g R5

 

Your rating: None Average: 5 (1 vote)
Great by
you are the best!!!
Re: by Ramsai Karri
try https://www.packtpub.com/support for this book
what's this? by
C:pobinboot.properties
Hello GOD - Thanks a Lot by
Thanks a Lot...This is a divine help for me...:-) neeraj.oracle@gmail.com

Post new comment

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
z
X
G
r
7
k
Enter the code without spaces and pay attention to upper/lower case.
Code Download and Errata
Packt Anytime, Anywhere
Register Books
Print Upgrades
eBook Downloads
Video Support
Contact Us
Awards Voting Nominations Previous Winners
Judges Open Source CMS Hall Of Fame CMS Most Promising Open Source Project Open Source E-Commerce Applications Open Source JavaScript Library Open Source Graphics Software
Resources
Open Source CMS Hall Of Fame CMS Most Promising Open Source Project Open Source E-Commerce Applications Open Source JavaScript Library Open Source Graphics Software