Expand the WebServiceOBE node in the Applications Navigator and select Project.

Choose File > Rename, and in the Rename dialog, change the file name from Project.jpr to FindWebService.jpr and click Save.

In the Connections Navigator, expand the UDDI Registry folder. JDeveloper comes with connections to three public UDDI registries.

Select the IBM Public UDDI v2 Registry, right-click and choose Find Web Services from the context menu to launch the Find Web Services wizard.

Click Next on the Welcome page to begin.

In the Search Kind page, make sure that Name is selected and click Next to display the Search Criteria page.

You can search by category, but when you are just trying out the UDDI browser, it can be easier to get a result if you search by name.

In the Search Criteria page, you specify the criteria to use in searching for tModels. A tModel is a technical specification that enables a client to determine if the Web service complies with a particular behavior or programming interface.

In Search For, enter a search string such as ab% (% is a wild card). Click Next. This searches the UDDI registry for tModels that start with the letters "ab".

If you get an error at this stage, make sure that you have a connection to the Internet and that JDeveloper's proxy settings are correct. For more information, refer to Step 7 of Prerequisites.

The tModels that fit the search criteria are displayed. Those that use a WSDL have a tick in the Is WSDL? column. Select one of the tModels that has a tick, and click Next to display the Service page. (You do not have to wait for all of the descriptions to load before selecting the one you want and clicking Next.) This example uses Above All Software Test Service.

The Service page of the wizard shows the services that implement the tModel you selected.
It is possible that you will get a message at this point, saying that no service implements the tModel you selected, in which case click Back and select another service. From the Service page, click Next to display the Finish page.

The wizard displays a report of the Web service you have found. Click Finish to display the Find Web Services wizard dialog.

Leave Generate stub code into project FindWebService.jpr to invoke this service selected, and click OK. The Web Service Stub/Skeleton wizard is launched.

If Generate stub code to invoke this service is not displayed on the final dialog, it means that although the UDDI browser has located a Web service that appears to meet your requirements, it has failed the validation that the Web Services Stub/Skeleton wizard performs. There are a number of reasons why this can happen.

The most obvious reason is that although the Web service is registered in the UDDI registry, there is no WSDL at the location specified. If this happens, click Cancel on the dialog, and use the Back button in the wizard to find another Web service.

Another reason could be that the proxy settings in the browser do not match the proxy settings in JDeveloper.

In the Generate Web Services Stub/Skeleton wizard, if the Welcome page is displayed, click Next to display the Select Web Service Description page.

The URL of the Web service description (the WSDL Document URL) is already entered. Do not change it. Leave Generate Client-Side Stubs selected, and select Generate Main Method into Stub. This will make it easy for you to test your stub. Click Next to display the Select Stubs/Skeletons to Generate page.

Click on the Web service (the second line in the pane identified by ). The Service Name is displayed, and defaults are shown for the Package and the Class Name for the generated stub. Accept the defaults, and click Finish.

The business providing the service is added to the Connections Navigator under the UDDI registry you used, and the stub to implement the service, which is called <service_name>Stub.java, is added to the Applications Navigator under the FindWebService project. Depending on the Web service you chose, JDeveloper may add other Java classes, which are JavaBeans to implement any complex types that it finds in the Web service.

In the Applications Navigator, double-click the stub <service_name>Stub.java to open it in the Code Editor, and scroll down until you find

// Add your own code here.

Immediately below that line, add some code that will return a value from the Web service. For example, look for a method in the stub that returns a String, then add the code:

System.out.println(stub.<methodname>());

Then right-click the Code Editor and choose Make to make the stub.

Note: Depending on the Web Service that you choose, you may receive a compilation error stating that the class UnknownType is not found. If you receive this error, add the following import statement to the stub and then recompile:

import com.sun.corba.se.interceptor.UnknownType;

Right-click the Code Editor again and choose Run to run the stub. The stub connects to the Web service, and returns a value which is displayed in the log window. If the Log Window is not visible, choose View > Log.

With the WebServicesOBE selected in the Application Navigator, right-click and choose New from the context menu to display the New Gallery.

In the Categories list, select General, and then in the Items list, select Empty Project, and click OK to open the Create Project dialog.

Change the name of the project from Project1 to ModelWebService and click OK. The new project is created and displayed in the navigator.

With the project ModelWebService selected in the navigator, right-click and choose New to open the New Gallery.

In the General category, select Diagrams, and then in the Items list, select Java Class Diagram. Click OK to open the Create Java Class Diagram dialog.

Accept the defaults, and click OK. An empty class diagram opens in JDeveloper.

The Component Palette, located in the right section of the JDeveloper window, enables you to select diagram elements for different palettes. If the Component Palette is not visible, choose View > Component Palette.

Have a look at the list to see the other palettes that are available. For this subtopic you will be using the Java palette, so ensure that it is the selected palette.

