TIBCO BusinessWorks EJB Plug-in User s Guide. Software Release 5.3 February 2008

Transcription

1 TIBCO BusinessWorks EJB Plug-in User s Guide Software Release 5.3 February 2008

2 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN TIBCO BUSINESSWORKS EJB PLUG-IN USER S GUIDE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIB, TIBCO, Predictive Business, Information Bus, The Power of Now, TIBCO Rendezvous, TIBCO InConcert, TIBCO Administrator, TIBCO Adapter, and TIBCO BusinessWorks are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

3 iii Contents Preface v Related Documentation vi TIBCO BusinessWorks Documentation vi Other Documentation vi Typographical Conventions viii How to Contact TIBCO Support ix Chapter 1 Enterprise JavaBeans (EJB) EJB Overview Accessing an EJB Requirements for Connecting to the EJB Server Sending or Receiving Java Objects Chapter 2 EJB Palette Reference EJB Connection Configuration Test Connection Button Pooling and Caching EJB Home Configuration Advanced Input Output Error Output EJB Remote Configuration Advanced Input Output Error Output Chapter 3 Error Codes EJB Error Codes Index TIBCO BusinessWorks EJB Plug-in User s Gudie

4 iv Contents TIBCO BusinessWorks EJB Plug-in User s Gudie

5 v Preface This software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. Please see the readme.txt file for the availability of this software version on a specific operating system platform. TIBCO BusinessWorks is a standards-based, easy-to-deploy solution for companies looking to integrate their enterprise computing environment and automate their business processes. This manual describes the Enterprise JavaBeans (EJB) palette of TIBCO BusinessWorks. This manual is not intended to be a complete reference for developing process definitions using TIBCO BusinessWorks. Understanding the content of the TIBCO BusinessWorks documentation is a prerequisite to using the EJB palette. Topics Related Documentation, page vi Typographical Conventions, page viii How to Contact TIBCO Support, page ix

6 vi Related Documentation Related Documentation This section lists documentation resources you may find useful. TIBCO BusinessWorks Documentation The following documents are part of the TIBCO BusinessWorks documentation set: TIBCO BusinessWorks Concepts Read this manual before reading any other manual in the documentation set. This manual describes terminology and concepts of TIBCO BusinessWorks, and the other manuals in the documentation set assume you are familiar with the information in this manual. TIBCO BusinessWorks Installation Read this manual for information on installing one or more components of TIBCO BusinessWorks and setting up a TIBCO BusinessWorks domain. TIBCO BusinessWorks Getting Started This manual steps you through a very simple example of designing, deploying, and monitoring a TIBCO BusinessWorks process. TIBCO BusinessWorks Process Design Guide This manual describes how to create, edit, and test business processes using TIBCO BusinessWorks. TIBCO BusinessWorks Palette Reference This manual describes each of the palettes available in TIBCO BusinessWorks. TIBCO BusinessWorks Administration This manual describes how to use TIBCO Administrator to deploy, manage, and monitor TIBCO BusinessWorks processes. TIBCO BusinessWorks Error Codes This manual describes errors returned by TIBCO BusinessWorks. TIBCO BusinessWorks Release Notes Read the release notes for a list of new and changed features. This document also contains lists of known issues and closes issues for this release. Other Documentation You may find it useful to read the documentation for the following TIBCO products:

7 Preface vii TIBCO Designer software: TIBCO Designer is an easy to use graphical user interface for design-time configuration of TIBCO applications. TIBCO Designer includes online help for each palette. TIBCO Administrator software: TIBCO Administrator is the monitoring and managing interface for new-generation TIBCO products such as TIBCO BusinessWorks.

8 viii Typographical Conventions Typographical Conventions The following typographical conventions are used in this manual. Table 1 General Typographical Conventions Convention code font bold code font italic font Key combinations Use Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example: Use MyCommand to start the foo process. Bold code font is used in the following ways: In procedures, to indicate what a user types. For example: Type admin. In large code samples, to indicate the parts of the sample that are of particular interest. In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable disable] Italic font is used in the following ways: To indicate a document title. For example: See TIBCO BusinessWorks Concepts. To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal. To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C. Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q. The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances. The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result. The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

9 Preface ix How to Contact TIBCO Support For comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows. For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site: If you already have a valid maintenance or support contract, visit this site: Entry to this site requires a user name and password. If you do not have a user name, you can request one.

10 x How to Contact TIBCO Support

