J2EE web applications

<script language="javascript1.2" type="text/javascript"> </script>  

<script language="JavaScript" src="popup.js" type="text/javascript"></script>

J2EE web applications

A J2EE web application is a collection of JSP pages, Java classes, archive and configuration files and that can be deployed on an application server.

J2EE web applications are assembled and deployed in Web Archive Archive (WAR) file. After placing the components of your web application in the appropriate directory structure, create a WAR file that you can deploy on your application server.

A web application that uses the Web Intelligence Report Engine SDK or Business Objects Enterprise SDK contains:

• JSP and HTML pages.
• Java classes and libraries.
• Application configuration files.

  Application configuration files describe the web application and its configuration parameters. Generally these files are standard J2EE components. An example of a standard J2EE configuration file is such as the deployment descriptor. Some application servers require specific configuration files. For more information on these, refer to the documentation provided with your application server.

• Business Objects components

  Including Java classes and libraries, as well as applets and other Business Objects components.

Installing Business Objects components

Business Objects SDK components are added to the development machine when BusinessObjects Enterprise XI is installed on the system. To develop a custom Web Intelligence Report Engine SDK application it is necessary to connect to a running BusinessObjects Enterprise server, however, the development environment does not have to be on the same machine as the BusinessObjects Enterprise Server. Install Web Intelligence Report Engine SDK components on a development machine by:

1. Run BusinessObjects Enterprise XI installer.
2. Click     Next on the Business Objects Enterprise XI Installation Wizard panel.
3. Select the I accept the License Agreement button in the License Agreement panel.
4. Click Next.
5. Select the Perform Server Installation
6. Click Next.
7. Enter your corporate information and keycode.
8. Click Next.
9. Specify the destination folder in the Destination folder text box.
10. Click Next.
11. Select the Custom button
12. Click Next.
13. Deselect all Business Objects Enterprise Features.
14. Enable the SDK products feature.

    To install J2EE components only, deselect the SDK products feature and install the Java features sub -c omponent.

15. Click Next.
16. Click Next.

This installs all components necessary to develop custom Business Objects applications; Java libraries are installed and registered correctly and .NET libraries are registered in the GAC.

Assembling a web application

To deploy a custom Web Intelligence application, you must archive the components in a Web Application Archive (.war) file. WAR files are defined in the Java Servlet API 2.2 specification.

To assemble all the components in a WAR file, you must:

1. Create the web application directory structure.

   WAR files require a specific directory structure. For information on the directory structure, see Assembling Business Objects components for J2EE.

2. Add necessary J2EE components in the application directory structure.
3. Add the Business Objects components.

   For information on how to add the Business Objects components, seeAdding Business Objects components for J2EE.

4. Generate a WAR file containing the contents of the directory structure created in step 1.

   For information on how to generate a WAR file, see Generating a WAR file.

Defining the web application directory structure

Before you assemble the application components, you must define the directory structure for the application. To do so:

1. Create a root directory with an appropriate name for the application
2. In the root directory, create the following directory structure.

 Structure of a J2EE web application

For more information on the directories necessary to create a web application see page 18.

Web application directories

The table below describes the directories and components needed to create a deployable Web Intelligence Report Engine customized application.

Directory	Description
root directory (/application_name)	This is the root directory of the web application, known as document root. It contains all the public files that can be served to clients. These include the JSP pages, HTML pages, image files and other static web resources. This directory should have an appropriate name for the web application.
/application_name/classes	contains servlet and utility classes that are accessible to clients
/application_name/META -I NF	contains the manifest file, manifest.mf As with WEB -I NF, the files located in this directory are considered as private files and are not served to clients.
/application_name/WEB -I NF	contains all resources related to the application that are not in the document root of the application Files located in this directory are considered as private files and are not served to clients. This is where your web application deployment descriptor, web.xml is located.
/application_name/WEB -I NF/classes	contains servlet and utility classes that are used by the web application but cannot be downloaded by clients, and configuration files for the Web Intelligence Report Engine SDK
/application_name/WEB -I NF/lib	contains JAR files that are used by the web application but cannot be downloaded by clients For example, this is where you place Web Intelligence SDK JAR files.
/application_name/WebiApplet	contains the JAR file used for the Web Intelligence Java Report Panel
/application_name/WebiApplet/AppletConfig	contains configuration files for the Web Intelligence Java Report Panel

 

