4 Using Oracle JDeveloper to Generate an Oracle Enterprise Scheduling Service Application

4.2.1.1 How to Create the EssDemoApp Application and Host Project

To work with Oracle Enterprise Scheduling Service, you first create an application in Oracle JDeveloper. You'll also create a hosting application to support job execution.

To create the EssDemoApp application and hosting project:

1. Start Oracle JDeveloper as described in Section 4.1.

2. In the Select Role dialog, select the Default Role, then click OK.

3. Click the Application menu, then click New.

4. In the Name your application window enter the name and location for the new application.

   1. In the Application Name field, enter an application name. For this sample application, enter EssDemoApp.

   2. In the Directory field, accept the default.

   3. Enter an application package prefix or accept the default, no prefix.

      The prefix, followed by a period, applies to objects created in the initial project of an application.

   4. In the Application Template area, select Generic Application.

   5. Click Next.

5. In the Name your project window, enter the name for the host project you're creating and select supporting technologies.

   1. In the Project Name field, enter a name for your hosting project. For this sample application, enter EssHost.

   2. On the Project Technologies tab, under Available, double-click ESS Host Support and ESS Job Support so that they are both listed under Selected on the right side of the dialog box.

   3. Click Next.

6. In the Configure Java settings window, in the Default Package field, enter oracle.esshost.

   Click Next.

7. In the Configure EJB settings window, select the following:

   • Under EJB Version, select the Enterprise JavaBeans 3.0 option button.

   • Under EJB Version 3.0, select the Generate ejb-jar.xml in this project check box.

   Click Next.

8. In the Configure ESS Host Support settings window, in the Application Id field, enter EssDemoApp.

   Click Finish.

   This displays the EssDemoApp Overview page. You can use sections of this page to get information about aspects of the application you're creating, as well as to manage its development progress. For now, though, you'll move on to creating project artifacts to support creating jobs.

4.2.1.2 How to Create the Client Project

In the preceding step, you created a project in which to develop the application to host your jobs. In this section, you'll use Oracle JDeveloper to create another project in the EssDemoApp application. This second project will provide support for client interaction with the hosting application.

To create the client project:

1. Click the File menu, then click New.

2. In the New Gallery, under Categories, expand General, then click Projects.

3. Under Items, click Generic Project, then click OK.

4. In the Name your project window, enter the name for the client project you're creating and select supporting technologies.

   1. In the Project Name field, enter a name for your client project. For this sample application, enter EssClient.

   2. On the Project Technologies tab, under Available, double-click the following items so that they are listed under Selected on the right side of the dialog box:

      • ESS Client Support

      • HTML

      • JSF

      • JSP and Servlets

      • XML

   3. Click Next.

5. In the Configure Java settings window, in the Default Package field, enter oracle.essclient.

   Click Next.

6. In the Configure EJB settings window, select the following:

   • Under EJB Version, select the Enterprise JavaBeans 3.0 option button.

   Click Next.

7. In the Configure ESS Client Support settings window, in the Application Id field, ensure the EssDemoApp is displayed there.

   Click Finish.

4.2.2.1 How to Create Metadata for the EssDemoApp Application

In this section, you use Oracle JDeveloper to create job definition metadata and a simple implementation class for a Java job.

To create metadata for the application:

1. In the Application Navigator, select the EssHost project.

2. Press Ctrl-N. This displays the New Gallery.

3. In the New Gallery, select the All Technologies tab.

4. In the Categories area expand Business Tier and select Enterprise Scheduler Metadata.

5. In the Items area, select Job Definition as shown in Figure 4-1.

   Figure 4-1 Adding Job Type Metadata to the Sample Application

   
   

6. Click OK. This displays the Create Job Definition dialog.

7. In the Create Job Definition dialog, specify the following:

   1. In the Name field, enter a name for the job definition. For this example, enter the name: HelloWorldJobDefinition.

   2. In the Package field, enter a package name. For this example, enter /oracle/esshost/metadata.

      Note that you should use slashes, rather than dots, to delimit names in metadata package names. A metadata package ending in ".metadata" will not be visible in Oracle JDeveloper.

   3. In the Job Type field, from the dropdown list select /oracle/as/ess/core/JavaJobType.

      If job types are not listed in the dropdown, ensure that you started Oracle JDeveloper as described in Section 4.1.

   4. Ensure that the Create Java Class check box and the Synchronous option button are selected.

      By selecting the Create Java Class check box, you're asking that a Java class for your Java job be created, saving you the trouble of creating one later. Selecting the Synchronous option specifies that this will be a synchronous Java job.

   5. Under Java Class, specify details for the Java class you're creating. In the Java Package field, enter its package name -- here, enter oracle.esshost.impl. In the Class Name field, enter a name for the class -- here, enter HelloWorldImpl as shown in Figure 4-2

      Figure 4-2 Creating a Job Definition with the Job Definition Creation Wizard

      
      

   6. Click OK.

      This creates the Java class you requested, along with the HelloWorldJobDefinition.xml file. Oracle JDeveloper displays XML file's contents in the Job Definition page.

      On the Job Definition page, you can edit job definition metadata, including properties that specify parameters for the job, access to this metadata, and a resource bundle to use for localization.

8. In the Job Definition page, in the Description field enter a description for the job type. For this example enter: Sample Java Job Definition.

   Leave the rest of the metadata unchanged.

9. In the Application Navigator, locate the class you created by expanding the items in the projects panel to EssHost > Application Sources > oracle.esshost.impl > HelloWorldImpl.java.

10. Open HelloWorldImpl.java in the source editor.

11. In the source editor, add simple code to implement the execute method. The execute method is where execution for a Java job begins. Your HelloWorldImpl class should look something like Example 4-1.

    Example 4-1 HelloWorldImpl with Execute Method Implemented

    public class HelloWorldImpl implements Executable, Cancellable
    {
      public void execute(RequestExecutionContext ctx, RequestParameters params)
        throws ExecutionErrorException, ExecutionWarningException,
               ExecutionCancelledException, ExecutionPausedException
      {
          System.out.println("**** Sample Job Running, Request ID: " +
              ctx.getRequestId());
      }
     
      public void cancel()
      {
      }
    }
    

12. Save and close HelloWorldImpl.java.

4.2.3.1 How to Add Application Code to Submit Job Requests

In this section, you'll create a servlet for receiving job submission requests.

To add a servlet to support job request submissions:

1. In the Application Navigator, select the EssClient project.

2. Press Ctrl-N. This displays the New Gallery.

3. In the New Gallery, in the Categories area, expand Web Tier and select Servlets.

4. In the Items area, select HTTP Servlet as shown in Figure 4-3.

   Figure 4-3 Adding Job Type Metadata to the Sample Application

   
   

5. Click OK. This displays the Create HTTP Servlet wizard.

6. In the Welcome page, click Next.

7. In the Create HTTP Servlet - Step 1 of 3: Servlet Information page, specify the following:

   1. In the Class field, enter a name for the servlet class. For this example, enter the name: EssDemo.

   2. In the Package field, enter a package name. For this example, enter oracle.essclient.servlet.

   3. In the Generate Content Type field, from the dropdown list ensure the HTML is selected.

   4. In the Implement Methods area, select the doGet() and doPost() check boxes, as shown in Figure 4-4.

      Figure 4-4 Creating a Servlet -- Step 1 of 3

      
      

   5. Click Next.