11 1 Chapter 1 Enterprise JavaBeans (EJB) The EJB palette of TIBCO BusinessWorks allows you to connect to J2EE-compliant application servers and invoke Enterprise JavaBeans (EJB) components, or enterprise beans, on the servers. Enterprise beans are distributed, server-side software components that provide services that remote clients can invoke. For more information about enterprise beans see Topics EJB Overview, page 2 Accessing an EJB, page 3 Requirements for Connecting to the EJB Server, page 4 Sending or Receiving Java Objects, page 5

12 2 Chapter 1 Enterprise JavaBeans (EJB) EJB Overview An Enterprise JavaBean (EJB) component is a software component that encapsulates the business logic of an application. The EJB specification was created by Sun Microsystems, Inc., and more information about enterprise beans can be found at The EJB palette of TIBCO BusinessWorks allows you to connect to J2EE-compliant application servers and invoke Enterprise JavaBeans (EJB) components, or enterprise beans, on the servers. The EJB specification includes support for Java Transaction API (JTA) UserTransactions. TIBCO BusinessWorks provides support for these transactions and allows enterprise beans to be called within a client-managed transaction. See TIBCO BusinessWorks Process Design Guide for more information about transactions. The following application servers are supported by the EJB palette: BEA WebLogic, Version 7.0 with service pack 2 BEA WebLogic, Version 8.1 with service pack 1 BEA WebLogic, Version 9.2 JBoss, Version IBM WebSphere, Version 5.0.2

13 Accessing an EJB 3 Accessing an EJB The EJB standard defines the mechanism for a client to access enterprise beans. 1. Obtain a reference to a JNDI server. 2. Perform a JNDI lookup operation to obtain a reference to the home object. 3. Obtain a reference to a remote object from the home object. 4. Invoke one or more methods on the remote object. The EJB palette encapsulates this process in three resources. EJB Connection a shared configuration resource used to specify the connection to the server. EJB Home an activity that connects to the server (specified by an EJB Connection resource), performs a JNDI lookup operation to obtain a reference to the home object, and obtains a reference to the remote object from the home object. You can also use this activity to invoke any methods defined on the home object. EJB Remote invokes a method defined on the Remote interface of the specified EJB.

14 4 Chapter 1 Enterprise JavaBeans (EJB) Requirements for Connecting to the EJB Server When invoking an EJB, a TIBCO BusinessWorks process instance acts as an EJB remote client. To connect to an EJB server and invoke an EJB, the client must have the following in the classpath: the EJB server JAR files (supplied by the EJB server vendor) required for clients. the client JAR files that contains the required EJB client stubs (EJBHome, EJBObject) for invoking the desired beans For more information about the files necessary for EJB clients, see the documentation for your EJB server. To load the required files into the Java VM, you can either modify the TIBCO Designer and TIBCO BusinessWorks classpath in the designer.tra and bwengine.tra files, or you can use File Aliases. You must use the same technique for loading the required files for both the application server JAR files and the client JAR files. See the comments in the designer.tra and bwengine.tra files for more information on adding paths to the classpath. See TIBCO Designer Palette Reference for more information about File Alias resources.

15 Sending or Receiving Java Objects 5 Sending or Receiving Java Objects Input parameters or return values for enterprise beans can be Java objects. You can use the activities of the Java palette to create the object within the process definition to send or receive a Java object to or from an EJB. For example, if you wish to call a remote method that requires a Java object as an input parameter, you can create the object with a Java Code activity. If you wish to use a Java object received as a return value from calling an EJB, you can pass the object to a Java Code activity. See TIBCO BusinessWorks Palette Reference for more information on working with Java objects in process definitions.

16 6 Chapter 1 Enterprise JavaBeans (EJB)

17 7 Chapter 2 EJB Palette Reference This chapter describes the resources contained in the EJB Palette. Topics EJB Connection, page 8 EJB Home, page 12 EJB Remote, page 17

18 8 Chapter 2 EJB Palette Reference EJB Connection Shared Configuration The EJB Connection shared configuration resource specifies the connection configuration for the JNDI server. The EJB Home activity uses this connection information to establish a connection to this service. Configuration The configuration tab has the following fields. Field Global Var? Description Name No The name to appear as the label for the resource. Description No Short description of the shared resource. Use Shared JNDI Configuration JNDI Configuration No No When this field is checked, the JNDI Configuration field appears that allows you to choose a JNDI Configuration shared configuration resource. When this field is unchecked, the JNDI Context Factory, JNDI Context URL, JNDI User Name, and JNDI Password fields appear. This field only appears when the Use Shared JNDI Configuration field is checked. This field allows you to choose a JNDI Configuration shared configuration object that specifies the JNDI connection information. See TIBCO BusinessWorks Palette Reference for more information about JNDI Configuration resources.