Adding Business Objects components for J2EE

To add the Business Objects components to the application:

• Copy the components manually from your Business Objects XI installation to your web application directory structure.

  For information on manually coping the components, see Assembling Business Objects components for J2EE.

Business Objects components that must added to a Web Intelligence Report Engine customized application are described in the next section.

Which Business Objects components does my web application need?

A web application that uses the Web Intelligence Report Engine SDK or Business Objects Enterprise SDK and RAS and Viewers SDK must contain certain basic Business Objects components in addition as the standard J2EE components. You can also include or customize other Business Objects components to create a more elaborate custom application.

The following table lists components and configuration files required by a custom Web Intelligence Report Engine SDK, BusinessObjects Enterprise SDK, RAS or Viewers SDK application. Optional Business Objects components are marked as "opt".

Component	File name	Required/Optional
		REBean SDK	BOE SDK	RAS + ViewersSDK
BusinessObjects Enterprise SDK
Main files for the BusinessObjects Enterprise SDK	cecore.jar celib.jar ceplugins.jar cereports.jar cesession.jar ceutils.jar cexsd.jar Serialization.jar	req	req
Components required to use the ORB.	CorbaIDL.jar bus405.jar	req	req	req
Business Objects and third party configuration files
Jakarta log4j properties file This is the configuration file for the log4j package discussed on page 20.	log4j.properties.	opt
Configuration file reader.	boconfig.jar	req
Business Objects and third party components
Apache logging library. This package is required if wilog.jar is used. This package used to debug applications. The Jakarta log4j system is part of the Jakarta project. See http://Jakarta.apache.org/log4j.	log4j.jar	opt
XML and XSL tools. Third party components for using XML and XSL, included in the Business Objects installation.	xalan.jar xercesImpl.jar xml -a pi.jars	req
Web Intelligence components
Classes common and necessary for both REBean.FC and REBean.WI.	rebean.common.jar	req
Classes necessary to work with DesktopIntelligence documents.	rebean.fc.jar	req
Classes necessary to work with Web Intelligence documents.	rebean.wi.jar	req
Interfaces for the Web Intelligence Report Engine object model.	rebean.jar	req
Web Intelligence servlets Contains the gateway between the Web Intelligence Java Report Panel and its server. It is required when if the Java Report Panel is used.	cdzlet.jar	opt
Web Intelligence Java Report Panel This is used for a web application used to create and edit Web Intelligence documents. Note:    you can create and edit documents using the REBean package rather than using the Java Report Panel. For more information, see the Customizing Web Intelligence with REBean guide.	ThinCadenza.jar	opt
Web Intelligence HTML cascading style sheets These files are required for the Web Intelligence HTML viewer.	file_name.css	req
Default settings for the Web Intelligence Java report panel. Required only when the Java Report Panel (ThinCadenza.jar) is included in the web application.	defaultConfig.xml defaultHelp.properties defaultSkin.properties	opt
Default settings for Web Intelligence report creation when using Web Intelligence Report Engine SDK.	defaultConfig.xml	opt
JavaScript files used to provide DHTML popup menu functionality. These files are not to be modified.	bomenuIE.js bomenuNS.js browserDetection.js drillcontext.js drillcontextDom.js message.js	req
Image files for viewing Web Intelligence documents in HTML format. These images required for all applications unless documents are viewed in PDF or Excel format only.	file_name.gif	req
Debug, trace and helper tools	jtools.jar	req
Web Intelligence logging utility library	wilog.jar	opt
RAS and Viewers SDK files
RAS and Viewers SDK	MetafileRenderer.jar rasapp.jar rascore.jar ReportPrinter.jar ReportTemplate.jar CRDBJavabeansServer.jar CRDBJavaServer.jar CRDBJavaServerCommon.jar CRDBJDBCServer.jar CRDBXMLServer.jar CRDB_JavaServer.ini webireporting.jar webireporting -j sf.jar WebReportWizard.jar crlov.jar crlovexternal.jar crlovmanifest.jar			opt
Web Services files
Web Services consumers library	dsws -b icatalog.jar dsws -c ommon.jar dswsreportengine.jar dsws -s ession.jar

