Initialize and configure UDDI Registry by pinging the UDDI Inquiry servlet end point. Open a browser window and enter the following URL:

http://<hostname>:<domain>:<HTTP listen port>/uddi/inquiry
Note: The HTTP listen port is typically 80 for windows installation.

The OracleAS UDDI Registry page is displayed. You should see the message:
"Welcome! Your registry is now up and running."

Unzip the webservices.zip file into your working directory E:\wkdir.

Download and install Ant which is a program used to compile and run java applications. For this OBE, Ant version 1.6.2 is used.
Note: As suggested in the Ant install you should create an environment variable called ANT_HOME set it to the directory in which you installed Ant, and add the ANT_HOME\bin directory to your PATH.

Open a command prompt and issue the following commands:
Note: While executing the commands, you might have to change the folder names as per your installation folders.

set ANT_HOME=E:\apache-ant-1.6.2-bin\apache-ant-1.6.2
set PATH=%PATH%;%ANT_HOME%\bin

Set the environment variable called ORACLE_HOME to the directory in which you installed the database. Include ORACLE_HOME\bin in the PATH.

set ORACLE_HOME=E:\oracle\product\10.1.0\db_1
set PATH=%PATH%;%ORACLE_HOME%\bin

Make sure your database service is running. Connect to the scott schema and execute the script create.sql.

cd E:\wkdir\webservices\server\sql
sqlplus scott/tiger
@create

This will create the necessary objects you will need to run your plsql Web Service.

Add JAVA_HOME to your environment variables and set it to ORACLE_HOME\jdk. Include JAVA_HOME\bin in the PATH.

set JAVA_HOME=%ORACLE_HOME%\jdk
set PATH=%PATH%;%JAVA_HOME%\bin

Add J2EE_HOME to your environment variables and set it to <oracleas_portalhome>\j2ee\home.

set J2EE_HOME=E:\portal_home\j2ee\home

Note: Use the same command prompt throughout the OBE because all the environment variables are set.

server/ - web services server components

sql/ - SQL scripts for the PL/SQL web service

create.sql - main script (you will run this)

createt.sql - script creating tables

createp.sql - script creating package

createb.sql - script create package body

drop.sql   - drop everything created

insert.sql - inserts required data into the employees table

wsejb/ - HelloEJB for the EJB web service

META-INF/

- ejb-jar.xml - EJB deployment descriptor

HelloEJB.java  - HelloEJB remote interface

HelloEJBHome.java - HelloEJB home interface

HelloEJBBean.java - HelloEJB bean implementation

wsweb/ - Web Components

WEB-INF/

- classes/

     - Hello.java - stateless Java web service interface
     - HelloImpl.java - stateless Java web service implementation
     - Count.java - stateful Java web service interface
     - CountImpl.java - stateful Java web service implementation
     - CompanyInterface.java - PL/SQL web service interface

config.xml - config file used by the WebServices Assembler tool

build.xml - build file used by Ant for server components

client/ - web services client components

HelloClient.java - stateless java web service client

CountClient.java - stateful java web service client

EJBWSClient.java - EJB web service client

PLSQLClient.java - PLSQL web service client

build.xml - build file used by Ant for server components

common.xml - common setup file for Ant

Examine HelloEJB and find out how it is implemented.

Examine the classes located in E:\wkdir\webservices\server\wsweb\WEB-INF\classes and understand how they are implemented.

Examine E:\wkdir\webservices\server\config.xml and understand how it defines various types of Web Services (stateless java, stateful java, stateless session EJB and stateless PL/SQL stored procedure)

Database Setup: examine the SQL scripts located in E:\wkdir\webservices\server\sql. These scripts create database tables, package, types and procedures required by the PL/SQL web service. The database objects have already been created for you in the scott/tiger schema.

The Web Services application has already been built for you. You should be able to find the EAR file in E:\wkdir\webservices\server\build (wsapp.ear).

If you need to recompile, run the ant tool from E:\wkdir\webservices\server to build the Web Services application. Ant will perform the following:

	Build the EJB Module
		Compile the Hello EJB classes
		Package the EJB Jar file
	Build the JAR file for PL/SQL web service
		Use JPublisher to generate Java and SQLJ files representing the database packages, types and procedures
		Use SQLJ Precompiler to translate generated SQLJ files to Java
		Compile all generated java classes
		Package java classes into a JAR file (representing the PL/SQL package)
	Compile the java classes for stateless and stateful java Web Services (interfaces and implementations)
	Call the WebServicesAssembler tool to build the web module, generate the web.xml descriptor that defines servlet entry points for different types of Web Services. Package everything into an EAR file

