Today, I attended a workshop at Oracle to get a first glimp of the SOA Suite 10.1.3.1. We used the “Developer Preview” of JDeveloper 10.1.3.1 to develop a few simple Web Services. The software is not yet available on Oracle Technet, but it will be…soon….
The installation of Oracle SOA Suite is very simple, run the installer and click “next”, “next”, “next”, … “finish”. By default, it installs an Oracle Lite database to store the metadata together with an Oracle Application Server 10.1.3.1. which provides a number of applications:
- Oracle Web Services Manager
- Oracle Business Rules Author
- Oracle Enterprise Service Bus
- Oracle BPEL Process Manager Controll
- Oracle Application Server Controll
One nice thing is that the Oracle Application Server is configured for Single Sign-On and it uses jazn-data.xml. This limits the amount of memory needed for the installation because you don’t need to install Oracle Internet Directory! For those of you who want to simulate the production environment, Oracle Application Server Controll enables you to change the security provider to Oracle Identity Manager, a 3rd Party LDAP Server (with standard support for Active Directory and Sun Directory Server) or use a custom JAAS security class to integrate with other LDAP Servers.
Now lets focus on what we tested tested today.
We used the JDeveloper wizards to generate and deploy a Web Service based on a Java class, and a Web Service based on a PL/SQL Stored Procedure. Nothing exciting because we already saw that working in previous JDeveloper releases.
We used Oracle Application Server Controll (formerly known as Enterprise Manager) to test the generated Web Services. No need to learn the URL’s to the deployed Web Service by heart, just navigate to the “Test Service” link and fill in the HTML form that’s generated by OracleAS. There’s even a possibility to stress test the service by entering the number of simultaneous threads, number of loops and the delay in ms.
The more demanding developers can:
- configure Web Service Auditing
- configure port level reliability features to guaranty response delivery and eliminate duplicate requests
- enable authentication mechanisms like username/password, certificate or SAML authentication
- sign SOAP messages to ensure integrity
- encrypt the SOAP message to ensure confidentiality
really nice stuff, and we didn’t use the Oracle Web Services Manager yet!!
Off course, in real life, not all Web Services are deployed to an Oracle Application Server. That’s where Oracle Web Services Manager comes into the picture.
But I’ll come back on that tomorrow….