19 EJB Connection 9 Field JNDI Context Factory JNDI Context URL JNDI User Name JNDI Password Global Var? Yes Yes Yes Yes Description This field only appears when the Use Shared JNDI Configuration field is unchecked. The InitialContextFactory to use when connecting to the JNDI server (javax.naming.context.initial_context_ FACTORY). This field provides a drop-down list of InitialContext Factories supplied by each supported application server vendor. You can supply a different InitialContextFactory other than the default options in the drop-down list. When using IBM WebSphere, you should use the JNDI Configuration resource instead of specifying the JNDI configuration on this resource. See the description of the JNDI Configuration shared configuration resource in TIBCO BusinessWorks Palette Reference for more information. This field only appears when the Use Shared JNDI Configuration field is unchecked. Specifies the URL of the server (javax.naming.context.provider_url). An example URL is provided when one of the supported JNDI context factory classes is selected. See your JNDI provider documentation for the syntax of the URL. This field only appears when the Use Shared JNDI Configuration field is unchecked. User name to use when logging into the JNDI server (javax.naming.context.security_ PRINCIPAL). If the JNDI provider does not require access control, this field can be empty. This field only appears when the Use Shared JNDI Configuration field is unchecked. Password to use when logging into the JNDI server (javax.naming.context.security_ CREDENTIALS). If the JNDI provider does not require access control, this field can be empty.

20 10 Chapter 2 EJB Palette Reference Field Maximum Connections Connection Retries Global Var? Yes Yes Description Maximum number of naming contexts (InitialContext) that are created and cached in the connection pool. If this field is set to zero or less, the naming context is not cached and a new context is created for each lookup (InitialContext.lookup()) operation. Maximum number of attempts to make to connect to the service or to create the naming context. If this field is set to one or less, only one attempt is made to establish a connection. Test Connection Button When the Test Connection button is clicked, TIBCO BusinessWorks attempts to connect to the specified service using the specified username and password. You can use this button to determine if the specified connection will succeed. Pooling and Caching Creating an InitialContext requires a great deal of overhead. Therefore, contexts can be cached and placed in a pool to improve performance over time. The Maximum Connections field specifies the maximum number of InitialContexts TIBCO BusinessWorks will create at any given time. IBM WebSphere uses its own caching mechanism for JNDI context objects. This mechanism interferes with the caching mechanism used by TIBCO BusinessWorks. To disable the IBM WebSphere caching mechanism, use a JNDI Configuration shared configuration with an optional JNDI property to disable caching. See the description of the JNDI Configuration resource in TIBCO BusinessWorks Palette Reference for more information. The InitialContext is only used when obtaining a reference to the Home object. Once the Home object is obtained, the context is released back into the pool. As process definitions request contexts, TIBCO BusinessWorks creates the contexts and places them in a pool. New contexts are created only when a request occurs and all available contexts in the pool are in use. If the specified maximum number of contexts have been created, and all contexts are being used, TIBCO BusinessWorks blocks any new requests until a context is freed from the pool.

21 EJB Connection 11 All contexts are cached for reuse by subsequent process instances. If you specify 0 or less for the Maximum Connections field, contexts are not cached, and each request creates a new InitalContext. If a context becomes "stale" (for example, the server is restarted), TIBCO BusinessWorks attempts to create a new context to replace the stale context in the pool. TIBCO BusinessWorks uses the Connection Retries field to determine how many attempts to make to re-establish the context.

22 12 Chapter 2 EJB Palette Reference EJB Home Activity object. The EJB Home activity establishes a connection to the service (based on the specified EJB Connection), obtains a reference to the home object, and then obtains a reference to the remote object from the home object. You can also use this activity to invoke a method on the EJB s home Once this activity is executed, you can then use the EJB Remote activity to invoke methods on the remote object without having to perform additional remote lookups. You can optionally cache the home object and the stateless remote objects to reuse them across process instances. This can improve the performance because further remote lookups are not necessary. Java class files or archives referenced by this resource must be available to the Java VM in which TIBCO Designer and the TIBCO BusinessWorks process engine are running. This is done either by adding the correct path to the classpath in the designer.tra and bwengine.tra files (see the comments in the.tra files for more information about modifying the classpath) or by using an Alias Library resource. If you add the path to the classpath, the system class loader loads the class into the Java VM. If you use an Alias Library resource, the TIBCO BusinessWorks application class loader loads the class into the Java VM. If both techniques are used, the class loaded by the system class loader takes precedence. Objects created from classes loaded by different class loaders are not able to interact. For example, an Alias Library resource points to the location of Java ClassA and a Java Method activity references ClassA. Java class ClassB is placed in the classpath and referenced by an EJB Home activity. The EJB Home activity returns the ClassB object and passes it to the Java Method activity, but the ClassA object in the Java Method activity may not be able to interact with the ClassB object. If you wish objects to interact correctly, ensure that the activities use the same class loader. Configuration The configuration tab has the following fields. Field Global Var? Description Name No The name to appear as the label for the activity in the process definition.