8. In the Create HTTP Servlet - Step 2 of 3: Mapping Information page, specify the following:

   1. In the Name field, enter a name for the servlet. For this example, enter the name: EssDemo.

   2. In the URL Pattern field, enter a URL for servlet mapping. For this example, enter /essdemo/*.

   3. Click Finish.

   The supplied EssDemo application includes the completed servlet. You need to copy the source code into your project. To do this, in Oracle JDeveloper replace the contents of the servlet with the contents of the file EssDemo.java supplied with the sample application.

4.2.4.1 How to Set Oracle Enterprise Scheduling Service Properties for the Application

In this section, you'll set default values for Oracle Enterprise Scheduling Service properties.

To set values for Oracle Enterprise Scheduling Service properties:

1. In the Application Navigator, right-click the EssHost project, then click Enterprise Scheduler Properties.

2. In the Enterprise Scheduler Properties dialog, enter EssDemoApp for all three of the fields provided: Logical Application Name, Application Policy Stripe, and JPS Interceptor Application Name.

3. Click OK.

4.2.5.1 How to Create the EJB-JAR Deployment Profile for the EssDemoApp

The sample application needs to contain the required EJB descriptors. You need to create the ejb-jar.xml and weblogic-ejb-jar.xml files and include these files with any Java implementation class that you create.

Oracle Enterprise Scheduling Service requires an application to assemble and provide an EJB JAR so that Oracle Enterprise Scheduling Service can find its entry point in the application while running job requests on behalf of the application. This EJB jar should have its required EJB descriptors in ejb-jar.xml and weblogic-ejb-jar, as well as any Java class implementations that are going to be submitted to Oracle Enterprise Scheduling Service. The descriptor files ejb-jar.xml and weblogic-ejb-jar must contain descriptions for the Oracle Enterprise Scheduling Service EJBs and should not be modified.

To create the EJB-JAR deployment profile:

1. In the Application Navigator, in the Projects panel, right-click the EssHost project, then click Project Properties.

2. In the Project Properties window, in the navigator, click Deployment.

3. Under Deployment Profiles, delete all profiles listed in the window, then click New.

4. In the Create Deployment Profile dialog, from the Archive Type dropdown, select EJB JAR file.

5. In the Name field, enter a name for the EJB. For this example, enter ess-ejb.

6. Click OK.

7. In the Edit EJB JAR Deployment Profile Properties dialog, in the navigator on the left, click General.

8. In the General window, in the Enterprise Application Name field, enter EssDemoApp.

9. In the navigator, expand to File Groups > Project Output > Contributors.

10. In the Contributors window, select the following check boxes:

    • Project Output Directory

    • Project Source Path

    • Project Additional Classpath

    • Project Dependencies

11. In the navigator, expand to File Groups > Project Output > Filters.

12. In the Filters window, on the Files tab, ensure that the following folders are selected:

    • META-INF (and its contents)

    • oracle (and its contents)

13. Click OK.

14. In the Project Properties dialog, click OK.

4.2.5.2 How To Update the WAR Archive Options

In this section, you specify information that Oracle JDeveloper can use to generate a WAR file.

To update the WAR archive options:

1. In the Application Navigator, in the Projects panel, right-click the EssClient project, then click Project Properties.

2. In the Project Properties window, in the navigator, click Deployment.

3. In the Deployment window, click New.

4. In the Create Deployment Profile dialog, from the Archive Type dropdown, select WAR file.

5. In the Name field enter WAR_EssDemoApp.

6. Click OK.

7. In the Edit WAR Deployment Profile Properties dialog, in the navigator on the left, click General.

8. In the General window, select the Specify Java EE Web Context Root option. In the field beneath the option, enter EssDemo.

9. In the navigator, expand to File Groups > Web Files > Contributors.

10. In the Contributors window, select the following check boxes:

    • Project Output Directory

    • Project HTML Root Directory

    • Project Source Path

11. In the navigator, expand to File Groups > Web Files > Filters.

12. In the Filters window, on the Files tab, ensure that the following folders are selected:

    • oracle (and its contents)

    • WEB-INF (and its contents)

    Click OK.

13. In the Project Properties dialog, click OK.

4.2.5.3 How to Update the EAR Options

In this section, you'll prepare an EAR file that assembles the EssDemoApp sample application. The EAR archive consists of the following:

• EJB JAR including the Oracle Enterprise Scheduling Service Java job implementation.

• WAR archive with the EssDemo servlet.

To update the EAR options:

1. Click the Application menu, then click Application Properties.

2. In the Application Properties dialog, in the navigation pane, click Deployment.

3. In the Deployment window, click New.

4. In the Create Deployment Profile dialog, in the Name field, enter EAR_EssDemoApp as the deployment profile's name.

   Click OK.

5. In the Edit EAR Deployment Profile Properties dialog, in the navigation pane on the left, click Application Assembly.

6. In the Application Assembly window, under Java EE Modules, ensure that all item check boxes are selected.

7. Click OK.

8. In the Application Properties dialog, click OK.

4.2.6.1 How to Deploy the EssDemoApp Application

To deploy the EssDemoApp application you need a properly configured and running Oracle WebLogic Server, and you need an active metadata server. When you deploy the application Oracle JDeveloper brings up the Deployment Configuration page. Select your repository from the dropdown list and Enter a partition name (the partition name defaults to application name).

To deploy the EssDemoApp application:

1. Check the Run Manager to make sure the Oracle WebLogic Server is up and running. If the Oracle WebLogic Server is not running, start the server. To start the server, from the Run menu click Start Server Instance.

2. In the Application Navigator, select the EssDemoApp application.

3. In the Application Navigator from the Application Menu select Deploy > EAR_EssDemoApp > to > IntegratedWLSConnection.

4. Oracle JDeveloper shows the Deployment Configuration page. Select the appropriate options for your Metadata Repository.

5. Click Deploy.

6. Verify the deployment using the Deployment Log.

4.2.6.2 How to Run the EssDemoApp Sample Application

To run the EssDemoApp sample application you access the EssDemo servlet in a browser.

To access the EssDemo servlet:

1. Enter the following URL in a browser:

   http://host:http-port/context-root/essdemo

   For example,

   http://myserver.us.oracle.com:7101/EssDemoApp/essdemo
   

   This shows the EssDemo servlet, as shown in Figure 4-5.

   Figure 4-5 Running EssDemo Servlet for Oracle Enterprise Scheduling Service Sample Application

   
   

2. Select a job definition from the Job drop-down menu.

3. Select a value from the Schedule drop-down menu.

4. Click Submit.

5. Refresh the browser to see the progress of the job in the Request Status area, as shown in Figure 4-6.

   Figure 4-6 Running EssDemo Servlet with Request Status for Submitted Requests

   
   

4.2.6.3 How to Purge Jobs in the EssDemoApp Sample Application

Using the EssDemoApp sample application and the EssDemo servlet you can remove completed jobs from the Request Status list.

To remove completed jobs:

1. Click Purge to purge a request.

2. Click Cancel to cancel a request that is either RUNNING or WAITING.

4.3.1.1 Creating the Back-End Hosting Application

To work with Oracle Enterprise Scheduling Service with a split application you use Oracle JDeveloper to create the back-end application and project, and to add Oracle Enterprise Scheduling Service extensions to the project.

To create the back-end hosting application:

1. From JDeveloper choose File > New from the main menu.

2. In the New Gallery, expand General, select Applications and then Generic Application, and click OK.

3. In the Name your application page of the Create Generic Application wizard, set the Application Name field to EssDemoApp.

4. Click Next.

5. In the Name your project window, enter the name for the host project you're creating and select supporting technologies. This project is where you will create and save the Oracle Enterprise Scheduling Service metadata

   1. In the Project Name field, enter a name for your hosting project. For this sample application, enter SuperEss.

   2. On the Project Technologies tab, under Available, double-click ESS Host Support and ESS Job Support so that both are listed under Selected on the right side of the dialog box.

   Click Next.

6. In the Configure Java Settings page, change the default package to oracle.apss.ess.howto, then click Next.

7. In the Configure EJB Settings page, select Generate ejb-jar.xml in this project and click Next.

8. In the Configure ESS Host Support settings page, in the Application Id field, enter EssDemoApp.

9. Click Finish.

4.3.1.2 Configuring Security for the Back-End Hosting Application

You need to create a user that is assigned to the EssDempAppRole role.

To configure security for the back-end hosting application:

1. Select Application > Secure > Configure ADF Security from the main menu.

2. In the ADF Security page of the Configure ADF Security wizard, select ADF Authentication, then click Next.

3. In the Authentication Type page, accept the default values as this application will not have a web module to secure.

4. Click Finish.

   A file named jps-config.xml is generated. You can find this file in the Application Resources panel by expanding Descriptors, and expanding META-INF. This file contains a security context or security stripe named after the application.

5. Select Application > Secure > Users from the main menu.

   A file named jazn-data.xml is generated.

6. In the overview editor for the jazn-data.xml file, click the Add icon in the Users list.

7. Set the name to EssDemoAppUser and set the password to welcome1.

8. Click the Application Roles navigation tab.

9. Click the Add icon in the Roles list and choose Add New Role.

10. Set the name to EssDemoAppRole.

11. Click the Add icon in the Mappings tab and choose Add User.

12. Select EssDemoAppUser and click OK.

4.3.1.3 Defining Metadata for the Back-End Hosting Application

To use the Oracle Enterprise Scheduling Service split application to submit a job request you need to create metadata that defines a job request, including the following:

• A job type: this specifies an execution type and defines a common set of parameters for a job request.

• A job definition: this is the basic unit of work that defines a job request in Oracle Enterprise Scheduling Service.

To create metadata for the back-end hosting application:

1. In the Application Navigator, select the SuperEss project.

2. Press Ctrl-N. This displays the New Gallery.

3. In the New Gallery, select the All Technologies tab.

4. In the Categories area expand Business Tier and select Enterprise Scheduler Metadata.

5. In the Items area, select Job Definition as shown in Figure 4-7.

   Figure 4-7 Adding Job Type Metadata to the Sample Application

   
   

6. Click OK. This displays the Create Job Definition dialog.

7. In the Create Job Definition dialog, specify the following:

   1. In the Name field, enter a name for the job definition. For this example, enter the name: HelloWorldJobDef.

   2. In the Package field, enter a package name. For this example, enter oracle/apps/ess/howto/metadata.

   3. In the Job Type field, from the dropdown list select /oracle/as/ess/core/JavaJobType.

      If job types are not listed in the dropdown, ensure that you started Oracle JDeveloper as described in Section 4.1.

   4. Ensure that the Create Java Class check box and the Synchronous option button are selected.

      By selecting the Create Java Class check box, you're asking that a Java class for your Java job be created, saving you the trouble of creating one later. Selecting the Synchronous option specifies that this will be a synchronous Java job.

   5. Under Java Class, specify defails for the Java class you're creating. In the Java Package field, enter its package name -- here, enter oracle.apps.ess.howto. In the Class Name field, enter a name for the class -- here, enter HelloWorldJob.

   6. Click OK.

      This creates the Java class you requested, along with the HelloWorldJobDefinition.xml file. Oracle JDeveloper displays XML file's contents in the Job Definition page.

      On the Job Definition page, you can edit job definition metadata, including properties that specify parameters for the job, access to this metadata, and a resource bundle to use for localization.

8. In the HelloWorldJobDef.xml Job Definition page, in the Desciption field, enter HelloWorld Example.

9. In the System Properties section, click the Add button.

10. In the Add System Property dialog, from the Name dropdown, select SYS_effectiveApplication.

11. In the Initial Value field, enter EssDemoApp.

12. Click OK.

13. In the Access Control section, click the Add button.

14. In the Add Access Control dialog, from the Role dropdown, ensure that EssDemoAppRole is selected. This is the role that you created during Section 4.3.1.2.

15. Select the following actions: Read and Execute.

16. Click OK.

4.3.1.4 Creating a Java Implementation Class in the Back-End Hosting Application

To define an application that runs a Java class under control of Oracle Enterprise Scheduling Service you need to create the Java class that implements the Oracle Enterprise Scheduling Service Executable interface. The Executable interface specifies the contract that allows you to use Oracle Enterprise Scheduling Service to invoke a Java class.

When you created metadata in , you also created the basic of the class you need.

To implement the execute method:

1. In the Application Navigator, locate the class you created by expanding the items in the projects panel to SuperEss > Application Sources > oracle.apps.ess > howto > HelloWorldJob.java.

2. Open HelloWorldJob.java in the source editor.

3. In the source editor, add the following code to implement the execute method. The execute method is where execution for a Java job begins. The code inside your method should look something like Example 4-2.

   Example 4-2 HelloWorldJob Execute Method Code

   StringBuilder sb = new StringBuilder(1000);
   sb.append("\n==================================");
   sb.append("\n= EssDemoApp request is now running");
   long myRequestId = ctx.getRequestId();
   sb.append("\n= Request Id = " + myRequestId);
   sb.append("\n= Request Properties:");
   for (String paramKey : params.getNames()) {
       Object paramValue = params.getValue(paramKey);
       sb.append("\n=\t(" + paramKey + ", " + paramValue + ")");
   }
   sb.append("\n=");
   sb.append("\n==================================");
   Logger logger = Logger.getLogger("oracle.apps.ess.howto");
   logger.info(sb.toString());
   

4.3.1.5 Setting Oracle Enterprise Scheduling Service Properties

With Oracle Enterprise Scheduling Service properties, you set values for settings used in the ejb-jar.xml file associated with the application. These properties include the following:

• Logical Application Name

  Specifies the logical name used to identify this application. Separate from the application name used when deploying the application to the container, this value lets you safely hardcode the logical application name in source code.

• Application Policy Stripe

  Specifies which JPS security stripe (or "security context") should be used to perform security checks.

• JPS Interceptor Application Name

  Specifies the application stripe name used at run time to determine which set of security policies are applicable.

To set values for Oracle Enterprise Scheduling Service properties:

1. In the Application Navigator, right-click the EssHost project, then click Enterprise Scheduler Properties.

2. In the Enterprise Scheduler Properties dialog, enter EssDemoApp for all three of the fields provided: Logical Application Name, Application Policy Stripe, and JPS Interceptor Application Name.

3. Click OK.

4.3.1.6 Assembling the Back-End Hosting Application for Oracle Enterprise Scheduling Service

After you create the back-end sample application you use ­Oracle JDeveloper to assemble the application.

To assemble the back-end application you do the following:

• Create the EJB Java Archive

• Create the application MAR and EAR files

4.3.1.7 Deploying the Back-End Hosting Application

After assembling the application, you can deploy it to the server.

To deploy the back-end hosting application:

1. From the main menu, choose Application > Deploy > EAR_EssDemoAppEar...

2. Set up and deploy the application to a container.

3. When the Deployment Configuration dialog appears, make a note of the default values, but do not change them.

4.3.2.1 Creating the Front-End Submitter Application

You use JDeveloper to build the front-end submitter application using similar steps as you used for the back-end hosting application.

To create the front-end submitter application:

1. Complete the steps in Section 4.3.1.1, "Creating the Back-End Hosting Application" but this time use ESSDemoAppUI as the name of the application. When you configure ESS host support settings, in the Application Id field, be sure to enter EssDemoApp.

4.3.2.2 Creating the SuperWeb Project

You need to create a web project for the servlet.

To create the SuperWeb project:

1. Right-click the SuperEss project and choose New.

2. In the New Gallery, expand General, select Projects and then Generic Project, and click OK.

3. In the Name your project window, enter the name for the host project you're creating and select supporting technologies. This project is where you will create and save the Oracle Enterprise Scheduling Service metadata

   1. In the Project Name field, enter a name for your hosting project. For this sample application, enter SuperWeb.

   2. On the Project Technologies tab, under Available, double-click ESS Client Support, JSP and Servlets, and ADF Library Web Application Support so that both are listed under Selected on the right side of the dialog box.

   Click Next.

4. In the Project Java Settings page, change the default package to oracle.apss.ess.howto and click Finish.

4.3.2.3 Configuring Security for the Front-End Submitter Application

You need to configure security for the application. You do not have to create any users or roles as the EssDemoAppUI application will simply share the users and roles created by the EssDemoApp application.

To configure security for the front-end submitter application:

1. Select Application > Secure > Configure ADF Security from the main menu.

2. In the ADF Security page of the Configure ADF Security wizard, select ADF Authentication.

3. In the Authentication Type page, select SuperWeb.jpr from the Web Project dropdown list.

4. Select HTTP Basic Authentication.

5. Click Finish.

   A file named jps-config.xml is generated. You can find this file in the Application Resources panel by expanding Descriptors, and expanding META-INF.

4.3.2.4 Creating the HTTP Servlet for the Front-End Submitter Application

Normally, more complex user interfaces that are built on heavy weight frameworks such as Oracle Application Development Framework are employed, but for the sake of simplicity, you use a basic HTTP servlet for the submitter application.

To create the HTTP Servlet for the front-end submitter application:

1. Right-click the SuperEss project and choose New.

2. In the New Gallery, expand Web Tier, select Servlets and then HTTP Servlet, and click OK.

3. In the Web Application page of the Web Application wizard, select Servlet 2.5\JSP 2.1 (Java EE 1.5).

4. In the Create HTTP Servlet - Step 1 of 3: Servlet Information page, enter EssDemoAppServlet in the Class field.

5. Enter oracle.apps.ess.howto in the Package field and click Next.

6. Click Finish.

7. In the source editor, replace the contents of ESSDemoAppServlet.java with the code in Example 4-3.

   Example 4-3 HTTP Servlet Code for the Front-End Submitter Application

   package oracle.apps.ess.howto;
    
   import java.io.IOException;
   import java.io.PrintWriter;
   import java.io.StringWriter;
    
   import java.util.ArrayList;
   import java.util.Calendar;
   import java.util.Enumeration;
   import java.util.HashSet;
   import java.util.Iterator;
   import java.util.List;
   import java.util.ListIterator;
   import java.util.Map;
   import java.util.Set;
   import java.util.SortedSet;
   import java.util.TreeSet;
   import java.util.logging.Level;
   import java.util.logging.Logger;
   import java.util.regex.Pattern;
    
   import javax.servlet.ServletConfig;
   import javax.servlet.ServletException;
   import javax.servlet.http.HttpServlet;
   import javax.servlet.http.HttpServletRequest;
   import javax.servlet.http.HttpServletResponse;
   import javax.servlet.http.HttpSession;
    
   import oracle.as.scheduler.MetadataObjectId;
   import oracle.as.scheduler.MetadataObjectId.MetadataObjectType;
   import oracle.as.scheduler.MetadataService;
   import oracle.as.scheduler.MetadataService.QueryField;
   import oracle.as.scheduler.MetadataServiceHandle;
   import oracle.as.scheduler.RequestDetail;
   import oracle.as.scheduler.RequestParameters;
   import oracle.as.scheduler.RuntimeService;
   import oracle.as.scheduler.RuntimeServiceHandle;
   import oracle.as.scheduler.State;
   import oracle.as.scheduler.core.JndiUtil;
    
    
   public class EssDemoAppServlet extends HttpServlet {
       @SuppressWarnings("compatibility:4685800289380934682")
       private static final long serialVersionUID = 1L;
    
       private static final String CONTENT_TYPE = "text/html; charset=UTF-8";
       private static final String MESSAGE_KEY = "Message";
       private static final String PATH_SUBMIT = "/submitRequest";
       private static final String PATH_ALTER = "/alterRequest";
       private static final String MDO_SEP = ";";
       private static final String ACTION_CANCEL = "Cancel";
       private static final String ESS_UNAVAIL_MSG =
           "<p>Enterprise Scheduler Service is currently unavailable. Cause: %s</p>";
    
       private enum PseudoScheduleChoices {
           Immediately(0),
           InTenSeconds(10),
           InTenMinutes(10 * 60);
    
           @SuppressWarnings("compatibility:-5637079380819677366")
           private static final long serialVersionUID = 1L;
    
           private int m_seconds;
    
           private PseudoScheduleChoices(int seconds) {
               m_seconds = seconds;
           }
    
           public int getSeconds() {
               return m_seconds;
           }
       }
    
    
    
    
    
       public EssDemoAppServlet() throws ServletException {
           super();
       }
    
       @Override
       public void init(ServletConfig config) throws ServletException {
           super.init(config);
       }
    
       @Override
       public void doGet(HttpServletRequest request, HttpServletResponse response)
           throws ServletException, IOException
       {
           response.setContentType(CONTENT_TYPE);
    
           HttpSession session = request.getSession(true);
           String lastMessage = String.valueOf(session.getAttribute(MESSAGE_KEY));
    
           if ("null".equals(lastMessage)) {
               lastMessage = "";
           }
    
           try {
               RuntimeLists runtimeLists = getRuntimeLists();
               MetadataLists metadataLists = getMetadataLists();
               renderResponse(metadataLists, runtimeLists,
                              request, response, lastMessage);
           } catch (ServletException se) {
               throw se;
           } catch (Exception e) {
               throw new ServletException(e);
           }
       }
    
       @Override
       public void doPost(HttpServletRequest request,
                          HttpServletResponse response)
           throws ServletException, IOException
       {
           response.setContentType(CONTENT_TYPE);
           request.setCharacterEncoding("UTF-8");
    
           HttpSession session = request.getSession(true);
           String pathInfo = request.getPathInfo();
    
           // Clear the message on every post request
           StringBuilder message = new StringBuilder("");
    
           try {
             // Select each handler based on the form action
             if ("".equals(pathInfo)) {
               // No processing
             } else if (PATH_SUBMIT.equals(pathInfo)) {
               postSubmitRequest(request, message);
             } else if (PATH_ALTER.equals(pathInfo)) {
               postAlterRequest(request, message);
             } else {
               message.append(String.format("<p>No handler for pathInfo=%s</p>",
                                            pathInfo));
             }
           }
           catch (ServletException se) {
               Throwable t = se.getCause();
               String cause = (t == null) ? se.toString() : t.toString();
               message.append (String.format(ESS_UNAVAIL_MSG, cause));
           }
    
           // Storing the messages in the session allows them to persist
           // through the redirect and across refreshes.
           session.setAttribute(MESSAGE_KEY, message.toString());
    
           // render the page by redirecting to doGet(); this intentionally
           // strips the actions and post data from the request.
           response.sendRedirect(request.getContextPath() +
                                 request.getServletPath());
       }
    
       /**
        * Handle the job submission form.
        * @param request
        * @param message
        * @throws ServletException
        */
       private void postSubmitRequest(HttpServletRequest request,
                                      StringBuilder message)
           throws ServletException
       {
           String jobDefName = request.getParameter("job");
           String scheduleDefName = request.getParameter("schedule");
    
           // Various required args for submission
           Calendar start = Calendar.getInstance();
           start.add(Calendar.SECOND, 2);
    
    
           // Launch the job based on form contents
           if (jobDefName == null || scheduleDefName == null) {
               message.append("Both a job name and a schedule name must be specified\n");
           } else {
               PseudoScheduleChoices pseudoSchedule = null;
    
               // See if schedule given is actually a pseudo schedule
               try {
                   pseudoSchedule = PseudoScheduleChoices.valueOf(scheduleDefName);
               } catch (IllegalArgumentException e) {
                   // The string is not a valid member of the enum
                   pseudoSchedule = null;
               }
    
    
               MetadataObjectId scheduleDefId = null;
               String scheduleDefNamePart = null;
               MetadataObjectId jobDefId = stringToMetadataObjectId(jobDefName);
    
               // Don't look up schedules that aren't real
               if (pseudoSchedule != null) {
                   scheduleDefNamePart = scheduleDefName;
                   start.add(Calendar.SECOND, pseudoSchedule.getSeconds());
               } else {
                   scheduleDefId = stringToMetadataObjectId(scheduleDefName);
                   scheduleDefNamePart = scheduleDefId.getNamePart();
               }
    
               String jobDefNamePart = jobDefId.getNamePart();
               String requestDesc = jobDefNamePart + "@" + scheduleDefNamePart;
    
    
               Logger logger = getLogger();
               long requestId = submitRequest(pseudoSchedule, requestDesc,
                                              jobDefId, scheduleDefId, start, logger);
    
               // Populate the message block based on results
               message.append(String.format("<p>New request %d launched using %s</p>",
                                            requestId, requestDesc));
           }
       }
    
       private Long submitRequest(final PseudoScheduleChoices pseudoSchedule,
                                  final String requestDesc,
                                  final MetadataObjectId jobDefId,
                                  final MetadataObjectId scheduleDefId,
                                  final Calendar start,
                                  final Logger logger)
           throws ServletException
       {
           RuntimeServicePayload<Long> myPayload = new RuntimeServicePayload<Long>() {
               @Override
               Long execute(RuntimeService service,
                            RuntimeServiceHandle handle,
                            Logger logger)
                   throws Exception
               {
                   RequestParameters params = new RequestParameters();
                   return (null != pseudoSchedule)
                       ? service.submitRequest(handle, requestDesc, jobDefId,
                                               start, params)
                       : service.submitRequest(handle, requestDesc, jobDefId,
                                               scheduleDefId, null,
                                               start, null, params);
               }
           };
           try {
               return performOperation(myPayload, logger);
           } catch (Exception e) {
               throw new ServletException("Error submitting request using job: " +
                                          jobDefId + " and schedule: " +
                                          scheduleDefId, e);
           }
       }
    
       /**
        * Handle the "Cancel" and "Purge" actions from the form enclosing
        * the Request Status table.
        * @param request
        * @param message
        * @throws ServletException
        */
       private void postAlterRequest(HttpServletRequest request,
                                     StringBuilder message)
           throws ServletException
       {
           String cancelID = null;
    
           /*
            * there are a few assumptions going on here...
            * the HTTP button being used to transmit the action and
            * request is backwards from its normal usage (eg. the name
            * should be invariable, and the value variable).  Because we
            * want to display either "Purge" or "Cancel" on the button, and
            * transmit the reqId with it, we are reversing the map entry
            * to get the key (which in this case will be the reqID), and
            * match it to the value (Purge or Cancel).
            * Assumptions are that there will be only one entry in the map
            * per request (one purge or cancel).  Also, that the datatypes
            * for the key and value willl be those documented for
            * ServletRequest (<K,V> = <String, String[]>).
            */
           Map requestMap = request.getParameterMap();
           Iterator mapIter = requestMap.entrySet().iterator();
           while (mapIter.hasNext()) {
               Map.Entry entry = (Map.Entry)mapIter.next();
               String key = (String)entry.getKey();
               String[] values = (String[])entry.getValue();
               if (ACTION_CANCEL.equals(values[0])) {
                   cancelID = key;
               }
           }
    
           if (cancelID != null) {
               try {
                   final String cancelId2 = cancelID;
                   RuntimeServicePayload<Void> myPayload = new RuntimeServicePayload<Void>() {
                       @Override
                       Void execute(RuntimeService service,
                                    RuntimeServiceHandle handle,
                                    Logger logger)
                           throws Exception
                       {
                           service.cancelRequest(handle, Long.valueOf(cancelId2));
                           return null;
                       }
                   };
    
                   Logger logger = getLogger();
                   performOperation(myPayload, logger);
                   message.append
                       (String.format("<p>Cancelled request %s</p>", cancelID));
               } catch (Exception e) {
                   throw new ServletException
                       ("Error canceling or purging request", e);
               }
           } else {
               message.append("<p>No purge or cancel action specified</p>");
           }
       }
    
       private String metadataObjectIdToString(MetadataObjectId mdoID)
           throws ServletException {
    
           String mdoString =
               mdoID.getType().value() + MDO_SEP + mdoID.getPackagePart() +
               MDO_SEP + mdoID.getNamePart();
    
           return mdoString;
       }
    
       private MetadataObjectId stringToMetadataObjectId(String mdoString)
           throws ServletException {
           String[] mdoStringParts = mdoString.split(Pattern.quote(MDO_SEP));
           if (mdoStringParts.length != 3) {
               throw new ServletException(String.format("Unexpected number of components %d found " +
                                                        "when converting %s to MetadataObjectID",
                                                        mdoStringParts.length,
                                                        mdoString));
           }
    
           MetadataObjectType mdType =
               MetadataObjectType.getMOType(mdoStringParts[0]);
           String mdPackage = mdoStringParts[1];
           String mdName = mdoStringParts[2];
    
           MetadataObjectId mdoID =
               MetadataObjectId.createMetadataObjectId(mdType, mdPackage, mdName);
           return mdoID;
       }
    
       /**
        * this changes the format used in this class for job definitions to the one
        * which will be used in the runtime query.
        * @param strMetadataObject
        * @return string representing object in runtime store
        * @throws ServletException
        */
       private String fixMetadataString(String strMetadataObject)
           throws ServletException {
           String fslash = "/";
           String[] mdoStringParts =
               strMetadataObject.split(Pattern.quote(MDO_SEP));
           if (mdoStringParts.length != 3) {
               throw new ServletException(String.format("Unexpected number of components %d found " +
                                                        "when converting %s to MetadataObjectID",
                                                        mdoStringParts.length,
                                                        strMetadataObject));
           }
           String[] trimStringParts = new String[mdoStringParts.length];
           for (int i = 0; i < mdoStringParts.length; i++) {
               String mdoStringPart = mdoStringParts[i];
               trimStringParts[i] = mdoStringPart.replaceAll(fslash, " ").trim();
           }
    
           MetadataObjectType mdType =
               MetadataObjectType.getMOType(trimStringParts[0]);
           String mdPackage = fslash + trimStringParts[1];
           String mdName = trimStringParts[2];
           MetadataObjectId metadataObjId =
               MetadataObjectId.createMetadataObjectId(mdType, mdPackage, mdName);
           return metadataObjId.toString();
       }
    
       private Set<String> getSetFromMetadataEnum(Enumeration<MetadataObjectId> enumMetadata)
           throws ServletException {
           Set<String> stringSet = new HashSet<String>();
    
           while (enumMetadata.hasMoreElements()) {
               MetadataObjectId objId = enumMetadata.nextElement();
               String strNamePart = objId.getNamePart();
               stringSet.add(strNamePart);
           }
           return stringSet;
       }
    
       //****************************************************************************
       //
       //   HTML Rendering Methods
       //
       //****************************************************************************
    
       /**
        * Rendering code for the page displayed.
        * In a real application this would be done using JSP, but this approach
        * keeps everything in one file to make the example easier to follow.
        * @param response The response object from the main request.
        * @param message Text that will appear in the message panel, may contain HTML
        * @throws IOException
        */
       private void renderResponse(MetadataLists ml,
                                   RuntimeLists rl,
                                   HttpServletRequest request,
                                   HttpServletResponse response,
                                   String message)
           throws IOException, ServletException
       {
           response.setContentType(CONTENT_TYPE);
           PrintWriter out = response.getWriter();
    
           String urlBase = request.getContextPath() + request.getServletPath();
    
           // Indents maintained for clarity
           out.println("<html>");
           out.println("<head><title>EssDemo</title></head>");
           out.println("<body>");
           out.println("<table align=\"center\"><tbody>");
           out.println("  <tr><td align=\"center\"><h1>Oracle Enterprise Scheduling Service Tutorial</h1></td></tr>");
           out.println("  <tr><td align=\"center\"><table cellspacing=6><tr>");
    
           // Job launch form
           out.println("    <td align=\"center\">");
           out.println("      <h2>Launch Job</h2>");
           renderLaunchJobForm(ml, out, urlBase);
           out.println("    </td>");
    
           out.println("    <td align=\"center\" bgcolor=\"blue\" width=\"2\"/>");
    
           out.println("  </tr></table></td></tr>");
    
           out.println("  <tr><td bgcolor=\"red\"/></tr>");
    
           // Message panel
           out.println("      <tr><td align=\"center\"><h3>Messages</h3></td></tr>");
           out.println("      <tr><td>");
           out.println(message);
           out.println("    </td></tr>");
    
           out.println("  <tr><td bgcolor=\"red\"/></tr>");
    
           // Request status
           out.println("  <tr><td align=\"center\">");
           out.println("    <form name=\"attrs\" action=\"" + urlBase +
                       PATH_ALTER + "\" method=\"post\">");
           out.println("    <h2>Request Status</h2>");
           out.println("    <table border=2><tbody>");
           out.println("          <th>reqID</th>");
           out.println("          <th>Description</th>");
           out.println("          <th>Scheduled time</th>");
           out.println("          <th>State</th>");
           out.println("          <th>Action</th>");
    
           renderStatusTable(out, rl.requestDetails);
    
           out.println("    </tbody></table>");
           out.println("    </form>");
           out.println("  </td></tr>");
           out.println("</tbody></table>");
           out.println("</body></html>");
           out.close();
       }
    
       private void renderLaunchJobForm(MetadataLists ml, PrintWriter out, String urlBase)
           throws ServletException {
           out.println("      <form name=\"attrs\" action=\"" + urlBase +
                       PATH_SUBMIT + "\" method=\"post\">");
           out.println("        <table><tbody>");
           out.println("          <tr><td align=\"right\">");
           out.println("            <b>Job:</b>");
           out.println("            <select name=\"job\">");
    
           renderMetadataChoices(out, ml.jobDefList, false);
           renderMetadataChoices(out, ml.jobSetList, false);
    
           out.println("            </select>");
           out.println("          </td></tr>");
           out.println("          <tr><td align=\"right\">");
           out.println("            <b>Schedule:</b>");
           out.println("            <select name=\"schedule\">");
    
           renderPseudoScheduleChoices(out);
           renderMetadataChoices(out, ml.scheduleList, false);
    
           out.println("            </select>");
           out.println("          </td></tr>");
           out.println("          <tr><td align=\"center\">");
           out.println("            <input name=\"submit\" value=\"Submit\" type=\"submit\">");
           out.println("          </td></tr>");
           out.println("        </tbody></table>");
           out.println("      </form>");
       }
    
       /**
        *
        * @param out - printwriter
        * @param jobChoices --  metadata to be displayed
        * @param bBlankFirst -- blank first (so that this param is not required)
        * @throws ServletException
        */
       private void renderMetadataChoices(PrintWriter out,
                                          Enumeration<MetadataObjectId> jobChoices,
                                          boolean bBlankFirst)
           throws ServletException
       {
           if (jobChoices == null)
               return;
    
           boolean bFirst = true;
           while (jobChoices.hasMoreElements()) {
               MetadataObjectId job = jobChoices.nextElement();
               String strJob = metadataObjectIdToString(job);
               String strNamePart = job.getNamePart();
               if (strNamePart.compareTo("BatchPurgeJob") == 0) {
                   continue;
               } else {
                   if (bFirst && bBlankFirst) {
                       out.printf("<option value=\"%s\">%s</option>", "", "");
                       bFirst = false;
                   }
                   out.printf("<option value=\"%s\">%s</option>", strJob,
                              strNamePart);
               }
           }
       }
    
       /**
        * helper method for rendering choices based on strings, adding an empty
        * string to the beginning of the list
        * @param out
        * @param choices
        */
       private void renderStringChoices(PrintWriter out, Set<String> choices) {
           if (choices == null)
               return;
    
           choices.add("");
           SortedSet<String> sorted = new TreeSet<String>(choices);
           Iterator choiceIter = sorted.iterator();
           while (choiceIter.hasNext()) {
               String choice = (String)choiceIter.next();
    
               out.printf("<option value=\"%s\">%s</option>", choice, choice);
           }
       }
    
       private void renderPseudoScheduleChoices(PrintWriter out) {
           for (PseudoScheduleChoices c : PseudoScheduleChoices.values()) {
               out.printf("<option value=\"%s\">%s</option>", c, c);
           }
       }
    
       private void renderStatusTable
           (PrintWriter out, List<RequestDetail> reqDetails)
       {
           if (reqDetails == null) {
               return;
           }
    
           for (RequestDetail reqDetail : reqDetails) {
               State state = reqDetail.getState();
    
               Calendar scheduledTime = reqDetail.getScheduledTime();
               String scheduledTimeString = null;
    
               if (scheduledTime == null) {
                   scheduledTimeString = "null scheduled time";
               } else {
                   scheduledTimeString = String.valueOf(scheduledTime.getTime());
               }
    
               final String actionButton;
               if (!state.isTerminal()) {
                   String action = ACTION_CANCEL;
                   String reqId = String.valueOf(reqDetail.getRequestId());
                   actionButton = String.format
                       ("<button type=submit value=%s name=\"%s\">%s</button>",
                        action, reqId, action);
               } else {
                   actionButton = "&nbsp;";
               }
    
               out.printf("<tr><td>%d</td><td>%s</td><td>%s</td><td>%s</td><td>%s</td></tr>\n",
                          reqDetail.getRequestId(), reqDetail.getDescription(),
                          scheduledTimeString, state, actionButton);
           }
       }
    
    
       private MetadataService getMetadataService() throws Exception {
           return JndiUtil.getMetadataServiceEJB();
       }
    
       private RuntimeService getRuntimeService() throws Exception {
           return JndiUtil.getRuntimeServiceEJB();
       }
    
       private abstract class Payload<SERVICE, HANDLE, RETURN> {
           abstract SERVICE getService() throws Exception;
           abstract HANDLE getHandle(SERVICE service) throws Exception;
           abstract void closeHandle(SERVICE service,
                                     HANDLE handle,
                                     boolean abort)
               throws Exception;
           abstract RETURN execute(SERVICE service, HANDLE handle, Logger logger)
               throws Exception;
       }
    
       private abstract class MetadataServicePayload<T>
           extends Payload<MetadataService, MetadataServiceHandle, T>
       {
           @Override
           MetadataService getService() throws Exception {
               return getMetadataService();
           }
    
           @Override
           MetadataServiceHandle getHandle(MetadataService service)
               throws Exception
           {
               return service.open();
           }
    
           @Override
           void closeHandle(MetadataService service,
                            MetadataServiceHandle handle,
                            boolean abort)
               throws Exception
           {
               service.close(handle, abort);
           }
       }
    
       private abstract class RuntimeServicePayload<T>
           extends Payload<RuntimeService, RuntimeServiceHandle, T>
       {
           @Override
           RuntimeService getService() throws Exception {
               return getRuntimeService();
           }
    
           @Override
           RuntimeServiceHandle getHandle(RuntimeService service)
               throws Exception
           {
               return service.open();
           }
    
           @Override
           void closeHandle(RuntimeService service,
                            RuntimeServiceHandle handle,
                            boolean abort)
               throws Exception
           {
               service.close(handle, abort);
           }
       }
    
       private <S, H, R> R performOperation
               (Payload<S, H, R> payload, Logger logger)
           throws Exception
       {
           S service = payload.getService();
           H handle = payload.getHandle(service);
    
           Exception origException = null;
           try {
               return payload.execute(service, handle, logger);
           } catch (Exception e2) {
               origException = e2;
               throw e2;
           } finally {
               if (null != handle) {
                   try {
                       boolean abort = (null != origException);
                       payload.closeHandle(service, handle, abort);
                   } catch (Exception e2) {
                       if (null != origException) {
                           logger.log(Level.WARNING, "An error occurred while " +
                               "closing handle, however, a previous failure was " +
                               "detected.  The following error will be logged " +
                               "but not reported: " + stackTraceToString(e2));
                       }
                   }
               }
           }
       }
    
       private final String stackTraceToString(Exception e) {
           StringWriter sw = new StringWriter();
           PrintWriter pw = new PrintWriter(sw);
           e.printStackTrace(pw);
           pw.flush();
           pw.close();
           return sw.toString();
       }
    
       private Logger getLogger() {
           return Logger.getLogger(this.getClass().getName());
       }
    
       private class MetadataLists {
           private final Enumeration<MetadataObjectId> jobDefList;
           private final Enumeration<MetadataObjectId> jobSetList;
           private final Enumeration<MetadataObjectId> scheduleList;
           private final Enumeration<MetadataObjectId> jobTypeList;
    
           private MetadataLists(Enumeration<MetadataObjectId> jobDefList,
                                 Enumeration<MetadataObjectId> jobSetList,
                                 Enumeration<MetadataObjectId> scheduleList,
                                 Enumeration<MetadataObjectId> jobTypeList)
           {
               this.jobDefList   = jobDefList;
               this.jobSetList   = jobSetList;
               this.scheduleList = scheduleList;
               this.jobTypeList  = jobTypeList;
           }
       }
    
       private class RuntimeLists {
           private final List<RequestDetail> requestDetails;
           private final Set<String> applicationChoices;
           private final Set<String> stateChoices;
           private final Set<MetadataObjectId> jobDefMDOChoices;
    
           private RuntimeLists(List<RequestDetail> requestDetails,
                                Set<String> applicationChoices,
                                Set<String> stateChoices,
                                Set<MetadataObjectId> jobDefMDOChoices)
           {
               super();
               this.requestDetails = requestDetails;
               this.applicationChoices = applicationChoices;
               this.stateChoices = stateChoices;
               this.jobDefMDOChoices = jobDefMDOChoices;
           }
       }
    
       /**
        * Retrieve lists of jobs, schedules, and status for use by the renderer
        * @throws ServletException
        */
       private MetadataLists getMetadataLists() throws Exception {
           Logger logger = getLogger();
    
           MetadataServicePayload<MetadataLists> myPayload =
               new MetadataServicePayload<MetadataLists>()
           {
               @Override
               MetadataLists execute(MetadataService service,
                                     MetadataServiceHandle handle,
                                     Logger logger)
                   throws Exception
               {
                   Enumeration<MetadataObjectId> jobDefs =
                       service.queryJobDefinitions(handle, null, QueryField.NAME, true);
                   Enumeration<MetadataObjectId> jobSets =
                       service.queryJobSets(handle, null, QueryField.NAME, true);
                   Enumeration<MetadataObjectId> schedules =
                       service.querySchedules(handle, null, QueryField.NAME, true);
                   Enumeration<MetadataObjectId> jobTypes =
                       service.queryJobTypes(handle, null, QueryField.NAME, true);
    
                   return new MetadataLists(jobDefs, jobSets, schedules, jobTypes);
               }
           };
           MetadataLists ml = performOperation(myPayload, logger);
           return ml;
       }
    
       private RuntimeLists getRuntimeLists() throws Exception {
           Logger logger = getLogger();
    
           RuntimeServicePayload<List<RequestDetail>> myPayload2 =
               new RuntimeServicePayload<List<RequestDetail>>()
           {
               @Override
               List<RequestDetail> execute(RuntimeService service,
                                           RuntimeServiceHandle handle,
                                           Logger logger)
                   throws Exception
               {
                   List<RequestDetail> reqDetails =
                       new ArrayList<RequestDetail>(10);
                   Enumeration requestIds = service.queryRequests
                       (handle, null, RuntimeService.QueryField.REQUESTID, true);
    
                   while (requestIds.hasMoreElements()) {
                       Long reqId = (Long)requestIds.nextElement();
                       RequestDetail detail = service.getRequestDetail(handle, reqId);
                       reqDetails.add(detail);
                   }
    
                   return reqDetails;
               }
           };
           List<RequestDetail> reqDetails = performOperation(myPayload2, logger);
           RuntimeLists rl = getRuntimeLists(reqDetails);
           return rl;
       }
    
       private RuntimeLists getRuntimeLists(List<RequestDetail> reqDetails) {
           Set<String> applicationSet = new HashSet<String>(10);
           Set<String> stateSet = new HashSet<String>(10);
           Set<MetadataObjectId> jobDefMOSet = new HashSet<MetadataObjectId>(10);
    
           if (reqDetails != null) {
               ListIterator detailIter = reqDetails.listIterator();
               while (detailIter.hasNext()) {
                   RequestDetail detail = (RequestDetail)detailIter.next();
                   applicationSet.add(detail.getDeployedApplication());
                   State state = detail.getState();
                   if (state.isTerminal())
                       stateSet.add(state.name());
                   jobDefMOSet.add(detail.getJobDefn());
               }
           }
    
           RuntimeLists rl = new RuntimeLists
               (reqDetails, applicationSet, stateSet, jobDefMOSet);
           return rl;
       }
    
   }
   

