Creating a Deployment Profile for BC4J UIX Applications

When creating a BC4J UIX application using JDeveloper, a J2EE web module (WAR file) is generated containing both the Business Components for Java (BC4J) and the UIX application files. The JDeveloper deployment profile wizards create all the necessary code to deploy business components as a web module to the embedded OC4J server or target application server. Typically, a UIX client accesses the BC4J application in a J2EE web module configuration. The UIX client can also include data tags, data web beans, XSQL, tag libraries, and UIX tags to access the business components.

To create a deployment profile for BC4J UIX applications:

  1. (Optional) If you do not want to deploy your business components logic directly to the J2EE web module, you must first create a deployment profile and choose to configure an EJB session bean. For more information on the common deployment configurations and how to determine whether to deploy directly to the web module, see Understanding the n-Tiered Business Components Architecture.
  2. Create a client UIX application project (for example, UIX JSP) containing your client application files.
    Note: When selecting the Application Module and deployment configuration, choose the configuration that you want your JSP to use to connect to the deployed application module. For example, choosing <YourApplicationModule>Local would deploy the business logic to the web module. Choosing <YourApplicationModule>9iAS instructs the JSP to use the business logic in the EJB session bean (created in step 1). Upon creation of the client application project, JDeveloper generates the web.xml and the WAR deployment profile.
  3. (Optional) If you want to edit the webxmlicon web.xml deployment descriptor settings, right-click its icon and choose Settings in the Navigator below the specified project. The Web Application Deployment Descriptor dialog lets you edit any of the standard deployment descriptor settings. Alternatively, you can choose Code Editor if you are knowledgeable about the web.xml format.
    For more information on these parameters, refer to the Sun Microsystems Java Servlet Specification, Version 2.2 which you can download from:
    http://www.javasoft.com/products/servlet/
  4. (Optional) If you want to edit the J2EE WAR deployment profile, select and right-click WAR_dep_profile_icon <Project_jpr_WAR>.deploy profile on the Navigator below the specified project. The WAR Deployment Profile Settings panel displays. Configure the settings for each page as appropriate:
    1. General Page
    2. WAR File Page: Directory View and Rules View
    3. WAR Options Subpage
    4. WEB-INF/classes Subpage
    5. WEB-INF/lib Subpage
    6. (Optional) Applet Options Page: to include an applet in your deployment profile. See Deploying an Applet as a WAR File.
    7. (Optional) Applet Classes Subpage
    8. (Optional)Applet Archives Subpage
    9. (Optional) Profile Dependencies Page: if the deployment profile depends on J2EE modules from another deployment profile. JDeveloper lets you build a WAR deployment profile that can specify EJB JAR or WAR dependencies from other projects. Thus, when the WAR is deployed to the target application server, the corresponding dependencies are also packaged with the WAR file in a single Enterprise Archive (EAR) file.
    10. (Optional) Platform Subpage: JDeveloper lets you specify a default connection to be displayed in the context menu of the web application deployment profile, and lets you specify the target platform. You can also pass command line parameters to any of the supported target connection types.
    11. Click OK when you are done.
  5. By default, you can run and debug the WAR components in JDeveloper's embedded OC4J server to test the application. However, when you are ready to deploy the resulting WAR or EAR to the target application server, make sure to create an application server connection.
  6. To deploy the BC4J UIX deployment profile, see Deploying BC4J UIX Applications.

Notes: