Start Oracle Enterprise Manager 10g Application Server Control from a command window, if it is not already running, with the following command:

emctl start iasconsole

Open your browser and enter the following URL: http://<hostname>.<domain>:1810/. Note: The administration port number is automatically assigned at installation time and may be different for your installation. When prompted for user name and password, enter ias_admin and the password that you entered at installation time, such as welcome1.

On the Application Server Control Console's Home page, view the System Components table.
Start the HTTP Server and the home OC4J components if they are not already running.
Do this by selecting the check box next to each component and then clicking the Start button on the components table (on the left corner).
Then select OC4J home link from the list to navigate to the OC4J home component page.

The OC4J home component page comes up with the Home page link that provides status and performance information for this OC4J component. Use the Applications property page link to view and manage the J2EE applications that have been deployed to the container and information on their usage and performance. On the Administration property page, you can manage the OC4J configuration. To define data sources, click the Administration property page.

On the Administration property page, under Application Defaults, click Data Sources to manage the container-level data sources.

On the Data Sources page, click Create to create a container-level data source.

On the Create Data Source page, enter (or copy and paste) these values in the following fields (other fields should remain blank).
Tip: To create additional data sources in the future, you can use the Create Like option to avoid retyping all the data.

	Name: HRDS
	Data Source Class: com.evermind.sql.DriverManagerDataSource
	JDBC URL: jdbc:oracle:thin:@localhost:listening port:sid Note: You may need to replace localhost with the host name or the IP address of the server where the Oracle database software is installed and running. You must also replace the listening port and the Sid with actual values.
	JDBC Driver: oracle.jdbc.driver.OracleDriver
	Username: hr
	Password: hr
	Location: jdbc/hrCoreDS
	Transactional (XA) Location: jdbc/xa/hrXADS
	EJB Location: jdbc/hrDS (This is the Data Source you specified for the entity beans on deploying the application.)
	Connection Retry Interval (seconds): 1
	Cached Connection Inactivity Timeout (seconds): 30

Scroll down to the bottom of the page and click Create to create the data source.

The Confirmation page indicates that the data source has been created. You are prompted to restart the home OC4J server before the changes can take effect. Click Yes.

The following page is displayed and updated while the OC4J home instance is restarted. Wait until you get confirmation that the OC4J instance has started.

On the Confirmation page indicating that the OC4J home instance be restarted, click OK.

The new data source HRDS should appear in the Data Sources list.

The HR application contains two container managed persistence entity beans (based on Departments and Employees tables in the HR demo schema) using EJB 2.0 abstract schema and local interfaces; the source files of the entity beans are located in \<wkdir>\j2ee\hrejb\hr. You can examine the code to see how the beans are implemented. The entity beans also use Container Managed Relationships and EJB query language. Examine the EJB deployment descriptors (ejb-jar.xml and orion-ejb-jar.xml located in \<wkdir>\j2ee\hrejb\META-INF) to see how the relationships are defined and how the Finder method uses the EJB query language.

The HR application uses OracleJSP EJB tags in Java Server Pages to access the entity beans. You can examine departments.jsp and employees.jsp in the \<wkdir>\j2ee\hrweb directory to see how the EJB tags work.

The application also contains two Servlet Filters: the LogFilter keeps track of the requested URLs and the TimerFilter times the execution of requests; the two filters are chained. You can examine the source files in the \<wkdir>\j2ee\hrweb\WEB-INF\classes\filter and the web deployment descriptor in the \<wkdir>\j2ee\hrweb\WEB-INF\web-xml directories to see how the filters are defined and chained together.

The application has already been built for you. You should be able to find the EAR file in \<wkdir>\j2ee\build (hrapp.ear).

On the Data Sources page, click the OC4J: home link to go back to the Home page of the OC4J home component.

Click the Applications property page link to display the applications for the home instance. Click the Deploy EAR file button to launch the Deploy Application Wizard.

The Deploy Application Wizard in Application Server Control will guide you through the steps required to deploy an application. On the Deploy Application page, click Browse..., to select the hrapp.ear from the \<wkdir>\j2ee\build directory as the EAR file to deploy. Enter hrapp as the application name. Click Continue.

On the Deploy Application: URL Mapping for Web Modules page, check whether /hrapp is specified as the URL Mapping for the application. Click Next.

On the Deploy Application: Resource Reference Mappings page, you see jdbc/hrDS in the Data Source field for the Employees and Departments Entity Bean, respectively. You already defined the jdbc/hrDS data source. Click Next.

Oracle Application Server 10g provides a Java Authentication and Authorization Service (JAAS) user provider that can be used for J2EE application security management. The default user manager service, in Oracle Application Server 10g, is also known as JAZN. On the Deploy Application: User Manager page, accept the default setting Use JAZN XML User Manager. Click Next.

On the Deploy Application: Review page, check the deployment information summary, that is, the EAR File to Deploy, Deployment Destination, and URLs Mapped to Application. Note that the application does not contain any Web Services modules, and notice the TIP on the review page indicating that the HTTP server will be restarted after deployment to pick up the new URL mappings. Click Deploy to deploy the application.

During deployment, the Application Server Control Console may display a page tracking the deployment process. Wait until you get the Confirmation page. When the Confirmation page is displayed, click OK.

After the application has been deployed, Application Server Control brings you back to the Applications property page of the OC4J home instance. Note that the hrapp appears in the Deployed Applications list. Click the hrapp link to access that application's page.

On the Application: hrapp page, you see the component modules of the application. Click the EJB Module hrejb link.

You can now click Departments to see the EJB itself.

The EJB information is now displayed.

Note: When the application is not accessed, there is no load displayed in the performance metrics. When the application is accessed, the data on the page is refreshed and you can monitor the application's performance by using the Application Server Control.

Enter the following URL to run the HR application from the browser:
http://<hostname>.<domain>:<HTTP-PORT>/hrapp/. You should be able to see the application main welcome page. Click Departments. Note: The HTTP Server port is automatically assigned at installation time and may be different for your installation.

A list containing all the departments in the HR database that you configured as the hrapp data source is displayed. Note that this invokes departments.jsp. Select a department such as Human Resources.

A list of Employees in the department selected is displayed. Click Back twice to return to the HR application main menu.

Click Employees.

You see a list of all employees in the HR database. Then, click Back to return to the HR application main menu.

You can also search for employees by name. Click Search.

Enter John as the first name and click Search.

You see a list containing all the employees whose first name is John.

Create a Data Source

Deploy the HR J2EE Application

Run the HR Application

To learn more about Oracle Application Server Containers for J2EE (OC4J), refer to the additional information on the OTN Web site.