23 EJB Home 13 Field Global Var? Description Description No Short description of the activity. EJB Connection No The EJB Connection shared configuration resource to use to connect with the remote EJB. JNDI Name Yes The name registered with the JNDI server for the EJB. Home Interface: Library Home Interface: Class Home Interface: Method No No No Use this field to specify an AliasLibrary resource that is used to locate the Java class files. Using this field automatically populates the Class field. See TIBCO Designer Palette Reference for more information about AliasLibrary resources. Name of the home interface for the EJB (javax.ejb.ejbhome). You can use the Show Class Browser button to the right of the field to display the available classes for enterprise beans. The home interface method to call. The drop-down list provides the methods contained in the selected home interface class.

24 14 Chapter 2 EJB Palette Reference Advanced The Advanced tab has the following fields: Field Cache Home Object Cache Stateless Bean Remote Object Global Var? No No Description Specifies whether the home object should be cached for use by process instances. If unchecked, each process instance performs a JNDI lookup to obtain the home object reference. If checked, process instances can reuse the cached home object reference. Choosing to cache the home or remote object can improve performance over time. However, the home or remote object may become "stale". That is, the object changes on the EJB server, and the cached object no longer matches the object on the server. If the EJB Home activity encounters a stale Home object in the cache, the activity attempts to recreate the Home object. The Connection Retries field of the EJB Connection shared configuration resource specifies the number of retries that the EJB Home activity will attempt before failing to recreate the Home object. If the EJB Home activity is successful in recreating the Home object, the activity succeeds and a new Home object is placed in the cache. If the activity cannot recreate the Home object after the maximum number of retries, the activity fails and takes the error transition. Specifies whether the remote object should be cached for use by process instances. The remote object can only be cached for stateless session enterprise beans. If unchecked, each process instance obtains a new remote object reference. If checked, process instances can reuse the cached remote object reference. If the process instance encounters a stale cached remote object, the object is removed from the cache, an error is returned, and the activity fails. However, subsequent process instances will attempt to recreate the remote object.

25 EJB Home 15 Input See TIBCO BusinessWorks Process Design Guide for more information about mapping and transforming input data. The input for the activity is the following. Input Item Datatype Description MethodParameters complex An object containing the parameters required by the Home interface method (shown only if the method is selected on the Configuration tab requires parameters). Output The output for the activity is the following. Output Item Datatype Description MethodReturnValue depends upon the method The value returned by the Home interface method. Shown only if the home interface method selected on the Configuration tab returns a value. Error Output The Error Output tab lists the exceptions that can be thrown by the method invoked on Home interface. Once a method to invoke is selected, the exceptions that the method can throw are listed on the Error Output tab. Because a method can return any Java exception, the potential exceptions cannot be listed here. While all potential errors cannot be known, the error schema for all errors is the same. The following describes the schema for exceptions returned by the EJB Home activity.

26 16 Chapter 2 EJB Palette Reference Error Schema Element Datatype Description <exceptionname> complex The fully-qualified name of the exception, including the Java package name. This is a container for the remaining elements. <exceptionname> Java Object The Java exception object. exceptionclassname string The exception class name. The value of this element is obtained by calling the <exception>.getclass().getname() method. exceptionmessage string The exception message. The value of this element is obtained by calling the <exception>.getmessage() method.

27 EJB Remote 17 EJB Remote Activity The EJB Remote activity invokes a method on the remote object obtained by the EJB Home activity. This activity must be placed after an EJB Home activity in a process definition. Configuration The configuration tab has the following fields. Field Global Var? Description Name No The name to appear as the label for the activity in the process definition. Description No Short description of the activity. EJB Home Activity Remote Interface: Library Remote Interface: Class Remote Interface: Method No No No No The EJB Home activity in the process definition that obtained the reference to the remote object. The drop-down list only supplies EJB Home activities that obtain references to remote objects. EJB Home activities that do not create remote objects are not listed. The name of the Alias Library resource, if one is used by the selected EJB Home activity. See TIBCO Designer Palette Reference for more information about Alias Library resources. The name of the remote interface (javax.ejb.ejbobject) obtained by the EJB Home activity. This field is populated automatically based on the selected EJB Home activity. The method to call. The drop-down list provides a list of public methods contained in the remote interface class.