Use a compression tool (e.g. winzip) to examine the content of the generated wsapp.ear file. Take a close look at the wsapp_web.war\WEB-INF\web.xml file generated by WebServicesAssembler, understand how it defines the servlet entry points for the following types of Web Services and identify the components that implement each type of Web Service.

	Stateless java class
	Stateful java class
	Stateless session EJB
	Stateless PL/SQL stored procedure

Open your browser and enter the following URL: http://<hostname>.<domainname>:1810/.
Note: The administration port number is automatically assigned during installation of Oracle AS 10g and may be different for your installation. When prompted for user name and password, enter ias_admin and the password you specified when installing the application server, for example welcome1.

You will see the OracleAS Farm page that lists the application server instances on your machine. Click on the link for the portal instance to go to Portal Home page.

When prompted for user name and password, enter ias_admin and the password you specified when installing the application server.

You will see the Enterprise Manager 10g Application Server Control Console for Portal.

In the System Components table click the OC4J_Portal link.

The Home page is the initial administration page for the portal OC4J instance, and provides status and performance information. The Applications page provides a list of applications that have been deployed to the container and information on their usage and performance. The Administration page provides links to view and modify configuration information.

Click the Administration tab.

Click UDDI Registry under Related Links.

OracleAS UDDI Registry supports the following standard taxonomies for classifying tModels, businessEntities, and businessServices:

• North American Industry Classification System (NAICS)
  This is a classification system for each industry and corresponding code.
• United Nations Standard Products and Services Codes (UNSPSC)
  This is the first coding system to classify both products and services for use
  throughout the global marketplace.
• ISO 3166 Geographic Taxonomy
  This a list of all countries and their subdivisions.

Click North American Industry Classification System (NAICS).

NAICS taxonomy in turn has many categories. These categories and the respective codes are listed in a table. You can click on the category names to view the sub-categories. To see the Web Services published under a particular category you must select the category and click View Services. In this OBE, you will publish the Web Services to Wholesale Trade category.

Click OC4J: OC4J_Portal in the breadcrumbs to return to the portal OC4J home.

2.

To add or modify a data source click the Administration tab.

In the Administration tab page, scroll down and click Data Sources.

In the Data Sources page, select the OracleDS radio button and click Edit.

Click Yes on the confirmation page to restart the OC4J server.

A progress page displays while the portal OC4J is being restarted, followed by a confirmation page when the home OC4J instance has been restarted. In the confirmation page click OK.

You are returned to the data source page. Click the OC4J: OC4J_Portal link in the breadcrumbs to go to the OC4J instance configuration page.

Go to the Applications page.

Click Deploy EAR File to launch the deployment wizard, which will guide you through the steps required to deploy an application.

In the Deploy Application page, click Browse..., to select the wsapp.ear from the E:\wkdir\webservices\server\build directory as the EAR file to deploy. Enter wsapp as the application name. Click Continue.

In the Deploy Application: URL Mapping for Web Modules page, check that /wsapp is specified as the URL Mapping for the application. Click Next.

In the Deploy Application: Resource Reference Mappings page, enter jdbc/OracleDS as the JNDI Location, this maps the jdbc/wsDS data source (used by the PL/SQL Web Service) to the jdbc/OracleDS defined in a previous step. Click Next.

Oracle Application Server 10g provides a JAAS user provider that can be used for J2EE application security management. This is the default Oracle Application Server 10g user manager service, also known as JAZN. In the Deploy Application: User Manager page, accept the default setting Use JAZN XML User Manager. Click Next.

You will see that the application has three Web Services. However, none of the Web Services are published yet. Select the first Web Service and click Publish.

In the Service Details section enter the Name as count, Code as 42(this is the code for the Wholesale category under NAICS Classification). In the TModel Details section enter the Name as Count and Code as 42. Click OK.

You can see that the Web Service is published. Similarly, publish the next two Web Services.

After publishing all the Web Services, click Next.

In the Deploy Application: Review page, check the deployment information summary (source/target, resource mappings, etc.). Also note that the application contains three Web Services modules. Click Deploy to deploy the application to Oracle Application Server 10g.