How do the Business Objects components fit together?

Business Objects components provide Web Intelligence, BusinessObjects Enterprise and Crystal Reports functionality and support utilities to the application. They enable the application to access the Business Objects cluster. The deployed web application uses the data in the Business Objects configuration files to access the Business Objects cluster.

Web Intelligence Report Engine SDK applications

The figure below shows how Business Objects components fit in a custom Web Intelligence application. It illustrates how components relate to the Business Objects deployment.

 

Assembling Business Objects components for J2EE

The rest of this guide is concerned with the Business Objects Enterprise SDK, Web Intelligence Report Engine SDK and associated REBean samples.

After you create the directory structure (see Defining the web application directory structure), you must place application components in the appropriate directories.

This section explains where in the directory structure you must place each component. It also lists the source for each component. A component may be created by a developer or copied from an existing Business Objects product or web application.

For a description of each component, see Which Business Objects components does my web application need?.

The document root directory

You must add application components that will be accessed directly by the client browser in the document root directory. The following table lists the standard J2EE and Business Objects components that must be stored in the document root directory or an appropriate subdirectory as well as the source of each component.

Component	File name	Source
JSP files	*.jsp	created by the application developer or copied from one of the WAR files in $INSTALLDIR/Tomcat/ webapps/ businessobjects/enterprise11/desktoplaunch/viewers/cdz
HTML files	*.html
image files	*.gif *.jpg
Other static resources Note:    If your application server is configured to run with a web server, you can deploy static resource files on the web server while deploying the rest of the application on the application server. See Static resource files.
Web Intelligence HTML cascading style sheets These files must be accessible to the JSP pages that are using them.	*.css	$INSTALLDIR/Tomcat/ webapps/ businessobjects/enterprise11/desktoplaunch/viewers/cdz/ style/skin_default
Web Intelligence HTML generation scripts These scripts must be accessible to the JSP pages that are using them. They are required for applications that view Web Intelligence documents. These files are not to be modified.	bomenuIE.js	$INSTALLDIR/Tomcat/ webapps/ businessobjects/enterprise11/desktoplaunch/viewers/cdz
	bomenuNS.js
	browserDetection.js
	drillcontext.js
	drillcontextDom.js
	message.js	$INSTALLDIR/Tomcat/ webapps/ businessobjects/enterprise11/desktoplaunch/viewers/cdz/ language/xx where xx is the message language
image files for Web Intelligence HTML generation The images directory should be in the directory where the JSP pages that are using it are stored. Note:    You must not rename the Web Intelligence images directory when you copy it to an application.	*.gif	$INSTALLDIR/Tomcat/ webapps/ businessobjects/enterprise11/desktoplaunch/viewers/cdz/ images

The /WEB-INF directory

Add private files that are not served to clients in the /WEB -I NF directory.

The deployment descriptor, web.xml must be stored in the /WEB -I NF directory. Web.xml can be created manually, generated by your development environment or retrieved from an existing application and modified.

Deployment descriptor

A WAR archive requires at least one deployment descriptor file called web.xml, that is stored in the WEB -I NF directory. The deployment descriptor is an XML file that describes the web application and the components it contains.

Some application servers also require their own additional deployment descriptors. For information, refer to your application server documentation.

Example:    Deployment descriptor

The following text is an example of a simple deployment descriptor. In the file an web application ID, name and a description are defined.

< ? xml version="1.0" encoding="UTF -8 " ? >

<!DOCTYPE web -a pp PUBLIC "-//Sun Microsystems, Inc.//DTD Web

Application 2.2//EN" "http://java.sun.com/j2ee/dtds/

web -a pp_2_2.dtd">

   <web -a pp id="web_application_ID">

      <display -n ame>web_application_name</display -n ame>

      <description>web_application_description</description>

   </web -a pp>

The /WEB-INF/classes directory

Application components may use servlets or classes that are not served directly to the client. Place servlet and utility classes used only by the application in the /WEB -I NF/classes directory.