28 18 Chapter 2 EJB Palette Reference Advanced The Advanced tab has the following field: Field Release Remote Object Global Var? No Description If this field is checked, the remote object is released after this activity completes. If this field is unchecked, the remote object can be used by subsequent EJB Remote activities within this process definition. This field is only meaningful for stateful session and entity beans. Cached remote stateless session beans are never released when this field is checked. This field is useful if you wish to release the memory used by the stateful session and entity bean before continuing with the remainder of the process definition. Note: If you are invoking a method on a stateful session or entity bean, you should only check this field when no subsequent activities in the process definition invoke the remote object. If the object is released and a subsequent invocation is made, an error is returned. Input See TIBCO BusinessWorks Process Design Guide for more information about mapping and transforming input data. The input for the activity is the following. Input Item Datatype Description MethodParameters complex An object containing the parameters required by the remote interface method (shown only if the method is selected on the Configuration tab requires parameters).

29 EJB Remote 19 Output The output for the activity is the following. Output Item Datatype Description MethodReturnValue depends upon the method The value returned by the remote interface method. Shown only if the remote interface method selected on the Configuration tab returns a value. Error Output The Error Output tab lists the exceptions that can be thrown by the invoked method. Once a method to invoke is selected, the exceptions that the method can throw are listed on the Error Output tab. Because a method can return any Java exception, the potential exceptions cannot be listed here. While all potential errors cannot be known, the error schema for all errors is the same. The following describes the schema for exceptions returned by the EJB Remote activity. Error Schema Element Datatype Description <exceptionname> complex The fully-qualified name of the exception, including the Java package name. This is a container for the remaining elements. <exceptionname> Java Object The Java exception object. exceptionclassname string The exception class name. The value of this element is obtained by calling the <exception>.getclass().getname() method. exceptionmessage string The exception message. The value of this element is obtained by calling the <exception>.getmessage() method.

30 20 Chapter 2 EJB Palette Reference

31 21 Chapter 3 Error Codes This chapter describes error codes that can be returned by activities within the EJB palette. Topics EJB Error Codes, page 22

32 22 Chapter 3 Error Codes EJB Error Codes BW-EJB : Activity input schema creation error. Exception [%1] occurred while trying to create input schema. %2 Description: The EJB plugin activity is not able create schema for the activity's input tab. Exception occurred Resolution: Please correct the error and retry. BW-EJB : Activity output schema creation error. Exception [%1] occurred while trying to create output schema. %2 Description: The EJB plugin activity is not able create schema for the activity's output tab. Exception occurred Resolution: Please correct the error and retry. BW-EJB : Activity input data conversion error. Exception [%1] occurred while trying to render the activity input data. %2 Description: This activity is not able to convert the activity's input data Resolution: Please Contact TIBCO Support

33 EJB Error Codes 23 BW-EJB : Activity output data conversion error. Exception [%1] error occurred while trying to create the activity output data. %2 Description: This activity is not able to create the output data. Resolution: Please Contact TIBCO Support BW-EJB : Connection Test Failed. %1 Description: Unable to establish connection to the server. Resolution: Please correct the error stated in the exception message and retry. BW-EJB : Connection Test Failed. Exception [%1] occurred. Description: Unable to establish connection to the server. Exception occurred Resolution: Please correct the error stated in the exception message and retry. BW-EJB : Unable to obtain information for method [%1] from the class [%2]. NoSuchMethodException occurred. %3 Description: The method name is not contained in the declared Java class. Resolution: It is possible that the declared Java class has been modified since the last configuration of this activity. Please reconfigure this activity or verify that the declared Java class has not changed since the last configuration.

34 24 Chapter 3 Error Codes BW-EJB : Unable to obtain information for method [%1] from the class [%2]. SecurityException occurred. %3 Description: SecurityException occurred while trying to get method information from the declared Java class. Resolution: Please correct the error and retry. BW-EJB : Unable to obtain information for method [%1] from the class [%2]. ClassNotFoundException occurred. %3 Description: ClassNotFoundException occurred while trying to get method information from the declared Java class. Resolution: Please verify that the declared class file is contained in the classpath. BW-EJB : Unable to obtain information for method [%1] from the class [%2]. Exception occurred. %3 Description: Exception occurred while trying to get method information from the declared Java class. Resolution: Please correct the error and retry.