The Processing: Deploy page is displayed.

Click OK in the confirmation page.

After clicking OK in the confirmation page the Applications page of the OC4J instance is displayed. You should see wsapp in the list of Deployed Applications.

Select wsapp from the list of deployed applications.

In the Application: wsapp page select the wsapp_web entry from the list of Web Modules.

Scroll down to look at the Servlets/JSPs section. Click Mapping under Properties.

In the Mappings page you see the Servlet URL mappings for each of the Web services. Click Back button of the browser to return to Application: wsapp page.

Click Environment under Properties to examine the Data Source JNDI mapping you defined upon deployment.

Click Back button of the browser to return to Application: wsapp page.

Click Advanced Properties to see how the data source is mapped in the orion-web.xml file.

Click OC4J: OC4J_Portal in the breadcrumbs to return to the OC4J Home page.

Click Administration to go to Administration page.

Click UDDI Registry under Related Links to browse UDDI Registry.

Recollect that you have published the Web Services to Wholesale Trade category of NAICS taxonomy. Click North American Industry Classification System (NAICS).

5.

You can see all the categories under NAICS classification. Select Wholesale Trade Category and click View Services.

All the Web Services that you registered to this category are shown.

Click count Web Service.

You see the details that you specified while publishing the Web Service to UDDI.

Open a browser and enter the following URL to run the Web Services application from the browser: http://<hostname>:80/wsapp/. This page was generated by the Web Services Assembler. You should be able to see four different types of Web Services: Stateless Java, Stateful Java, Stateless session EJB, Stateless PL/SQL procedure.

Click on stateless Java web service - /wsapp/helloService to go to the stateless Java Web Service page.

Optionally you can click on the Service Description link to view the WSDL file for the Web Service. Examine the XML elements of the WSDL document.

Click sayHello to test run the stateless Java web service.

Enter any string in the Value field and click Invoke.

You should be able to see the result SOAP message returned by the stateless Java Web Service. Close this window when done.

Click Back button of the browser to return to the helloService Web Service Home page.

Right click Proxy Jar and select Save Target As… to download the proxy jar file generated by OC4J. Save it to E:\wkdir\webservices\client directory as helloService.jar (make sure you change the file extension to .jar). You will need this jar file to build a standalone Web Service client application.

Go back to the Web Services Home page and click stateful Java web service - /wsapp/countService.

Click count to test run the stateful webservice.

Click Invoke.

A new window is displayed containing the SOAP result returned by the web service.

Reload (or refresh) the page. You should be able to see the counter increase, as highlighted every time you reload the page. Close the window when done.

Save the generated Proxy Jar as countService.jar in the E:\wkdir\webservices\client directory.

Click Back button of the browser to return to the Web Services Home page. Click on stateless session bean web service. The EJB Web Service is very similar to the stateless Java web service except it is implemented using a stateless session bean. Save the generated Proxy Jar as ejbService.jar in the E:\wkdir\webservices\client directory. Since the steps are same, these steps are not included in the OBE.

Return to the Web Services Home page and click stateless PLSQL web service - /wsapp/plsqlService.

Click getemp in the Company Web Service Home page.

Enter 1234 in the Value field (employee id) and click Invoke.

You should be able to see the result SOAP message representing a row in the EMPLOYEES table returned by the PLSQL Web Service. Close the window when done.

Save the generated Proxy Jar as plsqlService.jar in the E:\wkdir\webservices\client directory.

Now you will build standalone Java applications to access the deployed Web Services. Make sure the E:\wkdir\webservices\client directory contains the following Web Services stub files (saved from the Proxy Jar links):

	helloService.jar
	countService.jar
	ejbService.jar
	plsqlService.jar

Take a look at how these proxy classes are implemented. Examine the client applications located in E:\wkdir\webservices\client and see how they access the Web Services by calling the proxy classes.

Open a command prompt window and execute the following commands:

d:
cd E:\wkdir\webservices\client
ant

You can run all the client applications all at once:

ant RunAll

Or run them individually:

ant RunStateless
ant RunStateful
ant RunEJB
ant RunPLSQL

Browse the UDDI Registry

Deploy the Web Services application to Application Server 10g and Publish Web Services to OracleAS UDDI Registry

Test the deployed Web Services application