Applications with ADF Business Components are deployed in much the same manner as other applications. However, the ADF runtime libraries must be installed on servers that host business components applications. To accomplish this task, JDeveloper provides the ADF Runtime Installer, which you run within JDeveloper. The installer places the ADF libraries from the JDeveloper installation on your target application server.
When business components are deployed as a simple archive, the business components are packaged as a J2EE Java archive (JAR) file which the client application can access. Deploying as a J2EE JAR file is especially suited to client code, such as JClient applications, that run on fast, shared machines.
When business components are deployed as a J2EE web module, the business components are packaged as a J2EE web archive (WAR) file which the web application can access. Deploying as a J2EE web module is especially suited to web applications, such as ADF UIX applications, JSP applications, and servlets, that run on fast, shared machines.
When business components are deployed as an EJB session bean, the business components run in a separate tier (middle-tier) from the client programs. For example, the EJB session bean runs on an EJB server such as Oracle Application Server.
At deployment time, the application module must be enabled for client data binding. In JDeveloper, you can make the application module available to the client (remoteable) when creating a deployment profile with the Create Business Components EJB Deployment Profile Wizard, Step 2 of 2: AppModules . Making the application module remoteable means creating an EJB remote interface and/or client-side proxies for application module methods which must be deployed to the client platform. For more information, see:
Notes:.
Copyright © 1997, 2004, Oracle. All rights reserved.