35 EJB Error Codes 25 BW-EJB : Java class [%1] not found in the classpath. ClassNotFoundException occurred. %2 Description: ClassNotFoundException occurred while trying to access the specified Java class. Resolution: Please verify that the specified class file is contained in the classpath. BW-EJB : Linkage error occurred for the Java class [%1]: %2 Description: LinkageError occurred while trying to access the specified Java class. Resolution: Please correct the error stated in the exception message and retry. BW-EJB : Unable to create an instance of the Java class [%1]: %2 Description: Unable to create an instance of the specified Java class. Resolution: Please correct the error stated in the exception message and retry. BW-EJB : The EJB Connection [%1] not found in repository Description: The repository does not contain the EJB Connection activity referenced by this activity. Resolution: Please correct the error and retry.

36 26 Chapter 3 Error Codes BW-EJB : The EJB Connection [%1] contains invalid field values. Description: The EJB Connection activity referenced by this activity contains invalid field values. Resolution: Please correct the error and retry. BW-EJB : Exception occurred while trying to obtain the EJB Connection reference [%1]: %2 Description: Unable to get the EJB Connection referenced by this activity Resolution: Please correct the error and retry. BW-EJB : Unable to create an instance of 'javax.naming.initialcontext'. NamingException occurred. %1 Description: Exception of type 'javax.naming.namingexception' occurred while trying to construct an instance of 'javax.naming.initialcontext'. Resolution: Please correct the specified NamingException and retry. BW-EJB : Unable to create an instance of 'javax.naming.initialcontext'. Exception [%1] occurred. %2 Description: Exception occurred while trying to construct an instance of 'javax.naming.initialcontext'. Resolution: Please correct the error stated in the exception message and retry.

37 EJB Error Codes 27 BW-EJB : Unable to obtain the EJBHome object for the JNDI name [%1]. NamingException occurred. %2 Description: Exception of type 'javax.naming.namingexception' occurred on invocation of the method 'javax.naming.initialcontext.lookup(..)' Resolution: Please correct the specified NamingException and retry. BW-EJB : Unable to obtain the EJBHome object for the JNDI name [%1]. Exception [%2] occurred. %3 Description: Exception occurred on invocation of the method 'javax.naming.initialcontext.lookup(..)' Resolution: Please correct the specified NamingException and retry. BW-EJB : Unable to obtain EJBMetaData from the EJBHome object of type [%1]. Exception [%2] occurred while trying to invoke the method 'getejbmetadata()' on the EJBHome object. %3 Description: Exception occurred while trying to invoke the method 'javax.ejb.ejbhome.getejbmetadata()'. Resolution: Please correct the error stated in the exception message and retry.

38 28 Chapter 3 Error Codes BW-EJB : Unable to cast the EJBHome object reference obtained from the JNDI to the declaring EJBHome interface class [%1]. Exception [%2] occurred while trying to invoke the method 'javax.rmi.portableremoteobject.narrow(..)'. %3 Description: Exception occurred while trying to invoke the method 'javax.rmi.portableremoteobject.narrow(..)'. Resolution: Possible causes for this error are: (1). The EJBHome interface is not bound to the correct JNDI Name. Verify that the EJBHome interface name specified for this activity is bound to the JNDI name specified in this activity. (2). The EJBHome interface class file is not in the classpath. Verify that the EJBHome interface class is in the classpath. BW-EJB : EJB system exception occurred. The EJBHome interface method [%1] raised exception [%2]. %3 Description: The EJBHome interface method raised an system exception. The EJB system exception are exceptions that are subclass of the class 'java.rmi.remoteexception'. Resolution: This error was returned by the EJBHome interface method. Please refer to your application server documentation and the bean implementation for details. BW-EJB : EJB application exception occurred. The EJBHome interface method [%1] raised exception [%2]. %3 Description: The EJBHome interface method raised an application exception. The EJB application exceptions are business logic exception thrown by the bean or the exceptions that are not the subclass of the class 'java.rmi.remoteexception'. Resolution: This error was returned by the EJBHome interface method. Please refer to the bean implementation for details.