Click Java class in the Component Palette, then click on the class diagram. This creates a modeled Java class. Resize it so that it is comfortable to work with.

Click below the second line on the class, in the methods compartment, and type
+ getDate() : String

Examine the Java class that has been created. If necessary in the navigator, expand ModelWebService, then Application Sources, then mypackage1 and double-click JavaClass1.java. This opens the Java class in the Code Editor. You can also open the code editor by double-clicking on the class in the class diagram.

Edit the class so that the method is:

public static String getDate()
{
return (new java.util.Date()).toString();
}

Return to the class diagram by clicking the Java Class Diagram1 tab above the Code Editor. Right-click the modeled class and choose Generate > Web Service from the context menu to fast create a Web service from it.

The new modeled Web service is displayed on the diagram, and the Web service container MyJavaClass1WS is displayed in the Application Navigator.

On the diagram, right-click the modeled Web service and choose Run Embedded Server from the context menu.
Alternatively, in the navigator, right-click MyJavaClass1WS and choose Run from the context menu.

The Web service is deployed to JDeveloper's embedded OC4J server and the progress is recorded in the log window.

In the navigator, right-click the Web service container, MyJavaClass1WS to invoke the context menu. Alternatively, you can right-click the Web service in the class diagram to invoke the context menu.

Select Generate Sample Java Client from the context menu .This creates EmbeddedMyJavaClass1WSStub.java which is listed in the navigator. The Java class opens in the Code Editor.

Scroll down until you find:
// Add your own code here.

Immediately below that line, add:
System.out.println("The date and time is " + stub.getDate());

Right-click in the Code Editor and choose Make to make the class.

Right-click again and choose Run to run the class. The log window shows the current date and time which has been returned from the Web service.

If the log window shows an error at this point it is probably because the stub is not able to connect to the Web service running in the embedded OC4J server. This can happen if you are running DHCP.

Go to Tools > Preferences and select Web Browser/Proxy to see the current settings. The list of proxy server exceptions includes 127.0.0.1 and localhost. However, if you look at the stub you have just generated, at the line starting "private String _endpoint", the actual IP address of your machine is used. The port is 8988, the port for the embedded OC4J server.

To get the stub to work, you can do one of the following:

Add your machine's IP address to the list of proxy server exceptions. Go to Tools > Preferences and select Web Browser/Proxy. Add your IP address to the end of Exceptions.

or

Turn off the proxy server in the dialog, but remember to turn it back on again for the next topic.

 

To create a new project, right-click the WebServiceOBE workspace in the navigator and choose New Project to open the New Gallery with Projects selected in the Categories list.

Choose Empty Project from the Items list and click OK.

In the Create Project dialog, change Project1 to PLSQLWebService and click OK.

To create the package in the database, with PLSQLWebService selected in the Application Navigator, right-click and choose New to open the New Gallery.

In the Categories list, expand Database Tier and select Database Files, then select SQL File in the Items list. Click OK.

In the Create SQL File dialog, change the File Name to wsobe.sql and click OK. The new empty file opens in the code editor.

REM
REM Create object EMP_REC
REM

CREATE or REPLACE type EMP_REC as object
(
employee_id number(6),
last_name varchar2(25),
job_id varchar2(10),
manager_id number(6),
hire_date date,
salary number(8,2),
commission_pct number(2,2),
department_id number(4)
);
/
show errors;

REM
REM EMP_FETCHER package spec
REM

CREATE or REPLACE package EMP_FETCHER as
FUNCTION get_emp(emp_no IN NUMBER) RETURN emp_rec;
END;
/
show errors;

REM
REM EMP_FETCHER package body
REM

CREATE or REPLACE package body EMP_FETCHER as
FUNCTION get_emp(emp_no IN NUMBER) RETURN emp_rec IS
emp_found employees%rowtype;
emp_rtn emp_rec;
BEGIN
SELECT *
INTO emp_found
FROM employees
WHERE employees.employee_id=emp_no;

emp_rtn := emp_rec
(
emp_found.employee_id,
emp_found.last_name,
emp_found.job_id,
emp_found.manager_id,
emp_found.hire_date,
emp_found.salary,
emp_found.commission_pct,
emp_found.department_id
);

RETURN emp_rtn;
END;

END;
/
show errors;

Click the Save button to save the SQL file.

Right-click wsobe.sql in the navigator, and choose Run in SQL*Plus > HRconn. (This assumes that you have already defined a database connection to the HR or HR8 user, as described in Prerequisites. The example uses HRconn for the name of that connection, but if you have used a different name, just select the connection that you defined.) Running this SQL file against the Human Resources schema in the database creates an object type called EMP_REC and a package called EMP_FETCHER.

If this is the first time you have run a file in SQL*Plus from JDeveloper, a dialog is displayed for you to enter the path to the SQL*Plus Executable. In the SQL*Plus Executable dialog, enter the path or browse to the location of the SQL*Plus executable on your machine.