The following table lists Business Objects components that must be stored in the /WEB -I NF/classes directory and where to find them.

Component	File name	Source
Jakarta log4j properties file See also the Apache logging package listed in The WebiApplet/AppletConfig directory.	log4j.properties.	generated when log4j is activated
Default settings for Web Intelligence reports created using Web Intelligence Report Engine SDK. The defaultConfig.xml file is also deployed in the /WebiApplet/AppletConfig directory to set default settings for the Web Intelligence Java Report Panel. See The WebiApplet/AppletConfig directory.	defaultConfig.xml	%Common Program Files%/Business Objects/3.5/java/webiApplet

The WebiApplet directory

The WebiApplet directory contains files necessary to use the Web Intelligence Java Report panel. The following table shows the files in the directory:

Component	File name	Source
Web Intelligence Java Report Panel applet	ThinCadenza.jar	%CommonProgramFiles%/Business Objects/3.5/java/webiApplet/

Note:    the WEBI -I NF/classes folder also contains files necessary for the Web Intelligence Java Report Panel. See The /WEB -I NF/classes directory for more information.

The WebiApplet/AppletConfig directory

Applications that use the Java Report Panel use the configuration files found in the WebiApplet/AppletConfig folder to retrieve default settings for Java Report Panel. The following table shows the files in the directory:

Component	File name	Source
Default settings for the Web Intelligence Java Report Panel. The defaultConfig.xml file is also deployed in the /WEBI -I NF/classes directory. It is used to set default values when creating Web Intelligence documents using theWeb Intelligence Report Engine SDK. See The /WEB -I NF/classes directory	defaultConfig.xml defaultHelp.properties defaultSkin.properties	%CommonProgramFiles%/Business Objects/3.5/java/webiApplet/AppletConfig

The /WEB-INF/lib directory

Applications may contain classes or JAR files that are not served to the client. Place JAR files used only by the application in the /WEB -I NF/lib directory.

The following table lists Business Objects and third party components that must be stored in the /WEB -I NF/lib directory and where to find them.

Component	File name	Source
Business Objects Enterprise SDK main files	cecore.jar celib.jar ceplugins.jar cereports.jar cesession.jar ceutils.jar cexsd.jar Serialization.jar	%CommonProgramFiles%/ Business Objects/3.5/java/lib
ORB components	CorbaIDL.jar ebus405.jar
Web Intelligence servlets	cdzlet.jar
Web Intelligence Report Engine SDK	webi.jar
Web Intelligence logging utility library	wilog.jar
Configuration file reader	boconfig.jar
trace and configuration utilities	witools.jar
Web Services Consumers Library	dsws -b icatalog.jar dsws -c ommon.jar dsws -r eportengine.jar dsws -s ession.jar
third party XML and XSL tools	xalan.jar	$INSTALLDIR/Tomcat/ common/endorsed
	xercesImpl.jar
	xml -a pi.jar
Apache logging library. See also the log4j properties file listed in The /WEB -I NF/classes directory	log4j.jar
Debug, trace and helper tools	jtools.jar	%CommonProgramFiles%/ Business Objects/3.5/java/lib

The /META-INF directory

The META -I NF directory contains a standard manifest file, manifest.mf which can contain information about the files packaged in the WAR file.

The manifest file in a WAR file is the same as manifest file contained in a JAR file. Manifest.mf is generated when you create the WAR file or you can create it manually. For information, see http://java.sun.com.

Generating a WAR file

When you have created and assembled the components of your application, you must generate the WAR file that will be deployed on your application server. You can do so using one of the following methods:

• The JAR utility included in Java 2 SDK.

  You can find more information about the JAR utility at:

  http://java.sun.com

• A WAR generation tool included with some application servers or development environments.

Static resource files

If your application server is configured to run with a web server, you can deploy static resource files on the web server. For more on static resource files, see Static resources on a web server.

---

<script language="JavaScript" type="text/javascript"> </script> <script src="DeploymentGuideHTML.js" type="text/javascript"></script>

Business Objects http://www.businessobjects.com/ Support services http://www.businessobjects.com/services/support/

<script language="javascript1.2" type="text/javascript"> </script>