39 EJB Error Codes 29 BW-EJB : The activity received incorrect value for the EJBHome interface method parameters. IllegalArgumentException occurred while trying to invoke the EJBHome interface method [%1]: %2 Description: The user specified incorrect value for the EJB Home method parameters. IllegalArgumentException occurred while trying to invoke the EJBHome interface method. Resolution: Verify that the correct values are provided for the EJBHome interface method parameter elements listed in the input tab of this activity. BW-EJB : The activity contains an invalid EJBHome object reference. The declaring EJBHome interface class [%1] found in the classpath is not valid or the EJBHome object reference obtained from the JNDI lookup is not an instance of the declaring EJBHome interface class [%2]. Exception occurred while trying to invoke the EJBHome interface method [%3]: %4 Description: The activity contains incorrect EJBHome object reference. Resolution: Possible causes for this error are: (1). The classpath refers to a incorrect EJB Client jar file that contains the declaring EJBHome class. Verify that the classpath refers to the correct EJBHome class or the EJB Client jar file. BW-EJB : Unable to invoke the EJBHome interface method [%1]. Exception [%2] occurred while trying to invoke the specified EJBHome interface method. %3 Description: Unable to invoke a method on the EJBHome interface. Exception occurred. Resolution: Please correct the error stated in the exception message and retry.

40 30 Chapter 3 Error Codes BW-EJB : EJB system exception occurred. The EJBRemote interface method [%1] raised exception [%2]. %3 Description: The EJBRemote (EJBObject) interface method raised an system exception. The EJB system exception are exceptions that are subclass of the class 'java.rmi.remoteexception'. Resolution: This error was returned by the EJB Remote interface method. Please refer to your application server documentation and the bean implementation for details. BW-EJB : EJB application exception occurred. The EJBRemote interface method [%1] raised exception [%2]. %3 Description: The EJBRemote (EJBObject) interface method raised an application exception. The EJB application exceptions are business logic exception thrown by the bean or the exceptions that are not the subclass of the class 'java.rmi.remoteexception'. Resolution: This error was returned by the EJB Remote interface method. Please refer to the bean implementation for details. BW-EJB : Input data error. The activity received incorrect value for the EJBRemote interface method parameters. IllegalArgumentException occurred while trying to invoke the EJBRemote interface method [%1]: %2 Description: The user specified incorrect value for the EJBRemote (EJBObject) method parameters. IllegalArgumentException occurred while trying to invoke the EJBRemote interface method. Resolution: Verify that the correct values are provided for the EJBRemote interface method parameter elements listed in the input tab of this activity.

41 EJB Error Codes 31 BW-EJB : Unable to invoke the EJBRemote interface method [%1]. Exception [%2] occurred while trying to invoke the specified EJBRemote interface method: %3 Description: Unable to invoke a method on the EJBRemote (EJBObject) interface. Exception occurred. Resolution: Please correct the error stated in the exception message and retry. BW-EJB : An instance of the EJBRemote object [%1] not found in the current TIBCO BusinessWorks job. Description: This activity is not able to obtain the EJB Remote object from the current TIBCO BusinessWorks job. Resolution: Make sure that the preceding EJB Home activity creates a remote object or the preceding EJB Remote activity does not release the remote object in the TIBCO BusinessWorks process. BW-EJB : Error occurred while trying to obtain the JNDI Configuration shared resource reference [%1]: %2 Description: Unable to get the shared JNDI Configuration resource referenced by the EJB Connection resource Resolution: Please correct the error and retry.

42 32 Chapter 3 Error Codes BW-EJB : %1 Role: debugrole Description: Debug Trace Message Resolution: None