When you click OK, or if you have already defined the path to the SQL*Plus executable, an Oracle SQL*Plus window opens, and the script is run. You should see the following messages:

Type created.
No errors.
Package created.
No errors.
Package body created.
No errors.

Type exit to close the SQL*Plus window.

In the Connections Navigator, expand the Database node. Expand the connection HRconn, then HR or HR8, then Packages to find the new package, EMP_FETCHER. It is this that you will use to create the Web service.

In the Connections Navigator, expand the HRconn node, then the HR or HR8 node, then the Packages node. Right-click the EMP_FETCHER package and choose Publish as Web Service to launch the Create PL/SQL Web Service wizard.

If the Welcome page is displayed, review the information and click Next to open the Database Connection and Package page.

Ensure that the Target Project is WebServiceOBE.jws/PLSQLWebService.jpr.

You cannot change the database connection and database package because you started the wizard from a specific database package. If you launched the wizard by selecting a project and choosing the wizard from the New Gallery, you would be able to select the database connection and the package, but you would not be able to change the project.

Accept the defaults, and click Next to open the Program Units to Publish page.

Select the FUNCTION GET_EMP(IN NUMBER) RETURN EMP_REC program unit, then click Next to open the Endpoint page.

Accept the defaults, and click Next and then Finish.

JDeveloper connects to the database and creates the Web service. This may take a few seconds.

The generated Web service is listed in the Application Navigator, and the WSDL document is opened in JDeveloper's XML Editor.

JDeveloper uses JPublisher to translate from PL/SQL to Java, a process which generates several files such as Java classes and beans to act as a Java wrapper to the PL/SQL. The files that are generated are displayed in the Structure Pane when you select the Web service in the Application Navigator.

In the Applications Navigator, right-click the WebServices.deploy file and choose Deploy to and select WSConnection. If WSConnection is not shown, see steps 4 and 5 of Prerequisites.

The Web service is deployed to the external instance of OC4J and the progress is recorded in the log window.

With the project PLSQLWebService selected in the Applications Navigator, choose New to open the New Gallery.

In the Categories list, expand Business Tier and choose Web Services. In the Items list, select Web Service Stub/Skeleton and click OK to launch the Web Service Stub/Skeleton wizard.

If the Welcome page is displayed, click Next to display the Select Web Service Description page.

From the list, select the URL of the Web service, <location>/MyWebService1.wsdl . Leave Generate Client-Side Stubs selected, and select Generate Main Method into Stub. Click Next to display the Select Stubs/Skeletons to Generate page.

Click Finish.

The new Java class, MyWebService1Stub.java is listed in the navigator and opened in the Code Editor. Scroll down until you find

// Add your own code here.

Immediately below that line, add:

EmpRecUser1 emp = stub.getEmp(new BigDecimal(111));
System.out.println("ID = "+ emp.getEmployeeId());
System.out.println("NAME = "+ emp.getLastName());
System.out.println("SALARY = "+ emp.getSalary());

Right-click the Code Editor and choose Make to make the stub. Then right-click again and choose Run to run the stub.

The stub connects to the Web service in the external server using the employee id 111 as a parameter, and returns information about the employee, which is displayed in the log window.

Display the TCP Packet Monitor window by choosing View > TCP Packet Monitor. The TCP Packet Monitor window opens. By default it is docked at the lower right of JDeveloper's user interface.

Start monitoring the packets by clicking .

Run one of the Web service stubs you have already created. In the navigator, right-click the stub and choose Run. The request/response packets are listed in the TCP Packet Monitor.

Note: If no message is shown in the TCP Packet Monitor, check the browser and proxy exception list and ensure that the local machine name is not listed.

To see the contents of a packet pair, select it in the History page, then click the Data tab.

Use the and buttons to examine other packet pairs.

When you are debugging a Web service, you can change the contents of a request packet and resend it so as to see the changes in the response packet. To try this, make the appropriate change to the request packet, and click .

The amended packet is sent and you can examine the response packet to see the change.

To stop the TCP Packet Monitor, click .

To close TCP Packet Monitor window, click the Close icon at the top right of the window.

Located an existing Web service on the Internet by finding a tModel in a public UDDI registry

Used the wizard to automatically generate a stub to the service that you found

Ran the stub that was generated by JDeveloper to test the implementation of the Web service

Modeled a Java class on a class diagram

Automatically generated a Web service from the modeled class

Ran the Web service on JDeveloper's embedded OC4J server

Created a simple Java client to test the Web service

Created a database connection from JDeveloper

Created a Web service directly from a package in the database

Deployed the Web service to an external instance of the OC4J server

Created a stub to the Web service and used it to test that the Web service returns the expected value

Used the TCP Packet Monitor to view the request/response packets sent while running the stub

Changed information in the request packet, resent the request, and examined the response packet to see the change