4.3.2.5 Editing the web.xml File for the Front-End Submitter Application

You need to edit the web.xml file to and Oracle Enterprise Scheduling Service metadata and runtime EJB references.

To edit the web.xml file for the front-end submitter application:

1. In the Application Navigator, expand SuperWeb, expand Web Content, expand WEB-INF and double-click web.xml.

2. In the overview editor, click the References navigation tab and expand the EJB References section.

3. Add two EJB resources with the information shown in Table 4-1.

   Table 4-1 EJB Resources for the Front-End Submitter Application

   EJB Name	Interface Type	EJB Type	Local/Remote Interface
   ess/metadata	Local	Session	oracle.as.scheduler.MetadataServiceLocal
   ess/runtime	Local	Session	oracle.as.scheduler.RuntimeServiceLocal

   
   

4. Click the Servlets navigation tab and click the Servlet Mappings tab.

5. Change the /essdemoappservlet URL pattern to /essdemoappservlet/*.

4.3.2.6 Editing the weblogic-application.xml file for the Front-End Submitter Application

You need to create and edit the weblogic-application.xml file.

To edit the weblogic-application.xml file for the front-end submitter application:

1. In Application Navigator, right-click the SuperEss project and select New.

2. In the New Gallery, expand General, select Deployment Descriptors and then Weblogic Deployment Descriptor, and click OK.

3. In the Select Descriptor page select weblogic-application.xml.

4. Click Next, click Next again, and click Finish.

5. In the source editor, replace the contents of the weblogic-application.xml file that you just created with the XML shown in Example 4-4.

   Example 4-4 Contents to Copy to weblogic-application.xml for a Front-End Submitter Application

   <?xml version = '1.0' encoding = 'UTF-8'?>
   <weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                         xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-application
    
   http://www.bea.com/ns/weblogic/weblogic-application/1.0/weblogic-application.xsd"
                         xmlns="http://www.bea.com/ns/weblogic/weblogic-application">
    
       <!-- The following application parameter tells JPS which stripe it should
          - use to upload the jazn-data.xml policy.  If this parameter is not
          - specified, it will use the Java EE deployment name plus the version
          - number (e.g. EssDemoApp#V2.0).
         -->
       <application-param>
           <param-name>jps.policystore.applicationid</param-name>
           <param-value>EssDemoAppUI</param-value>
       </application-param>
    
       <!-- This listener allows JPS to configure itself and upload the
          - jazn-data.xml policy to the appropriate stripe
         -->
       <listener>
           <listener-class>oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener</listener-class>
       </listener>
    
       <!-- This listener allows MDS to configure itself and upload any metadata
          - as defined by the MAR profile and adf-config.xml
         -->
       <listener>
           <listener-class>oracle.mds.lcm.weblogic.WLLifecycleListener</listener-class>
       </listener>
    
       <!-- This listener allows Oracle Enterprise Scheduling Service to configure itself
         -->
       <listener>
           <listener-class>oracle.as.scheduler.platform.wls.deploy.ESSApplicationLifecycleListener</listener-class>
       </listener>
    
       <!-- This shared library contains all the Oracle Enterprise Scheduling Service classes
         -->
       <library-ref>
           <library-name>oracle.ess.client</library-name>
       </library-ref>
       <library-ref>
           <library-name>adf.oracle.domain</library-name>
       </library-ref>
   </weblogic-application>
   

4.3.2.7 Editing the adf-config file for the Front-End Submitter Application

You need to edit the adf-config.xml file to tell the application to share the metadata that was created in the hosting application.

To edit the adf-config.xml file for the front-end submitter application:

1. From the Application Resources panel, expand Descriptors, expand ADF META-INF, and double-click adf-config.xml.

2. In the source editor, replace the contents of the adf-config.xml file with the XML shown in Example 4-5.

   Example 4-5 Contents to Copy to adf-config.xml for a Front-End Submitter Application

   <?xml version="1.0" encoding="UTF-8" ?>
   <adf-config xmlns="http://xmlns.oracle.com/adf/config">
     <adf-security-child xmlns="http://xmlns.oracle.com/adf/security/config">
       <JaasSecurityContext initialContextFactoryClass="oracle.adf.share.security.JAASInitialContextFactory"
                            jaasProviderClass="oracle.adf.share.security.providers.jps.JpsSecurityContext"
                            authorizationEnforce="false"
                            authenticationRequire="true"/>
     </adf-security-child>
     <adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
       <mds-config xmlns="http://xmlns.oracle.com/mds/config" version="11.1.1.000">
         <persistence-config>
           <metadata-namespaces>
             <namespace metadata-store-usage="ess_shared_metadata" path="/oracle/apps/ess/howto"/>
           </metadata-namespaces>
           <metadata-store-usages>
             <metadata-store-usage default-cust-store="false" deploy-target="false" id="ess_shared_metadata"/>
           </metadata-store-usages>
         </persistence-config>
       </mds-config>
     </adf-mds-config>
   </adf-config>
   

4.3.2.8 Assembling the Front-End Submitter Application for Oracle Enterprise Scheduling Service

After you create the front-end sample application you use ­Oracle JDeveloper to assemble the application.

To assemble the back-end application you do the following:

• Create the EJB Java Archive

• Create the WAR file

• Create the application MAR and EAR files

4.3.2.9 Deploying the Front-End Submitter Application

After assembling the application, you can deploy it to the server.

To deploy the front-end submitter application:

1. From the main menu, choose Application > Deploy > EAR_EssDemoUIEar...

2. Set up and deploy the application to a container.

3. On the Deployment Configuration dialog, there should be two entries in the Shared Metadata Repositories panel. Find the shared repository mapped to the /oracle/apps/ess/howto namespace. Change its partition to the partition used when deploying EssDemoApp. If you used the default value, this should be EssDemoApp_V2.0.

4. Click OK.

4.3.2.10 Running the Split Application

To run the split application:

1. Enter the following URL in a browser:

   http://host:http-port:/ESSDemoAppUI/essdemoappservlet

   For example,

   http://myserver.us.oracle.com:7101/EssDemoAppUI/essdemoappservlet
   

2. Log in as EssDemoAppUser with the password welcome1.

3. Follow the same steps as in the combined application.