43 TIBCO Software Inc. End User License Agreement 33 TIBCO Software Inc. End User License Agreement READ THIS END USER LICENSE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THE SOFTWARE, YOU AGREE TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT DOWNLOAD OR INSTALL THE SOFTWARE AND RETURN IT TO THE VENDOR FROM WHICH IT WAS PURCHASED. Upon your acceptance as indicated above, the following shall govern your use of the Software except to the extent all or any portion of the Software (a) is subject to a separate written agreement, or (b) is provided by a third party under the terms set forth in an Addenda at the end of this Agreement, in which case the terms of such addenda shall control over inconsistent terms with regard to such portion(s). License Grant. The Software is the property of TIBCO or its licensors and is protected by copyright and other laws. While TIBCO continues to own the Software, TIBCO hereby grants to Customer a limited, non-transferable, non-exclusive, license to use the Number of Units set forth in the Ordering Document, in machine-readable, object code form and solely for Customer's internal business use. Restrictions. Customer agrees not to (a) make more copies than the Number of Units plus a reasonable number of backups; (b) provide access to the Software to anyone other than employees, contractors, or consultants under written contract with Customer agreeing to be bound by terms at least as protective of TIBCO as those in this End User License Agreement ("Authorized Users"); (c) sublicense, transfer, assign, distribute to any third party, pledge, lease, rent, or commercially share the Software or any of Customer's rights under this Agreement (for the purposes of the foregoing a change in control of Customer is deemed to be an assignment); (d) use the Software for purposes of providing a service bureau, including, without limitation, providing third-party hosting, or third-party application integration or application service provider-type services, or any similar services; (e) use the Software in connection with ultrahazardous activities, or any activity for which failure of the Software might result in death or serious bodily injury to Customer or a third party; or (f) directly or indirectly, in whole or in part, modify, translate, reverse engineer, decrypt, decompile, disassemble, make error corrections to, create derivative works based on, or otherwise attempt to discover the source code or underlying ideas or algorithms of the Software. Customer may engage in such conduct as is necessary to ensure the interoperability of the Software as required by law, provided that prior to commencing any decompilation or reverse engineering of any Software, Customer agrees to it shall observe strict obligations of confidentiality and provide TIBCO reasonable advance written notice and the opportunity to assist with and/or conduct such activity on Customer's behalf and at Customer's expense. Beta and Evaluation Licenses. Notwithstanding the foregoing, if the Software is being provided for demonstration, beta testing, or evaluation purposes, then Customer agrees (a) to use the Software solely for such purposes, (b) that the Software will not be used or deployed in a production or development environment, and (c) that such use shall automatically terminate upon the earlier of thirty days from the date Customer receives the right to install the Software, or Customer's receipt of notice of termination from TIBCO. Maintenance. Provided Customer has paid applicable support fees (not included with Software fees unless separately listed), TIBCO shall provide support for generally available Software ("Maintenance") on an annual basis commencing on the Purchase Date. Thereafter Maintenance will be automatically renewed for successive one (1) year terms at the then current rates. Customer shall designate at TIBCO's support website the number of authorized contacts as permitted by TIBCO based on the level of Maintenance purchased (contacts are changeable upon 48-hours prior written notice to TIBCO). Each contact may contact TIBCO for problem resolution during TIBCO's published support hours corresponding to the level of Maintenance purchased. Upon notice from a contact of a Software problem which can be reproduced at a TIBCO Maintenance facility, TIBCO shall use reasonable efforts to correct or circumvent the problem according to its published maintenance objectives. TIBCO reserves the right to make changes only to the most currently available version. TIBCO will use reasonable efforts to support the previously released version of the Software for a maximum of six months. TIBCO shall have no obligation to provide Maintenance for the Software if (i) used on any computer system running other than the operating system software for which the Software is approved (as set forth in the Software documentation) and licensed hereunder, or (ii) if Customer has modified or authorized a third party to modify the Software. TIBCO shall have no obligation to modify any version of the Software to run with any new versions of any operating system, or any other third party software or hardware. If Customer purchases Maintenance for any Software, Customer must purchase the same level of Maintenance for all copies of the Software for which it is licensed. Maintenance Fees for lapsed Maintenance or the changing of the level of Maintenance shall be mutually agreed upon between Customer and TIBCO. Upgrades, patches, enhancements, bug fixes, new versions and/or new releases of the Software provided from time to time under Maintenance shall be used only as replacements to existing copies, and shall not be deemed to increase the Number of Units, and use thereof shall be governed by the terms of this Agreement, except for the first paragraph of the Limited Warranty and any right of return or refund. Services. Customer may request additional services ("Services") either in an Ordering Document, or by a separate mutually executed work order, statement of work or other work-request document incorporating the term of this End User License Agreement (each, a "Work Order"). Unless otherwise expressly agreed to in a Work Order, all Services and any work product therefrom shall be (a) performed on a time and materials basis, plus meals, lodging, travel, and other expenses reasonably incurred in connection therewith, (b) deemed accepted upon delivery, and (c) exclusively owned by TIBCO (except for Confidential Information of Customer), including all right, title and intellectual property or other right or interest therein. Each Work Order is intended to constitute an independent and distinct agreement of the parties, notwithstanding that each shall be construed to incorporate all applicable provisions of this End User License Agreement. Fees for Services shall be due and payable in United States dollars net 30 from the date of TIBCO's invoice. Limited Warranty. If Customer obtained the Software directly from TIBCO, then TIBCO warrants that for a period of thirty (30) days from the Purchase Date: (i) the media on which the Software is furnished will be free of defects in materials and workmanship under normal use; and (ii) the Software will substantially conform to its Documentation. This limited warranty extends only to the original Customer hereunder. Customer's sole and exclusive remedy and the entire liability of TIBCO and its licensors under this limited warranty will be, at TIBCO's option, repair, replacement, or refund of the