Novell
Integration Manager

6.0 RELEASE NOTES

April 2006

Welcome to Novell^® Integration Manager^TM (Version 6.0). These release notes include the following sections:

Important note about 6.0 documentation	Where to find information about Version 6.0 of Novell Integration Manager
Installing Integration Manager	How to prepare for installing Novell Integration Manager
System requirements	Software and hardware needed to run Novell Integration Manager
What's new in 6.0	New features in Version 6.0 of Novell Integration Manager
What's new in 5.2.1	New features in Version 5.2.1 of Novell Integration Manager
Documentation updates	Updates to the documentation for Novell Integration Manager
Known issues	Known problems with this version of Novell Integration Manager
Problems fixed in Version 5.2	Problems that have been fixed in 5.2, organized by category
Problems fixed in Version 5.2.1	Problems that have been fixed in 5.2.1, organized by category
Problems fixed in Version 6.0	Problems that have been fixed in 6.0, organized by category

Release note updates   To check for updates to these release notes, click here.

Integration Manager Web site   For the latest Integration Manager downloads, discussion forums, news, and information, click here.

Important note about the Version 6 documentation

Most documentation specific to the Version 6 release of Integration Manager is provided in the product release note file (this document). The other Integration Manager online help and PDF files are still primarily at the 5.2 level; they have not been updated to reflect Version 6 product changes (except where noted).

Installing Integration Manager

For a complete guide to installing Integration Manager, see the Novell Integration Manager Installation Guide. Additional notes and updates related to installation are listed below:

• Notes on upgrading from an earlier release of Composer:
• Configuration file issues
• Upgrading from Composer 4.2 to 5.x
• Upgrading from Composer 5.2 to 5.2.1
• Upgrading from Composer 5.2.1 to Integration Manager 6

System requirements

This section describes the software and hardware needed to run Integration Manager:

• Development environment
• Server environment

  Note   Version 5.2.1 of the exteNd Suite supports MySQL Version 4.1.9. Earlier versions of MySQL are not supported.

Development environment

Topic	What's required
Operating system	One of the following: SUSE Linux Professional 9 and 10 Novell Linux Desktop 9 Windows 2000 Professional with Service Pack 4 or higher Windows XP Service Pack 2
Minimum RAM (memory)	512 MB (1 GB or more recommended)
Disk space	300 MB. NOTE: Install may take up to 2.0 GB in temporary storage.
Display mode	True Color (32-bit), 800 x 600 or higher (1024 X 768 minimum recommended)
Java 2 JRE (Java Runtime Environment)	One of the following, included with Integration Manager:: Linux: JRE 1.4.2_03 Windows: JRE 1.4.2_03-b02
Web browser	One of the following: Firefox 1.0 or higher Mozilla 1.6.x or 1.7 Internet Explorer 6 SP1

Server environment

Topic	What's required
Operating system	One of the following: SUSE LINUX Enterprise Server 9 (Service Pack 1) Novell Open Enterprise Server Open Enterprise Server (v1 Service Pack 2) Red Hat Enterprise Linux 3.0 or 4.0 Windows 2003 Server Windows 2000 Server with Service Pack 1 or higher Solaris 9 and 10
Application server	One of the following: JBoss Application Server Version 4.0.3 Novell exteNd Application Server Version 5.2.1 BEA WebLogic Server Version 8.1, Service Pack 4, or Version 9 IBM WebSphere Server Advanced Edition Version 5.1 or 6 Jakarta Tomcat Version 4.1 or 5.0
Database support	One of the following: Oracle 9i or 10g IBM DB2 8.1 or 8.2 Microsoft SQL Server 2000, 2003, or 2005 MySQL 4.1.9 or 5.0 Sybase Adaptive Server Enterprise (ASE) 12.5
Web browser	One of the following: Internet Explorer 6 SP1 (recommended) Firefox 1.0 Mozilla 1.6.x or 1.7
Minimum RAM (memory)	1 GB (2 GB or more recommended)
Disk space	55 MB
Java 2 JRE (Java Runtime Environment)	One of the following: Linux: JRE 1.4.2_03 Windows: JRE 1.4.2_03-b02 Solaris: JRE 1.4.2_03

What's new in 6.0

For information about new 6.0 features, see What's New in the Integration Manager help.

What's new in 5.2.1

This section describes the new features that were added to the product in version 5.2.1:

Service Profiling

Integration Manager includes a new service profiling feature that, when used in conjunction with Novell Customer Support, provides timing statistics to help diagnose and resolve issues such as memory leaks, bottlenecks, threading issues, and other problems. Service profiling can be used with Servlet and SOAP service triggers, and can be enabled using the Enable Profiling check box on Servlet or Soap HTTP service trigger property sheets. Profiling data is captured and stored in XML format in the following directories:

• JBoss: /server/nim/profiles
• ExteNd application server: /exteNd5/AppServer/Composer/profiles
• WebLogic 8.1: /weblogic81/Composer/profiles
• WebSphere: WebSphere/AppServer/Composer/profiles
• Tomcat: tomcat/Composer/profiles

NOTE: Enabling service profiling will decrease performance, and should only be used for debugging purposes with the assistance of Novell Customer Support personnel.

Tracing

Integration Manager includes a new TCP tracing feature that, when used in conjunction with Novell Customer Support, collects connection data that can be used to diagnose and resolve performance issues relating to connections. You access this feature by selecting Tracing from the Tools menu. This feature is designed to be used for debugging purposes with the assistance of Novell Customer Support personnel.

Documentation updates

The following updates apply to the documentation and help for Integration Manager:

Modifying Servlet type of previously deployed servlet   Under certain circumstances changing Servlet types of an already deployed application causes errors during server import/build.

Help for Save Project As… Command  If you select File > Save Project As, then select the Help button in the Save Project As dialog box, a help file is displayed that describes how to work with projects, but does not provide specific help for the Save Project As command. For information about using the Save Project As command, follow the steps given in the online help in the topic titled "Creating a New Project", starting at step 2 in the procedure. (TDR6978)

Known issues

The following is a summary of current known issues with exteNd Composer. Note that you may encounter other issues; check the release note updates for more information.

• Common issues
• XML Mapping and Action issues
• Linux designer issues
• JDBC Connect issues
• Animation issues
• WSDL issues
• Subproject issues
• Deployment issues
• Configuration file issues
• NTLM authentication issues
• Application server issues
• 3270 Connect issues
• 5250 Connect issues
• CICS/RPC Connect issues
• Data General Connect issues
• EDI Connect issues
• HP3000 Connect issues
• HTML Connect issues
• JMS Connect issues
• PeopleSoft, Siebel, JD Edwards, Lawson, Oracle Applications, and Baan Connects issues
• Business Process Manager (BPM) issues
• SAP Connect issues
• T27 Connect issues
• Tandem Connect issues
• Telnet Connect issues
• UTS Connect issues
• Upgrading from Composer 4.2 to 5.x
• Upgrading from Composer 5.2 to 5.2.1
• Upgrading from Composer 5.2.1 to Integration Manager 6
• MySQL Issues
• Multiple entries for Hospital Project in Recent projects list
• Expired Composer Enterprise Server License issues
• Firefox and Mozilla browser with Process Console issues
• Sample Projects Issues
• Registry Browser Issues
• Using JNDI and CORBA factory classes in Composer Designer issues

Common issues

• Deleting WSDL Resources   After deploying a project with a SOAP Service Trigger and its associated WSDL resource chosen in the deployment panel, if you delete the WSDL resource of the service and again deploy the project using all the same values (including the WSDL resource associated with the SOAP trigger), deployment does not provide an error or warning that the WSDL no longer exists. If accessing the service via a browser the user will receive an error saying, "Unable to retrieve the contents of the resource".
  
  
• Incorrect Help page   When using the Help button (or F1 key) in a dialog, the browser may sometimes open the help page at the wrong location. If this happens, go back to Integration Manager and click the dialog's Help button (or F1) again. The Help page should open at the correct location on the second try. (TDR6988)
  
  
• XForms are not supported on WebSphere 4.0.x or exteNd 4.0.x.
  
  
• XForms on WebLogic 6.1   To make XForms work on WebLogic 6.1, the startup command file for WebLogic 6.1 must be changed to have xalan.jar preceding the WebLogic classpath.
  
  
• Modifying Log level from runtime console   Changing the log level from the Integration Manager Console does not take affect until after the server has been started.
  
  
• Retrieving stylesheets from authentication server   Retrieval of an XSL stylesheet from an authentication server will fail with the following exception:

com.sssw.shr.aghttp.AgoLoginCancelledRuntimeException: Authentication cancelled

It is possible if you have the embedded instruction and return XML, thus leaving the browser to render the stylesheet. This assumes that the browser in use can provide this support.



• Browsing for XHTML Image source throws ResourceSet error   Using the XForms Editor in Composer, one is unable to browse to an image. note - setting a valid image URL works, this is merely a browse to problem. (TDR7545)
  
  
• Browser that is used to launch deployment is the system default   not the browser that is specified in Tools/Preferences. (TDR7473)
  
  
• Running a Soap server in a cluster or behind an iChain security solution  

  The service location in the WSDL returned by the SOAP HTTP trigger is always the URL in the servlet request. When a proxy is used, this location may be different than the client needs. In order to accommodate this situation, an INIT param or a context param can be placed in the web.xml that defines the SOAP HTTP trigger servlet to indicate the server and port to return to the client. For example, to override the request's server and port with "my.server.com:8080", add the following in the web.xml of the WAR that has the SOAP trigger:
  
  <init-param>
  <param-name>overrideServerNameAndPort</param-name>
  <param-value>my.server.com:8080</param-value>
  </init-param>
  This snippet belongs in the <servlet> tag for <servlet-class>com.sssw.b2b.xs.soap.GXSJWebSoapServer</servlet-class>
  
  To make a change for ALL SOAP triggers in that WAR, add:
  <context-param>
  <param-name>overrideServerNameAndPort</param-name>
  <param-value>my.server.com:8080</param-value>
  </context-param>
  at the top of the web.xml before the first <servlet> tag.   (TDR7378)
  
  

• Printing a Component produces blank pages   It is not possible to print with the Navigator and Output tabs hidden. If you attempt to print with the Navigator and Output tabs hidden, blank pages will be printed.
  
  
• Creating functions with same name   Composer will allow you to create Functions with the same name within different Script files. Only the first one created can be made public.
  
  
• Temporary DOMs   When creating temporary DOMS within an XML map component, there are certain reserved words that cannot be used to name a DOM. Using these reserved words as a Temporary Document or Alias names may cause improper results. For example if you name a Temporary Document "Math " you will be unable to use the Math methods (e.g., sqrt).
  
  
• Integration Manager reserved words should not be used in Components or Services   Do not use the words Input, Input1 -- Input(n), Output, Output1 -- Output(n). These are Integration Manager-reserved words.
  
  
• Code Table Resources   If you copy four columns of data (for example, from Excel) and try and paste them into a three column code table, the first three columns will be pasted without presenting a message that the fourth column is being truncated.
  
  
• Validation of new sample document   Validation is required after loading a new Sample document in Integration Manager.
  
  
• Validation of multiple samples   A user may have an Input DOM whose XML Template contains two or more Sample XML documents. When a component is first opened the default Sample is loaded and then validated against its Schema or DTD. If the user subsequently selects "File | Load XML Sample", the new Sample is not validated. This can cause some Schema features and DOM methods, such as the DOM method getElementByID(), to not work.

  Workaround: To solve the problem the user needs to load the sample then validate the DOM by right-clicking on the DOM and selecting "Validate".

  
  
• WSDL Resources are required for Web Service Interchange   The Web Service Interchange action requires a WSDL before you can create a Web Service Interchange action. If you attempt to create a WS Interchange action and no WSDL resources exist, a message is displayed that warns you that you must create a WSDL resource first. If WSDL resources do exist and you create a WS Interchange action, then delete all WSDL resources, you will be unable to edit the existing action.

  Workaround: Create a new WSDL resource and then edit the action.

  
  
• WS Interchange fails on Red Hat with a whitespace error   This bug is due to WSSDK using a newer version of javax.xml.soap interface than is in the classpath of a WebSphere 5.0 install on Red Hat. It is using a getDocument method on SoapElement, which does not exist in the interface in the classpath. (TDR7599)

  Workaround: To workaround this problem, copy the saaj-api12.jar file from {WebSphere Directory}/composer/lib/ to the appServer/java/jre/lib/ext directory.

  
  
• Menu rendered improperly   There is a context/right-mouse-click menu painting problem that sometimes causes the context menu to appear with tooltip content instead of menu commands.
  
  
• UDDI Registry Browser with proxy server   The UDDI Registry Browser is unable to communicate via a proxy server. XML Interchange, Web Service Interchange, and, if installed, Composer HTML Connect use the proxy server settings under Tools, Configuration.
  
  
• ECMAScript keywords that may not be used as identifiers in ECMAScript programs  

  break	else	new	var
  case	finally	return	void
  catch	for	string	while
  continue	function	switch	with
  date	If	this
  default	In	throw
  delete	instanceof	try
  do	math	typeof

  
  

XML Mapping and Action issues

• Elements with text node separated by child elements   If an XML element has text separated by child elements then only the last portion of the text will be displayed in the Input DOM window within Composer. However, if you Map the element, all portions of the text will be seen in the resulting Output DOM element. In the XML fragment below, the MYELEMENT data is separated by CHILDELEMENT. This is a valid XML content model. Composer will only display "for myelement" however, mapping MYELEMENT will transfer "this is data for myelement" .

  <MYELEMENT>

  this is data

  <CHILDELEMENT>

  child data

  </CHILDELEMENT>

  for myelement

  </MYELEMENT>

  
  
• Map Action Content Editor   In the Map Action content editor you cannot select text that is not displayed on the screen. The user can select the "Modify" button and manually set the boundaries of the area desired.
  
  
• Repeat for Element defaults to incorrect Message Part   In the Repeat for Group action the target source is defaulted to Input rather than Output.

  Workaround: Select the correct source, either a Temp or Output DOM.

  
  
• Large DOM trees   When editing data in a very deeply nested tree within a DOM the edit dialog box sizes larger than the window.

  Workaround: Manually resize the dialog by dragging the edges.

  
  
• Animation within XML Map Component   When running in Animated mode on the XML Map component, Execute is not disabled. For example, go into any XML map and start animation. Press Step Into twice, then choose from the menu (C)omponent (E)xecute. Nothing happens. If you then choose End Animation, you will receive the error message "Error Executing Stop Run" and details will show a Root Exception Stack Trace.
  
  
• Send Mail Action caches the mail server in Designer   In the Send Mail Action, the mail server that is used the first time is used throughout the Composer session. Subsequent Send Mail Actions will ignore the Mail Server entry and use the original one. In runtime, however, switching mail servers is allowed.
  
  
• Web Service Interchange   WS Interchange Header Support: A header may be added via the WS Interchange action however the change is not included in the runtime.
  
  
• Case Sensitivity while calling Components   Integration Manager allows you to call a component without regard for the case of the object name. However if the case is not specified correctly then you will receive a Null Pointer Error during execution on the Server.
  
  
• Filter Document button is not enabled for XML Interchange action   The Filter Document button is not enabled as expected when you create an XML Map component with System Any as the Output Message, and then create an XML Interchange action that gets a file to output. After pressing the Apply button in the XML Interchange dialog box, the Filter Document check box should be enabled, but it is not. To work around this problem, select OK to close the XML Interchange dialog box, then right-click on the XML Interchange action and select Edit Action. The Filter Document check box should now be enabled. (TDR7634)
  
  
• Dynamic Component action is evaluated whenever anything is edited in the Action model  The Dynamic Component action is evaluated any time you edit anything in the Action model. This could cause irrelevant error messages (e.g., a message that reports an undefined variable, when you haven't had the chance to define the variable yet). You may ignore the error message. (TDR7701)
  
  

Linux designer issues

• Show java console preference does not display the java console on Linux   In Linux, Tools/Preferences/display Java Console has no affect. (TDR7562)
  
  
• ExteNd Director will not launch on Linux machine when used as XML editor   In Linux, using the Launch External Editor does not work using the default picked by the installer. (TDR7553)
  
  
• Cannot hit WSDL URI from registry browser in Linux   The following error is thrown...browser.java.io.IOException-java.io.IOException:"/opt/kde3/bin/konqueror". not found. (TDR7551)
  
  
• F1 key displays incorrect help topic   Pressing F1 key for context-sensitive help in Designer on SUSE displays an incorrect help page. (TDR7521)
  
  
• Search within Help system   From within the Help system (F1 key), if one clicks on the Search tab, a find dialog box should appear. This feature works properly in Mozilla, but not with Galeon or Konqueror. (TDR7603)
  
  
• Konqueror only shows XForms labels   XForms are only supported on Internet Explorer and Mozilla. They may not render correctly on other browsers, such as Konqueror. (TDR7497)
  
  
• Deployment of Integration Manager project using Konqueror browser fails   Deployment using Konqueror browser is not supported in this release. You can deploy using the Mozilla browser. (TDR7776)
  
  
• Out of Memory error when executing a service on Linux   (TDR7322)
  
  
• Project variables lost when upgrading project  When upgrading a project under Linux, rename the project.xml file to PROJECT.xml before performing the conversion. Otherwise, all project variables will be lost. (TDR7499)
  
  
• Process Manager does not work after installation on SLES9   In some cases, when installing Integration Manager on SLES9, the installation of Process Manager fails (when the application server starts, you’ll see a message indicating that the "Process Database" was not found). To work around this problem, you can use the application server's management console to create the pools that were not created during the installation (see "Configuration and Setup" in the Process Manager User's Guide). To create the pools using the exteNd application server management console:
  1. Start the Server Management Console.
  2. Click on "Pools".
  3. In the Pools list, click on JDBC.
  4. Select Add.
  5. Select "MySQL" from the Database Platform list.
  6. Use "Process50" as the Pool Name.
  7. Use one of the following for the JDBC URL:
  • jdbc:mysql://127.0.0.1:63306/process50?profileSql=false&maxRows=0
  • jdbc:mysql://:63306/process50?profileSql=false&maxRows=0
  8. Add another pool, this time using "Samples50" as the Pool Name.

  PPR48892,TDR7785

  
  
• Right-click on Form Resource Does not display menu on SLES9   If you click the right mouse button on a Form resource while using Integration Manager on SLES9, the context-sensitive menu is not displayed. You can work around this by selecting the item that you want to edit with the left mouse button, and then selecting the desired editing commands from the Edit or Form Designer menus. (TDR7800)
  
  

JDBC Connect issues

• Special characters returned by SQL query   If a JDBC query returns certain unprintable characters, this can cause the creation of an invalid XML document. To workaround this problem, preprocess any documents containing this type of information before writing out the XML document.

Note:   Integration Manager DOES handle and convert all XML reserved characters.



• Drag and drop in SQL Native Interface Panel   Commas are not added after each value when dragging them into the SQL statement.
  
  
• Menu item 'EDIT' doesn't work   In the JDBC component selecting the Action Menu Item "Edit" on a SQL Statement Action does not trigger any event. This is because the SQL action is edited in the Native Interface panel that is already displayed.
  
  
• Tables are listed regardless of access rights   When using the Novell Oracle Driver the user is presented with a list of all tables in the database even if you do not have access to them. This is due to the driver not filtering the list.
  
  

Animation issues

• Caching of resources   Integration Manager caches resources during animation. To be sure that you are executing updated components always save, close and reopen Objects prior to retesting.
  
  
• Stop button does not work   During animation, the STOP button does not work during run to the end.  When running to a break point, first press Pause to stop the animator then press STOP.
  
  
• Hourglass not displayed when running to breakpoint   An hourglass is not displayed when running to breakpoint. This does not cause any problems in the execution but may be confusing to the user.
  
  
• Setting breakpoints on conditional actions   Integration Manager allows you to set a breakpoint on the action blocks just below a conditional action (TRUE, FALSE, ON ERROR) however the breakpoint has no effect. However placing a breakpoint on the conditional action (IF, TRY) itself works fine.
  
  
• Animation does not stop at breakpoint of a called service   For example, set a breakpoint in a called service. Start animation in the parent (or using) service. Click on "Run to Breakpoint/end". You never hit the breakpoint set in the called service.
  
  

WSDL issues

• Correcting the type attribute for Response parts   WSDL generation for Complex RPC SOAP Web Services incorrectly declares the type attribute for Response parts. To correct this, a namespace prefix needs to be added to the type name, and the namespace declaration using this prefix must be declared in the WSDL definition. (TDR 7609)
  
  
• Web Service Interchange calling Integration Manager SOAP service   If you have WS Interchange actions that access other Integration Manager SOAP services, they will need to update those actions manually to map any SOAP Fault messages. This is done on the Messages tab of the WS Interchange action after acquiring the 5.2 updated WSDL for their old Integration Manager SOAP Service.
  
  
• Optional MIME Content Type   The WSDL spec allows a MIME part to not specify a specific content type by making the <mime:content type> attribute optional. What this means for a service is that it can accept MIME attachments of any type. Thus, a client calling this service is free to send attachments of any type.

  The WS-Interchange action currently does not support WSDLs in which this attribute is omitted. Since a specific content-type is not specified it does not know what type to send, and therefore throws an exception when the action is executed.

  Workaround: Since Integration Manager does not allow a user to specify the attachment content type, any WSDL that is used in conjunction with WS Interchange MUST have the content type specified for the message part.

  
  
• Error when opening WSDL created in previous version of Integration Manager   In Integration Manager, when opening a WSDL created in a version of Composer prior to 5.0 (for example, Composer version 4.2), you may receive the following error:

  Fatal Error! At Line: 230 Column: 50 Datatype error: Value '""' is a Malformed URI. 

  Prior to version 5.0, Composer used WSDL 1.0. Composer version 5.0 and higher uses WSDL 1.2. The error message, above, provides information only; it does not affect execution. The error message correctly indicates that a WSDL 1.0 WSDL does not pass WSDL 1.2 validation.

  
  
• WSDL definitions must contain a name attribute   All WSDL definitions must contain a "name" attribute. When creating a new WSDL file that is NOT associated with an existing Integration Manager Web Service, you must define a "name" attribute on the "definitions" element whose value is identical to the WSDL xObject name. This is the name you supplied on the first wizard panel at creation time in place of the text "untitled". Failure to do so will result in the WSDL object not being saved and work can be lost. So if you are writing WSDL from scratch in Integration Manager or copying WSDL in from an external source, be sure to define a "name" attribute.

  Integration Manager Compliant:

  <definitions name="MYWEBSERVICE" targetNamespace="http://www.mybiz.com/mywebservice/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">

  WSDL Compliant (this is valid WSDL but not sufficient for Integration Manager):

  <definitions targetNamespace="http://www.mybiz.com/mywebservice/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">

  
  
• RPC Binding can contain only simple message parts   The message portion of the WSDL file can only contain message parts that are simple types. Complex types are not currently supported.
  
  
• RPC Binding - namespaces   Integration Manager templates that are used to generate the input and output messages will have any namespace declarations ignored. The method portion of the Soap body will contain a default namespace based on the namespace attribute found in the "/definitions/binding/operation/input/soap:body" WSDL node. You should endeavor to keep template definitions free of any namespace declarations, or revisit them and ensure they match the namespace used in the WSDL.
  
  
• RPC Binding - generating from undefined templates   It is not possible to generate WSDL documents for Integration Manager services that use input or output documents that have a category of {System} and a template name of {Any}.
  
  
• RPC Binding - QName   When creating a new WSDL resource, use a valid QName at http://www.w3.org/XML/Schema.
  
  

Subproject issues

• Relative path checkbox   When a subproject is added, if the path name of the subproject includes a lowercase drive letter (e.g. d:\project1.spf rather than D:\project1.spf) the Relative check box does not work.
  
  
• Subprojects containing Process components fail to load   When attempting to execute a Process which exists in a subproject, the following message appears...

   - <ERROR> 
  
  <TITLE>Composer Service Trigger Error</TITLE> 
  
  
  <DESCRIPTION>While processing the input request for an Composer
  service trigger, a problem occurred. The following error will indicate
  where the error occurred and should provide clues as to how to fix the
  problem.</DESCRIPTION> 
  
  - <EXCEPTION> 
  
  - <![CDATA[ 
  
  com.sssw.b2b.xs.GXSException: Composer Exception caught while executing
  the service main project uses subproject templates; 
  
          ---> nested
  com.sssw.b2b.ee.process.rt.GNVProcessException: Dynamic creation of the
  XObject factory failed:
  
  
  com.sssw.b2b.xs.GXSException - GXSBaseFactory: Unable to create the
  Composer object factory with the context 'ActionExamples', for the
  object store driver 'EJB_DRIVER' due to an exception:
  
  com.sssw.b2b.rt.GNVException - Exception occurred while instantiating
  the XObjectStore driver: EJB_DRIVER
  
  com.sssw.b2b.rt.GNVException - Unable to set the initial context
  'ActionExamples' due to the following exception:
  
  com.sssw.b2b.rt.GNVException - Error while retrieving the resource
  bean's home interface for JNDI name
  'RMI/com/sssw/b2b/xs/ostore/ActionExamples/ResourceBean':
  
  javax.naming.NameNotFoundException - null
  
  ]]> 
  
  </EXCEPTION> 
  
  </ERROR>

  Workaround: Place Process in main project. (TDR7493)

  
  

Deployment issues

• Modifying servlet type of previously deployed servlet   Under certain circumstances changing Servlet types of an already deployed application causes errors during server import/build.
  
  
• Tomcat   The Tomcat deployment JSP tells you to select the EAR file; Integration Manager actually deploys a WAR file.
  
  
• Deploying a Process (BPM)   Deploy fails when a web service calls a process with multiple inputs.
  
  
• Deploy status is cached from previous deploy   Due to browser refresh problems, sometimes deploying a second time, the browser does not refresh -- instead, it will show the previous deployment completed screen. To workaround this problem, if using Internet Explorer, select Tools, Internet Options, Temporary Internet files, Settings, and change the "Check for newer versions of stored pages" to "Every visit to the page."
  
  
• Deploying with EJBs   Every time a deploy is done and there is an EJB the following message appears in the Integration Manager dialog. The warnings are displayed due to EJB 1.0 compliant method signatures that report exceptions that are no longer advised in the EJB 2.0 specification.

  Validation of GXSEEJBResource in <jar> deployed WARNING
  Remote home interface: com.sssw.b2b.xs.ostore.IGXSEJBResourceHome
  Remote interface: com.sssw.b2b.xs.ostore.IGXSEJBResource
  Bean class: com.sssw.b2b.xs.ostore.IGXSEJBResourceBean
  -W throw clause for 'getResource' should not include
  java.rmi.RemoteException - (EJB 2.0 spec -7.1-.4) 

  
  
• Deploying JMS Services and Process Components   JMS Services and Process Components must be deployed as J2EE 1.2 to exteNd Application Server 4.0/4.01 if the application server is secured.
  
  
• Incorrect deployment message   A deployment descriptor may report that the deployment succeeded without error even though the deployment log indicates that an HTTP error occurred on the web server.
  
  
• Deployment by multiple developers to WebSphere and WebLogic   Two users should not concurrently deploy to either WebSphere or WebLogic Application Servers. The deployments in this case might not successfully complete.
  
  

Configuration file issues

• Project Names   Anything after a period is truncated from a project name. For example, if you create a new project and call the project "Tutorial(5.2)" and save it, the file will be saved as "Tutorial(5).spf". This is also the name that will appear in the title bar in the Integration Manager Pane.
• Upgrading from previous versions of Integration Manager   If installing Integration Manager on a computer on which Composer had previously been installed, the install program neither reads the existing xConfig nor updates the new xConfig to reflect changes that were made in the previous version. The affected entries which are likely to have been modified are:

  Affected xConfig Entry	Set Method
  XCD_HTTP_HANDLER	Set from the Tools | Preferences dialog.
  OVERWRITELOG	Set from the Tools | Preferences dialog.
  EXTXMLEDITOR	Set from the Tools | Preferences dialog.
  BROWSER	Set from the Tools | Preferences dialog.
  MAXRECENTPROJECTS	Set from the Tools | Preferences dialog.
  RECENTPROJECTSLIST	Set from the Tools | Preferences dialog.
  PROXYSERVERINFO entries	Set from the Tools | Preferences dialog.
  VERBOSE_OUTPUT	Set manually inside xConfig.
  DOUBLEBUFFERING	Set manually inside xConfig.
  PARSER_OPTIM	Set manually inside xConfig.
  VM_PARAMS	Set manually inside xConfig.
  JAR entries	Set manually inside xConfig.

  
  

NTLM authentication issues

• How to configure NTLM authentication with proxy support for Integration Manager Server  

  1. Make your settings in Designer via the Tools | Preferences | Designer tab dialog.

  2. Exit Integration Manager.

  3. Open the xconfig.xml file in the ..\Designer\bin directory and copy the entire <PROXYSERVERINFO> element and all its descendants.

  4. Shut down the application server.

  5. Paste the element into the Integration Manager Server xconfig.xml file in the ..\AppServer\Composer\lib directory. Be sure to place it under the <XCONFIG><SYSTEM> branch.

  6. Restart the application server.

  
  

Application server issues

• Installing on WebLogic   When installing Novell Integration Manager Enterprise Edition to WebLogic, be sure the application server is started in development mode. For more information on this issue, please reference the WebLogic readme.txt file, which you can find in the \config\mydomain\applications directory.

  Note: After restarting the server you must go to the WebLogic server console, navigate to myDomain\Deployment\Web Application and choose a target server for Integration Manager. Then in the general tab check Deployed.

  You will receive the following warning in the WebLogic 8.1 console after restarting App Server.

  <Warning> <HTTP> <BEA-101247> D:\bea_81\user_projects\mydomain\.\myserver\.wlnotdelete\exteNdComposer\exteNdComposer.war: Public

  
  
• Installing on secured WebSphere Application Server   When installing to a secure WebSphere 5.2 server, ensure the Global Security >> Java 2 Security is NOT enabled. If Global Security is enabled the Integration Manager Consoles will fail.

  You may deploy to multiple web applications within a single Application Server in WebSphere as well as multiple EJB Containers.

  
  
• Deploying to a secured WebSphere Application Server   Projects should only be deployed to WebSphere 5.1 with the WebSphere Application Server unsecured. If the application server has Global Security enabled, an exception will occur at the end of the deployment, even if the application is deployed and runs correctly.

  This is the error message:

  GXSDeployHandler.doPost(): ERROR: Exception while performing deployment: Unable to apply deployment changes due to an exception
  com.sssw.b2b.xs.GXSException: Unable to apply deployment changes due to an exception; 
          ---> nested java.lang.Exception: Unable to retrieve variable map attributes due to an exception:
   null
          at com.sssw.b2b.xs.deploy2.ws50.GXSWS50DeployHandler.applyChanges(Unknown Source)
          at com.sssw.b2b.xs.deploy2.ws50.GXSWS50DeployHandler.deploy(Unknown Source)
          at com.sssw.b2b.xs.deploy2.GXSDeployHandler.run(Unknown Source)
          at java.lang.Thread.run(Thread.java:568)

  Once the project is deployed, turn the application server security back on. (TDR7589 and TDR7784)

  
  
• Deploying to a local WebSphere 5 Application Server with no Internet connection  When deploying a Integration Manager project to a WebSphere 5.0 server (locally on same machine) from Integration Manager Designer, and there is no internet connection, an exception occurs:

  Deployment Report:
  Deployment location will be: D:\WebSphere\AppServer\Composer\tmp
  Initializing DOM from deployment JAR descriptor file.
  Performing the deployment.
  Stored the generated EAR file in the following location: D:\WebSphere\AppServer\Composer\staging\BRU-DDP7J-test\BRU-DDP7J-test\deployextend.ear
  GXSDeployHandler.doPost(): ERROR: Exception while performing deployment: Unable to apply deployment changes due to an exception
  com.sssw.b2b.xs.GXSException: Unable to apply deployment changes due to an exception; 
          ---> nested java.lang.IllegalStateException: Unable to install the EAR 'D:\WebSphere\AppServer\Composer\staging\BRU-DDP7J-test\BRU-DDP7J-test\deployextend.ear' as an application
          at com.sssw.b2b.xs.deploy2.ws50.GXSWS50DeployHandler.applyChanges(Unknown Source)
          at com.sssw.b2b.xs.deploy2.ws50.GXSWS50DeployHandler.deploy(Unknown Source)
          at com.sssw.b2b.xs.deploy2.GXSDeployHandler.run(Unknown Source)
          at java.lang.Thread.run(Thread.java:512)

  To work around this problem, deploy the project from the application server deployment console. (TDR7636)

  
  
• Deployment from Integration Manager Designer to WebSphere 5.1 with latest Fixpack fails   Integration Manager deploys projects without error to WebSphere 5.1. However, if you deploy a project to WebSphere 5.1.1 or 5.1.1.2 (base WebSphere 5.1 with Fixpack 1 or 1.2), you receive the following error:

  Deployment Report:
  Deployment location will be: D:\servers\WebSphere\AppServer\Composer\tmp
  Initializing DOM from deployment JAR descriptor file.
  Performing the deployment.
  Stored the generated EAR file in the following location: D:\servers\WebSphere\AppServer\Composer\staging\dot-net\dot-net\my.ear
  GXSDeployHandler.doPost(): ERROR: Exception while performing deployment: Unable to apply deployment changes due to an exception
  com.sssw.b2b.xs.GXSException: Unable to apply deployment changes due to an exception; 
          ---> nested java.lang.IllegalStateException: Unable to install the EAR 'D:\servers\WebSphere\AppServer\Composer\staging\dot-net\dot-net\my.ear' as an application
          at com.sssw.b2b.xs.deploy2.ws50.GXSWS50DeployHandler.realApplyChanges(Unknown Source)
          at com.sssw.b2b.xs.deploy2.ws50.GXSWS50DeployHandler.applyChanges(Unknown Source)
          at com.sssw.b2b.xs.deploy2.ws50.GXSWS50DeployHandler.deploy(Unknown Source)
          at com.sssw.b2b.xs.deploy2.GXSDeployHandler.run(Unknown Source)
          at java.lang.Thread.run(Thread.java:567)

  You will also also see an error in the WebSphere Systemout.log similar to "warning from EJBDeploy invalid type of DB vendor [severity 2]".

  This problem is due to a known bug in the Fixpack (see http://issues.apache.org/bugzilla/show_bug.cgi?id=33031). We recommend that you do not apply this Fixpack. If you must apply the fixpack, or if it is already applied, create the archive manually, using the Archive Project command on the File menu (see "Creating EAR, WAR, and JAR Archives" in the Novell Integration Manager User’s Guide). Once you have created the project archive, deploy the archive using the WebSphere administrative console. (TDR7810)

  
  
• Installing on WebSphere Network Deployment Product   Make sure the Deployment Manager and Application Servers are running.

  1. Install the Integration Manager Enterprise Server following the instructions in the Integration Manager Installation Guide.

  2. Open a command-line window and execute the '{WebSphere_Home}/Composer/bin/xcs-portviewer' batch file. This will display the RMI ports for all of the servers registered with the deployment manager.

  3. For each detail section from step 2, pertaining to a Type of 'APPLICATION_SERVER', please note the following pieces of information (Case is important):

      a) The node name.

      b) The server name.

  4. For the section from step 2 that signifies the 'DEPLOYMENT_MANAGER', please note the following pieces of information:

      a) The host.

      b) The RMI port.

  5. Copy the Composer folder into the WebSphere_Home directory on each managed server within the network topology.

  6. On each of the Servers (SRV), run the '{WebSphere_Home}/Composer/bin/xcs-nd-install' batch file. You will need to supply the connection type, host and RMI port of the Deployment Manager (DMG) when executing the batch file, using the following syntax:

      xc-nd-install RMI <DMG_HOST> <DMG_PORT> install <SRV_NODE>

      <SRV_SERVER> <Composer_App_Name>

      where:

      DMG_HOST – The deployment manager host name.

      DMG_PORT – The deployment managers RMI port.

      SRV_NODE – The node name of the APPLICATION_SERVER.

      SRV_SERVER – The server name of the APPLICATION_SERVER.

      Composer_App_Name – The name for the Integration Manager Console application to be installed on the APPLICATION_SERVER.

  
  Note: All Host, Node, and Server names are case sensitive

  
  Note: The 'Composer_App_Name' must be unique for each iteration of step 6. This is to ensure that an Integration Manager console is available on each of the servers that has the Integration Manager binaries installed. We recommend that you add the Node and/or the server name to the 'ComposerConsole' suffix.

  
  7. Restart the Application Servers

  
  Accessing the Integration Manager Consoles on the WebSphere Network Deployment Product:

  On the application server: http://{App_Server}:port\exteNdComposer\Console. Cannot access the Integration Manager Consoles on the Deployment Manager.

  
  

  How to Deploy Integration Manager Web Services on the WebSphere Network Deployment Product:

  Archive the Integration Manager Project.

  Manually deploy the EAR from the Deployment Manager to the desired App Server.

  
  
• WebSphere Manual Uninstall Procedure  

  In the WebSphere Administration Console, find the Application Server where Integration Manager is installed. Within the Application Server, there is a Servlet Engine that hosts the available web applications on that particular Application Server.

  Within the Servlet Engine there should be an Integration Manager web application. Shut down the current Application Server and remove the Integration Manager Web Application and its contents.

  Under the Application Server, remove the command line arguments that reference Integration Manager. The command line arguments can be accessed by clicking on the Application Server in the WebSphere Administration console and should be visible from the default tab.

  Remove the Dependent Classpath associations that exist under the core node in the Administration Console under the default tab (General).

  Remove the Integration Manager folder from within the WebSphere parent directory (WebSphere/AppServer/Integration Manager).

  Note: When removing the Integration Manager folder be sure that all Application Servers are shutdown from within the WebSphere Administration console. The NT service does NOT need to be stopped to remove the Integration Manager folder from the WebSphere parent directory.

  
  
• Process fails when used with ServiceProviders on WebSphere   A Process may fail when used with ServiceProviders on WebSphere, with an error message similar to the following:

   <ERROR> <TITLE>Composer Service Trigger Error</TITLE><DESCRIPTION>While processing the input request for an Integration Manager service trigger, a problem occurred.  The following error will indicate where the error occurred and should provide clues as to how to fix the problem. </DESCRIPTION> <EXCEPTIO ><![CDATA[com.sssw.b2b.xs.GXSException: Composer Exception caught while executing the service PriceQuotesStaticLocator; 
          ---> nested com.sssw.b2b.rt.GNVException: <?xml version="1.0" encoding="UTF-8"?>
  <FaultInfo>
   <MainCode>-1</MainCode>
   <SubCode>1</SubCode>
   <Message>1 rtPROCESS014006:Error encountered executing Web Service Send
  2 Nested Message: rtPROCESS014002:Error encountered executing SOAP Request:
  3 Nested Message: com/sssw/jbroker/web/portable/Stub</Message>
   <ProcessId>28</ProcessId>
   <ActivityName>BCompanyQuote</ActivityName>
  </FaultInfo>
  ]]></EXCEPTION></ERROR
  

  To work around this problem, add the line 'security.provider.6=cryptix.jce.provider.CryptixCrypto' to the %WAS_HOME%\AppServer\java\jre\lib\security\java.security file. This adds the Cryptix security provider to the runtime environment. (TDR7809)
  
  
• JSP exception when starting Process engine on WebSphere using DB2 8.2   You may receive the following error message when starting the Process engine on WebSphere using DB2 8.2

   ExecuteTag: Composer Exception caught while executing the service ProcessMain
          at com.sssw.b2b.xs.tl.ExecuteTag.doEndTag(Unknown Source)
          at org.apache.jsp._ProcessMain._jspService(_ProcessMain.java:257)
          at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java(Compiled Code))
          at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
          at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java(Compiled Code))
          at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java(Compiled Code))
          at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java(Compiled Code))
          at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
          at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java(Compiled Code))
          at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java(Compiled Code))
          at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java(Compiled Code))
          at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java(Inlined Compiled Code))
          at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java(Compiled Code))
          at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java(Compiled Code))
          at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java(Inlined Compiled Code))
          at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java(Compiled Code))
          at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java(Compiled Code))
          at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java(Compiled Code))
          at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:125)
          at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:286)
          at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
          at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:116)
          at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java(Compiled Code))
          at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java(Compiled Code))
          at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java(Compiled Code))
          at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Compiled Code))
          at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:449)
          at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))

  When configuring the Process Engine Database using DB2 8.2, the Application server needs to be restarted after initializing the Process database and prior to starting the Process Engine. Otherwise a JSP exception will appear in the browser when starting the Process Engine. (TDR7812)

  
  
• Deploying to JBoss   When deploying to JBoss on Windows and using a relative path to specify the Staging Directory, you will not receive a message that the deployment is complete (although the deployment will complete). As a best practice, do not use a relative path when specifying the Staging Directory. Use only absolute paths. (TDR7739)
  
  
• JNDI Lookup Fails for JMS Connection Factory using JBoss application server   The Integration Manager JAR resource creates a temporary JAR file in the Designer/tmp directory. An exception can occur when the client code in the JBoss jbossall-client.jar attempts to perform file I/O on the temporary JAR file, and a space exists in the path to the Designer/tmp directory. You can use either of the following methods to work around this problem:
  • Add the jbossall-client.jar file to the Integration Manager design time classpath by editing xconfig.xml, and to the runtime classpath by editing the application server AgJars.conf file.
  • Make sure that there are no spaces in the full path to the Designer/tmp directory.

  (TDR7795)

  
  
• Native binaries for DG, HP3000, and Tandem connectors are not installed on the application server   Native binaries are never installed to the application server with Integration Manager Server installs. Native binaries are installed with Integration Manager Designer, in the /Composer/Designer/bin directory. (TDR7071)
  
  

3270 Connect issues

• Consoles on WebSphere   If you deploy Integration Manager service components to more than one WebSphere application server you will need to copy the Integration Manager consoles for 3270 Connect, 5250 Connect, Telnet Connect, Data General Connect, HP 30000 Connect, Tandem Connect, UTS Connect and SAP Connect to each application server. This will allow you to monitor the various Integration Manager Connector connection pools for the specific application servers.

  Instructions that describe how to copy these Integration Manager Consoles are available for from the Integration Manager Product Download section on www.Novell.com. Also included in this download is a new file called exteNdComposerConsoles.ear, which is required.

  
  
• Connection Pools   It is possible for two different deployed projects to have the same connection name (pooled) specified, in which case one component in one project may call into the connection pool of the project erroneously.

  Workaround: To avoid this problem make sure all connections are uniquely named.

  
  
• Help System   If you have both 3270 and 5250 Connectors installed, selecting Help Topics (F1) from the menu in 3270 Connector will display 5250 help documents. This happens on the main windows for 3270 and 5250, the Stylesheet editor dialogs, and the MultiRow wizard and dialogs.
  
  
• MultiRow Wizard   When creating a MultiRow Action if you do not walk through each panel of the wizard the MultiRow action will be created incorrectly
  
  
• Disconnect button does not work with EPI Connection   Within the 3270 Component there exists a connect/disconnect button for an existing Terminal or EPI connection. The disconnect for the terminal connection works as expected, but the disconnect for an EPI Connection will not release the Gateway connection until the Component window is closed using the Windows Task Manager to kill the process. The EPI disconnect will in fact hang the Integration Manager application, but if the user can wait long enough the connection will time out after 7 - 10 minutes.
  
  
• Connection object information is cached   If you change the Logon or Password of a 3270 component, then immediately run the component, you'll find that the logon or password change has not taken affect. To work around this problem, close, then reopen the component.
  
  
• Connection Resources located in Subprojects   When using the Pre-initialize Pool feature, if you are using a connection from a sub-project, the connection name that should be used is the original and not the shared connection name (i.e., TutorialEnd:InventorySystem.xml vs. InventorySystem.xml).
  
  
• Importing Components from other projects   Importing a 3270 component will fail if the connection does not exist.

  Workaround: Import the connection first, then import the component.

  
  
• The 3270 and 5250 Open Console buttons are not displayed on Integration Manager Server console when using Mozilla Firefox browser.   The 3270 and 5250 Open Console buttons are not displayed in the Integration Manager Server console when you are using the Mozilla Firefox browser. To work around this issue, select the link for 3270 or 5250 in the About Products list, and use the Console button on the About page that is displayed. (TDR 7808)
  
  

5250 Connect issues

• Consoles on WebSphere  
  
  
• Connection Pools  
  
  
• Importing Components  
  
  
• No Open Console button in Mozilla Firefox  
  
  

CICS/RPC Connect issues

• Designer  

  The RPC test connection button does not verify the region.

  The STOP button does not work during run to the end animation. When running to a break point, first press Pause to stop the animator then press STOP.

  
  
• X-Windows system  

  Solaris Note:  Please be aware that there are issues with running the CICS transaction gateway on Solaris. The following text is taken from the documentation for the IBM CICS transaction gateway:

  "When using X-Windows from a remote system, for example, to access the configuration tool and iKeyman, you must set up the DISPLAY environment variable to allow the application to display its windows on that system.

  On the display system (that is one that will display the windows), enter the command:

  xhost +appl

  where appl is the network name of the system being used to run the application.

  On the application system, before you run the application, enter the command:

  DISPLAY=disp:0

  followed by

  export DISPLAY

  where disp is the network name of the system where the windows will be displayed (followed by a colon and the display ID - normally 0). The application windows are then displayed on the disp system".

  
  

Data General Connect issues

• Consoles on WebSphere  
  
  
• Connection Pools  
  
  
• Importing Components  
  
  

EDI Connect issues

• Apply button in Map Action does not work   Pressing Apply in the Map dialog does nothing. The action only takes effect if you press Apply and then press OK. Pressing OK without pressing Apply first, does nothing (as it should).
  
  
• New feature for processing inbound EDI with errors  In release 6.0 we've added an option to continue to process inbound EDI, even if errors exist. You can now choose to ignore (skip) errors detected by the EDI parser. If an error is encountered, instead of throwing an Integration Manager error, the description of the error is re-directed to a new element/attribute, and processing continues. The result is that the parser converts the EDI Document to XML, and you can then determine how to handle the error in question.

  For example, a single EDI document might contain 100 repeating segments (one doctor / 100 patients). Let's say that a few of the patient Segments contain data that is either an invalid length, or an invalid code (according to the Integration Manager metadata). In previous releases, the entire document would fail and none of the patient records would be processed (the EDI document will not be converted to XML at all). In this release, an XML document will be produced. Immediately after an error is detected, Integration Manager creates a new element called <EDISkipError>. The new element contains an attribute named "ParseError" which describes the error (as you would currently see in your ERROR log). In our example, you would have a loop on the Patient segments. You can now use xpath to determine if any child elements contain an attribute named "ParseError". If the attribute exists, you can choose to Continue to the next patient segment, log the error(s) and/or write the XML segment to disk.

  To enable this new feature, you must modify the xconfig.xml file (both design and runtime). The following is an example of the modification required to enable the new feature, as well as a sample snippet of a Temp DOM created from an EDI Document with errors.

  The following new line (displayed in bold text) should be inserted directly before the first <INTERCHANGEHANDLERS> element in the xconfig.xml (Designer and Server):

  <EDISKIPERRORS>TRUE</EDISKIPERRORS>
  </COMPONENT_FACTORY>
  <COMPONENT_FACTORY>
  <NAME>EDI</NAME>
  <VISUAL>com.sssw.b2b.ee.edi.dt.GVEDIXObjectFactory</VISUAL>
  <NONVISUAL>com.sssw.b2b.ee.edi.rt.GNVEDIXObjectFactory</NONVISUAL>
  <CORE_ENABLER>false</CORE_ENABLER>
  <ENABLER_VERSION>5.2.1</ENABLER_VERSION>
  <MIN_CORE_VERSION>5.0</MIN_CORE_VERSION>
  <ENABLER_LICENSE>myLicenseGoesHere</ENABLER_LICENSE>
  <EDISKIPERRORS>TRUE</EDISKIPERRORS>
  <INTERCHANGEHANDLERS>
  <HANDLER>
  ...

  Sample result from parsing EDI Document with errors (partial Temp DOM):

  ...
  ...
  <SG3>
  <N9 description="Reference Identification">
  <D128 description="Reference Identification Qualifier"
  elementid="N901"><EDISkipErrors>
  <EDISkipError ParseError="The length of the contents of the data element is
  too long. the defined maxLength is 3, 
  the found length is 19 ("-987265pok;jwg[9uL1")"/>
  <EDISkipError ParseError="Invalid value:-987265pok;jwg[9uL1 Allowed values are
  01,ZX,ZY,ZZ"/>
  </EDISkipErrors>-987265pok;jwg[9uL1</D128>
  <D369 description="Free-form Description" elementid="N903">Comparison
  Message</D369>
  </N9>
  ...
  ...

  
  

HP3000 Connect issues

• Consoles on WebSphere  
  
  
• Connection Pools  
  
  
• Importing Components  
  
  

HTML Connect issues

• Pop-up windows are not supported   Some web sites use pop-up windows, which are not supported by the Integration Manager Connect.
  
  
• NTLM Proxy during design time   There is a known issue during Design time when using an NTLM protected proxy where image retrieval may cause authentication to fail. This only happens on certain Web sites. After the NTLM authentication fails, the system will be unable to access any Web sites via the proxy, and you will get the error "Error Executing This HTML Action: Error retrieving the content from null;” To prevent this situation from occurring, you may turn off image loading by editing the file "xconfig.xml" in the exteNdComposer\Designer\bin directory. Locate the <LOAD_IMAGES> tag in the <NAME>HTML</NAME> section of the file and change its value to OFF.
  
  
• ActiveX Controls   The HTML Connect WILL NOT process ActiveX controls. Not all web applications use ActiveX controls. Even when they do, they may have no effect on your specific integration requirements. For many of these situations there are workarounds. For instance if you need to use a select button that executes Java Script to send the parameter list to the next page, you can capture the parameters being sent and then modify the action to manually populate the values of the parameters.
  
  
• Screen painting issue with some sites with frames   Sites with frames may sometimes paint a frame outside of the HTML native interface window.

  Workaround: Minimize and Maximize to repaint

  
  
• Loading a saved ScreenDoc into a DOM   You cannot load ScreenDoc into a DOM after writing it to disk. In addition to the problem that the DOM could not be loaded, there is no indication of any error feedback to the user.
  
  
• Authenticated HTTP Connections   When trying to create an authenticated HTTP connection using a client certificate after clicking finish, the connection is created. However the client certificate file (*.cer) corrupts the xml file and creates an invalid component.

  Certificates in base64 encoded X.509 format can be read in without corrupting the component. Certificates in DER binary encoded format will corrupt, however.

  
  
• v5.2 does not support download of non-HTML files from HTML Connect  
  
  

JMS Connect issues

• Apply button in Map Action does not work   Pressing Apply in the Map dialog does nothing. The action only takes effect if you press Apply and then press OK. Pressing OK without pressing Apply first, does nothing (as it should).
  
  
• Deploying JMS Services   JMS Services and Process Components must be deployed as J2EE 1.2 to exteNd Application Server 4.0/4.01 if the application server is secured.
  
  
• Problem with copybook fields   There is a problem with copybook fields in JMS, which can be best described by an example. Within a JMS Send action in the "Before Send Actions" section, the user manually maps a value to one of the copybook fields in the Message Body. The user mapped a "5" to a field which determines the count in an "occurs depending on" statement. A while loop maps a value to a field within the "occurs depending on" section for each instance that occurs while the index is less than the count value (5 in this case). The user executes the component and it works fine. When the user maps a "6" to the count field instead of a "5", the component runs fine until it gets to the 6th iteration in my while loop. It still thinks the value is "5" and it errors when it reaches the 6th iteration in the loop.

  Workaround: The count field is being cached. Save the component with the new value (e.g. in this case "6"), close it, and re-open it to workaround this problem.

  
  
• Using variables in Message Filters  When creating a Message Filter in a Receive Message action of a JMS Service, and you want to use a variable, prefix variable names with a colon. (TDR7662)
  
  

PeopleSoft, Siebel, JD Edwards, Lawson, Oracle Applications, and Baan Connect issues

• The Start/Stop button in Integration Manager Console  The Start/Stop button for Siebel, JD Edwards, Baan, Lawson, Oracle Applications, and PeopleSoft Services in the Integration Manager Server Console should toggle from Stop to Start when it is pressed. Instead it changes to "Disabled". If you need to restart the service, use the application server management console.
  
  
• File Listener for PeopleSoft, Siebel, JD Edwards, Lawson, Oracle Applications, or Baan won’t start on BEA WebLogic 8.1  An exception is thrown when attempting to start a File listener for PeopleSoft, Siebel, JD Edwards, Lawson, Oracle Applications, or Baan on BEA WebLogic 8.1. To correct this problem you must make a change to xconfig.xml. Open the xconfig.xml file (located in \Novell\exteNd5\Composer\Designer\bin) with a text or XML editor, and add the following child element to the System element:

  <JCA_FORCE_NONMANAGED>true</JCA_FORCE_NONMANAGED>

  For example:

  <?xml version="1.0" encoding="UTF-8"?>
  <XCONFIG>
    <SYSTEM Desc="Designer Configuration Options">
      <JCA_FORCE_NONMANAGED>true</JCA_FORCE_NONMANAGED>

  (TDR7782)

  
  
• Managed Mode Supported for Novell exteNd Application Server only  Managed mode connections are only supported for the Novell exteNd Application server. In managed mode, the application server controls connection pools. In non-managed mode, Integration Manager simply destroys a connection when it is no longer needed. Thus performance may be reduced when deploying a PeopleSoft, Siebel, JD Edwards, Lawson, Oracle Applications, or Baan connect to application servers other than Novell exteNd Application server.
  
  
• Restarting Listener Not Supported in Managed Mode for Novell exteNd Application Server  Restarting a listener when running the exteNd Application Server in managed mode is not supported in this release. (TDR7751)
  
  
• PeopleSoft Deployment to WebSphere   The following exception occurs when deploying a PeopleSoft Component that contains a Web service to WebSphere. The application actually does deploy and can be run; however, an error is generated. The following is an example of the error:

  Deployment Report:
  Deployment location will be: D:\program files\WebSphere\AppServer\Composer\tmp
  Initializing DOM from deployment JAR descriptor file.
  Performing the deployment.
  Stored the generated EAR file in the following location: D:\program files\WebSphere\AppServer\Composer\staging\jdoe-lt1\jdoe-lt1\PS.ear
  GXSDeployHandler.doPost(): ERROR: Exception while performing deployment: Unable to apply deployment changes due to an exception 

  (TDR7586)

  
  
• Message Handling ECMAScript extension method issues  The J2EE Connector framework of the Integration Manager Connect for PeopleSoft, Siebel, JD Edwards, Lawson, Oracle Applications, and Baan includes some new ECMAScript extension methods that are listed in the Expression Editor. Use of these methods is not supported in this release. The methods include the following Message Handling methods:
  • isRequestMatch
  • getRequestDocument()
  • setResponseDocument()
  
  
• Hourglass cursor not displayed in Function pane of Siebel Request Dialog Box  When browsing the list of available functions in the Function pane of the Siebel Request dialog box, it can take several minutes to retrieve function names from the Siebel system. Initially, an hourglass cursor is displayed, but if you move your mouse away from the Siebel Request dialog, the cursor changes to an arrow, and does not change back to an hourglass when you move the mouse back to the Siebel Request dialog box. However, processing does continue. Please wait for the list of functions to be returned from the Siebel system. (TDR7676)
  
  
• Delete function not available for all business functions listed in Request pane of Siebel Request Dialog Box  The Request pane of the Siebel Request Dialog box shows the Delete function as available for all functions. However, the Delete function is only available for selected functions. If you execute a delete query request for a business function for which the delete function is not supported, you will receive the following error:

  java.lang.Exception: The ability to delete records is not available in this screen or applet.

  (TDR7687)

  
  
• Exception occurs when animating actions in PeopleSoft Service when invalid XML file is received   The following exception occurs when an invalid XML document is received when animating a PeopleSoft Service:

  com.sssw.b2b.ee.iwaf.rt.GNVIWAFBaseException: Error converting IWAFRecord to GNVBaseRecord; 
          ---> nested java.lang.NullPointerException
          at com.sssw.b2b.ee.iwaf.rt.GNVIWAFBaseAdapterInterface.convertToIGNVRecord(Unknown Source)
          at com.sssw.b2b.ee.iwaf.rt.GNVIWAFBaseAdapterWrapper.setRequestRecord(Unknown Source)
          at com.sssw.b2b.ee.jca.rt.GNVAdapterServiceComponent.setAdapterRequest(Unknown Source)
          at com.sssw.b2b.ee.jca.dt.service.GVBaseAdapterListener.simulate(Unknown Source)
          at com.sssw.b2b.ee.jca.dt.service.GVBaseAdapterListener.onRequest(Unknown Source)
          at com.sssw.b2b.ee.iwaf.dt.service.GVIWAFListener.onMessage(Unknown Source)
          at com.ibi.afjca.novell.IWAFInboundConnection$deliveryWorker.run(IWAFInboundConnection.java:207)
          at com.ibi.adapters.util.workmanager.ThreadPool$ThreadPoolThread.run(ThreadPool.java:312)

  (TDR7761)

  
  
• Incorrect context help displayed for PeopleSoft, Siebel, JD Edwards, Lawson, Oracle Applications, and Baan Connects in Request Action, Service Request, and Adapter Service Request dialog boxes   When you click the Help button in the Request Action, Service Request or Adapter Service Request dialog boxes, help is displayed for this dialog box, but it may be for the wrong Connect (e.g., you are using PeopleSoft, but you get help for Siebel). To work around this problem, select the correct help by using the help system table of contents.

Business Process Manager (BPM) issues

• Deploying BPM Components   JMS Services and Process Components must be deployed as J2EE 1.2 to exteNd Application Server 4.0/4.01 if the application server is secured.
  
  
• Exception sometimes thrown in Designer when re-running a process   After executing a process if the user goes to the menu item View\XML Docs\Show\Hide… and makes the process input and process output visible, and the re-executes the process, the process will complete but throw an exception trying to display the DOMs.

  Workarounds: If this occurs you can close and open the component. This will fix the problem and the process can then be executed as many times as required.

  Alternatively, you can simply select Ok from the Show/Hide dialog and click on the process graph, without moving the documents, and the documents will be visible.

  
  

SAP Connect issues

• Installing SAP Java Connector (JCo)  

  Integration Manager SAP Connect is designed specifically to integrate with the SAP environment through the SAP JCo (Java Connector) libraries. Specifically, Integration Manager SAP Connect has been tested with SAP Java Connector 1.1.02, 1.1.03 and 1.1.04.

  Registered SAP users may download SAP JCo libraries from the following SAP site: http://service.sap.com. A valid SAP Service Marketplace user ID and password is required to access this SAP site.

  Note: SAP Java Connector 1.1 requires an RFC runtime library of version 6.10 or higher to be installed on the system on which you want to run JCo.

  
  
• Error Messages  

  Note: To install Integration Manager SAP Connect, you must have SAP Java Connector installed.

  If you do not have SAP Java Connector installed (as described below) before installing the Integration Manager SAP Connect, an error dialogue will appear.

  Also, the Integration Manager log will have the following message:

  java.lang.NoClassDefFoundError: com/sap/mw/jco/JCO$PoolChangedListener

  
  
• Integration Manager SAP Connect Developer  

  For Integration Manager SAP Connect Developer, follow the SAP instructions for installing JCO on Windows NT, Windows 2000.

  1. From the SAP site, download jco-ntintel-1.1.04.zip into an arbitrary directory {jco-install-path}.

  2. Unzip the file jco-ntintel-1.1.04.zip into an arbitrary directory {jco-install-path}.

  3. Add the DLLs to the Composer\Designer\bin directory.

  4. Add jCO.jar to the Composer\Designer\lib directory.

  5. Add a <JAR> entry for jCO.jar to the SAP section of xConfig. For example:

  <JAR>..\lib\jCO.jar</JAR>)

  
  
• Integration Manager SAP Connect Server on Windows NT, Windows 2000  

  For Integration Manager SAP Connect Server, follow the SAP instructions for installing JCO on Windows NT, Windows 2000

  1. From the SAP site, download jco-ntintel-1.1.04.zip into an arbitrary directory {jco-install-path}.

  2. Unzip the file jco-ntintel-1.1.04.zip into an arbitrary directory {jco-install-path}.

  3. Add the DLLs to a location within the application server directory tree that is in the path so that they can be found at runtime. For example, the application server bin directory.

  4. Add jCO.jar to the Composer\lib directory of the Server.

  5. Add [PATH]\Composer\lib\jCO.jar to the CLASSPATH of the application server

  
  
• Integration Manager SAP Connect Server on Solaris  

  For Integration Manager SAP Connect Server, follow the SAP instructions for installing JCO on Solaris.

  1. From the SAP site, download jco-sun-1.1.04.tgz or jco-sun-1.1.04.tar.z into an arbitrary directory {jco-install-path}.

  2. Expand the jco-sun-1.1.04.tgz or jco-sun-1.1.04.tar.z into an arbitrary directory {jco-install-path}.

  3. Add the SOs to a location with the application server directory tree that is in the LD_LIBRARY_PATH so that they can be found at runtime.

  4. Add jCO.jar to the Composer\lib directory of the Server.

  5. Add [PATH]\Composer\lib\jCO.jar to your CLASSPATH environment variable.

  
  
• Integration Manager SAP Connect Server on AIX  

  For Integration Manager SAP Connect Server, follow the SAP instructions for installing JCO on AIX.

  1. From the SAP site, download jco-rs6000-1.1.04.tgz or jco-rs6000-1.1.04.tar.z into an arbitrary directory {jco-install-path}.

  2. Expand the jco-rs6000-1.1.04.tgz or jco-rs6000-1.1.04.tar.z into an arbitrary directory {jco-install-path}.

  3. Add The SOs to a location within the application server directory tree that is in the LIBPATH so that they can be found at runtime.

  4. Add jCO.jar to the Composer\lib directory of the Server.

  5. Add [PATH]\Composer\lib\jCO.jar to your CLASSPATH environment variable.

  
  
• Integration Manager SAP Connect Server on HP-UX  

  For Integration Manager SAP Connect Server, follow the SAP instructions for installing JCO on HP-UX.

  1. From the SAP site, download jco-hp_32-1.1.04.tgz or jco-hp_32-1.1.04.tar.z into an arbitrary directory {jco-install-path}.

  2. Expand the jco-hp_32-1.1.04.tgz or jco-hp_32-1.1.04.tar.z into an arbitrary directory {jco-install-path}.

  3. Add The SLs to a location within the application server directory tree that is in the SHLIB_PATH so that they can be found at runtime.

  4. Add jCO.jar to the Composer\lib directory of the Server.

  5. Add [PATH]\Composer\lib\jCO.jar to your CLASSPATH environment variable.

  
  
• Consoles on WebSphere  
  
  
• Connection Pools  
  
  
• Error establishing connection for Listener on JBoss   After deployment, you may receive the following error establishing a connection for the listener:

  16:47:37,272 INFO  [STDOUT] java.lang.NoClassDefFoundError
  16:47:37,273 INFO  [STDOUT]     at com.sssw.b2b.ee.sap.rt.GNVSAPXObjectFactory.c
  reateConnHandler(Unknown Source)
  16:47:37,274 INFO  [STDOUT]     at com.sssw.b2b.ee.sap.rt.GNVSAPServiceXObjectFa
  ctory.getConnection(Unknown Source)
  16:47:37,274 INFO  [STDOUT]     at com.sssw.b2b.rt.factory.GNVBaseFrameworkFacto
  ry.getConnection(Unknown Source)
  16:47:37,275 INFO  [STDOUT]     at com.sssw.b2b.xs.GXSFrameworkFactory.getConnec
  tion(Unknown Source)
  16:47:37,276 INFO  [STDOUT]     at com.sssw.b2b.ee.sap.rt.GNVSAPComponent.getCon
  nection(Unknown Source)
  16:47:37,276 INFO  [STDOUT]     at com.sssw.b2b.ee.sap.xs.GXSSAPServiceComponent
  .getSAPRepository(Unknown Source)
  16:47:37,277 INFO  [STDOUT]     at com.sssw.b2b.ee.sap.xs.GXSSAPServiceControlle
  r.getSAPServer(Unknown Source)
  16:47:37,278 INFO  [STDOUT]     at com.sssw.b2b.ee.sap.xs.GXSSAPServiceControlle
  r.start(Unknown Source)
  16:47:37,278 INFO  [STDOUT]     at com.sssw.b2b.ee.sap.xs.GXSSAPServiceGroup.sta
  rt(Unknown Source)

  If this occurs, make sure that the following JCO files are in the {install path}/Novell/exteNd5/Composer/Designer/bin directory and that the files are executable:

  • librfccm.so
  • sapjcorfc.so
  • sapjco.jar

  (TDR7811)

  
  

T27 Connect issues

• Logon Connection Resource contains a hard coded reference   T27 Logon Connection Resource appears to be hard coded to use the 'GemTestLogicDefault' Logon Component. After creating a Logon Connection that uses any Logon Component, you will receive this error:

  Exception messages:

  1 dt009102:Connection failed

  2 Nested Message: rtUNISYS000806:Connection via GemTestLogicDefault timed out. 0 created connection(s) at this moment were busy and 3 connection(s) discarded.

  Root exception stack trace:

  com.sssw.b2b.ee.unisys.rt.GNVUnisysException: Connection via GemTestLogicDefault timed out. 0 created connection(s) at this moment were busy and 3 connection(s) discarded.

  (TDR5794)

  
  
• Consoles on WebSphere  
  
  
• Connection Pools  
  
  
• Importing Components  
  
  

Tandem Connect issues

• Consoles on WebSphere  
  
  
• Connection Pools  
  
  
• Importing Components  
  
  

Telnet Connect issues

• Consoles on WebSphere  
  
  
• Connection Pools  
  
  
• Importing Components  
  
  
• Some telnet sites do not work when deployed to a Linux server   (TDR7600)

  Workaround: Go through a proxy running on either a UNIX or Windows machine.

  
  

UTS Connect issues

• Consoles on WebSphere  
  
  
• Connection Pools  
  
  
• Importing Components  
  
  

Upgrading from Composer 4.2 to 5.x

• FESI to Rhino ECMAScript upgrade   Rhino is a more robust and stricter implementation of ECMAScript than FESI. Consequently, some functions and scripts that were allowed and worked under the FESI implementation will no longer work in the Composer 5.x Rhino implementation. When upgrading to version 5.x from any previous version of Composer, users must perform thorough testing in both their design time and deployed server environments.

  There are three potential problem areas. These areas are listed below and any actions required by users to detect and correct problems are also described:

  • ECMAScript Keyword and Future Reserved Word Usage
  • SilverStream Aggregate functions where(), min(), max(), sum(), avg(), and count()
  • Functions without a return statement

  ECMAScript Keyword and Future Reserved Word Usage

  Issue:   The Rhino implementation will not allow ECMA Keywords or Future Reserved Words to be used as identifiers in Integration Manager’s Script expressions. Many of these identifiers are allowed by FESI. For instance, the following two statements are allowed by FESI and work in Composer 4.2:

     var instanceof = 12;
     alert( instanceof )

  In Composer 5.x, the same statements produce the following error when the action model is executed:

     Error applying function action.
     Error evaluating ‘var instanceof = 12;
     Error trying to compile the script.
     missing variable name

  Potential Problem:   Use of ECMAScript Keyword and Future Reserved Words in Composer 5.x will cause component executions to fail.

  Corrective Action:   When upgrading to version 5.x from any previous version of Composer, users should perform thorough testing in both their design time and deployed server environments of all applications built using a Composer version prior to 5.x. No application should go into a production environment without upgrade testing.

  The following identifiers are not allowed in the Rhino implementation of ECMAScript in Composer 5.x. Keywords:

  one of	break	else	new	var
  case	finally	return	void	catch
  for	switch	while	continue	function
  this	with	default	if	throw
  delete	in	try	do	instanceof
  typeof

  Future Reserved Words:

  one of	abstract	enum	int	short
  Boolean	Export	Interface	static	byte
  extends	long	super	char	final
  native	synchronized	class	float	package
  throws	const	goto	private	transient
  debugger	implements	protected	volatile	double
  import	public

  SilverStream Aggregate functions where(), min(), max(), sum(), avg(), and count()

  Issue:   The Silverstream aggregate functions are special extensions made to Integration Manager’s ECMAScript implementation that provide powerful functionality across multiple nodes in XML document hierarchies. These functions allow the nesting of XPath expressions. In Composer 5.x, these nested XPath expressions must now be quoted strings. Below is an expression that is shown in its valid form in 4.2 and 5.x. Note the use of the single quotes for the nested XPath expressions and the use of the escape character (\).

  Valid 4.2 Aggregate function expression:

     Input.XPath(“INV:INVOICEBATCH/INV:INVOICE”).where(XPath(“INV:TOTALS/INV:INVOICETOTAL”) ==
     Input.XPath(“INV:INVOICEBATCH/INV:INVOICE”).max(XPath(“INV:TOTALS/INV:INVOICETOTAL”)))
     .XPath(“INV:INVOICEHEAD/INV:INVOICENO”)

  Valid 5.x Aggregate function expression:

     Input.XPath("INV:INVOICEBATCH/INV:INVOICE").where('XPath("INV:TOTALS/INV:INVOICETOTAL") == 
     Input.XPath("INV:INVOICEBATCH/INV:INVOICE").max(\'XPath("INV:TOTALS/INV:INVOICETOTAL")\')') 
     .XPath("INV:INVOICEHEAD/INV:INVOICENO")

  Potential Problem:   Failure to properly quote and escape nested XPath expressions will result in an error with the following message: "XPath" is not defined.

  Corrective Action:   Integration Manager will automatically detect and process nested XPath expressions created using previous Composer versions. In addition, new nested XPath expressions created using the Expression Builder dialog in 5.x will automatically have the proper quoted syntax applied.

  Expressions created manually are a potential problem as are any expression patterns not anticipated and detected by the automatic upgrade functions.

  Functions without a return statement

  Issue:   The Composer 4.2 FESI implementation allowed function definitions without an explicit return statement and would return the last variable evaluated. Rhino requires an explicit return statement for all functions.

  Potential Problem:   Functions without an explicit return statement in Integration Manager 6 will return the following: com.novell.mozilla.javascript.Undefined@xxxxxx

  Corrective Action:   Users should review all Custom Script functions created with Composer versions prior to 5.x and ensure that every function contains an explicit return statement that gets evaluated.

  When upgrading to Integration Manager 6 from any versions of Composer before 5.x, users should perform thorough testing in both their design time and deployed server environments of all applications built using a Composer version before 5.x. No application should go into a production environment without upgrade testing.

Upgrading from Composer 5.2 to 5.2.1

Except for the MySQL/Process Manager issue described in MySQL Issues, no backward-compatibility issues have been introduced with Composer 5.2.1. Projects created under 5.2 are fully compatible with the 5.2.1 design-time environment. Production applications built with Composer 5.2 do not need to be rebuilt for 5.2.1.

Upgrading from Composer 5.2.1 to Integration Manager 6

Before opening any projects created in earlier versions of exteNd Composer using Integration Manager 6, download and install the JCE "Unlimited Strength" Jurisdiction Policy Files from http://java.sun.com/products/jce/index-14.html#UnlimitedDownload. To install the JCE policy files, follow the instructions in the README.TXT file that is included with the download. Install the policy files to ..\nim\Common\jre\lib\security. Otherwise, you will receive the error message "error decrypting password" on any Integration Manager object that contains a password field (for example, connection resources, WS Interchange actions).

MySQL Issues

Processes and MySQL databases prior to Version 4.1.3  Integration Manager is not compatible with Processes developed with versions of Integration Manager prior to Composer 5.2.1 using MySQL databases versions prior to 4.1.3. This is due to a change in the primary key (ProcessName) field. This should not affect customers in production, because documentation for previous versions of exteNd stated that MySQL should not be used for production purposes.

Multiple entries for Hospital Project in Recent projects list

When Integration Manager is installed on Linux systems, there are four identical entries for the Hospital tutorial project in the Recent projects list on the File menu. This defect will be fixed in a future release.

Expired Integration Manager Enterprise Server License Issues

Updating your Integration Manager Enterprise Server Core license   An Integration Manager console user interface allows you to update runtime licenses for the installed Integration Manager Connects, but if the license for the Integration Manager Enterprise Server runtime itself expires, the license cannot be updated in the same way, using the user interface (because in order to get to the consoles, Integration Manager Enterprise Server--the core product--needs to be running, but if the license is expired, it can't run). To update the license for the Integration Manager Enterprise Server itself, use the UpdateLicense.bat file (or UpdateLicense.sh file for Linux and Solaris), located in your /Composer/bin directory (except on a JBoss server; in which case it is in the {JBOSS_INSTALL_DIR}/server/{configuration]/conf directory). From the command line, run:

updateLicense product newLicense [Composer | Server]

where product is the name of the particular product the license of which you would like to update, newLicense is the license string, and the final argument (one of Composer or Server) specifies whether to update the design-time or runtime version of the product in question.

Firefox and Mozilla browser with Process Manager issues

When using Firefox or Mozilla Browsers as the browser for the Process Console, the "View Text" option for the Process messages will fail with an XML Parsing Error. To work around this, click the right mouse button on the browser window and select "View Page Source" to view the message output. (TDR7780)

Sample Projects issues

• ActionExamples   The sample project titled "ActionExamples" needs modifications before you can run the project.

  Note:  The ActionExamples project was designed to be used with the MySQL database. However, MySQL is no longer installed along with Integration Manager. To use ActionExamples, you'll need to download and install MySQL, then follow the steps below.

  1. Open the project titled "ActionExamples".
  2. In the left-hand panel of the Integration Manager window, locate the Connection resource that is named "InventorySystem".
  3. Right-click on Inventory System and select Properties.
  4. Select the Connection Info tab.
  5. In the JDBC URL field, change "Localhost" to "127.0.0.1".
  6. In the Password field, enter the password for the MySQL root user.
  7. Select OK.
  8. In the left-hand panel of the Integration Manager window, in the Resource section, click on JAR. Integration Manager displays the list of defined JAR resources.
  9. Delete the JAR resource named “mysql-connector-java-3”.
  10. Create a new JAR resource. For the File/URL to Import, select the "mysql-connector-java-bin.jar" file, which is located in {install path}\Novell\exteNd5\MySQL\jdbc.
  11. Save the project. (TDR7640 and TDR7750)
      
      

Registry Browser Issues

• Clicking link to retrieve service WSDL from Registry throws error  Make sure that when clicking the link you are clicking the Retrieve icon (World with arrow pointing to the left).

Using JNDI and CORBA factory classes in Integration Manager Designer

If you are trying to create and test ORB-dependent code or actions (e.g., code that tries to invoke an EJB), you will need to ensure that the orb.properties file for your server environment is in your design-time jre/lib folder (depending on the application server that you are accessing). Also, to resolve classes mentioned in the orb.properties file, you will need to have the appropriate client JARs in your jre/lib/ext folder. For example, the exteNd application server comes with an orb.properties file that contains the following entries:

# make jBroker the default ORB
org.omg.CORBA.ORBClass=com.sssw.jbroker.ORB
org.omg.CORBA.ORBSingletonClass=com.sssw.jbroker.orb.SingletonORB

# get jBroker implementation of RMI-IIOP APIs
javax.rmi.CORBA.StubClass=com.sssw.jbroker.rmi.StubDelegate
javax.rmi.CORBA.UtilClass=com.sssw.jbroker.rmi.UtilDelegate
javax.rmi.CORBA.PortableRemoteObjectClass=com.sssw.jbroker.rmi.PortableRemoteObjectDelegate

A copy of this orb.properties file should be placed in your jre/lib folder so that Integration Manager Designer can invoke EJBs on the server. Otherwise, you will get CORBA exceptions. Likewise, for the exteNd ORB to resolve the class com.sssw.jbroker.rmi.PortableRemoteObjectDelegate, you would need to put the mp-orb.jar in your jre/lib/ext folder. (PPR 44797)

Problems fixed in Version 5.2

Category	Description
Common	If the user changes the "Template Name" parameter from SEARCHINPUT to SEARCHINPUTtest and then resizes one of these parameters, the added test will disappear
Common	Form resources created with the initial exteNd Composer 5.0 beta were stored in a subdirectory of "xhtml". This has been changed to "form" for 5.0. You will have to copy any xforms files that you have created in beta from the xhtml directory to the form directory to use them.
Common	In the Custom Script Editor window, when the user highlights a function in the Validated Functions List pane, the Function Creation and Variable Declaration pane scrolls to and displays the function but does not highlight the function in this pane.
Mapping	After editing a Map action the document trees will redraw and only the current tree node will not collapse.
Repeat	Closing a loop action dialog with the enter key rather than a mouse click causes the action model frame to scroll to the bottom.
JDBC	When dragging a DOM element into the SQL STATEMENT pane single quotes are wrapped around all element names the column type is not recognized.
JDBC	The keyword "FROM" is missing from the Delete tree in the JDBC keyword selection menu.
Deployment	Deploying a deployment object more than once throws an error on Windows XP. On the second attempt to deploy, the user is able to proceed through the screens in the deployment console, but the deployment report comes back with an error message (the beginning of which is below). ERROR: Deployment Report: Deployment location will be: C:\Program Files\Novell\exteNd5\AppServer\Composer\tmp Initializing DOM from deployment JAR descriptor file. Workaround: You may reboot the server to clear the cache. The problem is caused when the Internet Explorer 'Check for newer page versions' is set to 'Never'. To avoid the problem, change the setting to ‘Every visit to the page’.
Deployment	If you were using Sybase as the Process Database in version 5.0-beta and deployed Process projects with version 5.0-beta, you will need to re-deploy those projects in release 5.2. You will also need to re-initialize the database.
Deployment	When deploying an Integration Manager project to WebSphere, the name of the deployed application will always be the name of the enterprise archive file, without the .ear extension. Any other name that the user attempts to assign to the application, within the deployment console, will be ignored.
Deployment	After deploying an EJB servlet to exteNd Application Server using Integration Manager 5.2, an error is generated when trying to access an EJB from Integration Manager Custom Scripts. Workaround: You must use Novell HTTP handler, which may be set via the HTTP handler type drop down on the System Environment tab of the Integration Manager Configuration dialog. The Configuration dialog is accessed from the Tools/Configuration menu. The Novell HTTP Handler has some problems with secure sites when using Integration Manager HTML Connect, therefore, we recommend using the Integration Manager Handler unless you are accessing EJBs deployed to a Novell server.
Deployment	The application server is designed to run under the root uid. If this is not done, there will be errors during deployment of Integration Manager objects. If one chooses not to run the application server under the root uid, there are at least two workarounds to this problem. 1. Go to Common/jre/bin directory and run policytool. Open java.policy file, which is located in Common/jre/lib/security. Double-click on codebase ALL and add FilePermission to execute SilverCmd file located in AppServer/bin directory. Save policyfile and exit policytool. or 2. Login as root. Go to AppServer/bin directory and execute first "chown root SilverServer" and then "chmod a+s SilverServer". logout.
Validation	Validation error with mustUnderstand attribute defined in schema. There was a change to the soapEnvelope schema that fixes this problem. This file must replace the existing one in schema catalog. Please contact support.
HTML	Animated GIFs: Some animated GIFs on some web pages have been found to be problematic in Integration Manager Design time as they cause the application to run very slowly or some rare instances freeze. As a workaround, we have included an option to turn animated GIFs off. Currently, the only way to do this is to edit the xconfig.xml file manually. In the exteNdComposer/Designer/bin directory, edit the "xconfig.xml" file. Search for the <ANIMATED_GIFS>ON</ANIMATED_GIFS> section and change the value to OFF. Please note that as a consequence of this, some GIFs may not appear correctly.

Problems fixed in Version 5.2.1

Category	Description
Common	Deleting a project: A missing message causes a confusing dialog to appear when using File, Delete Project. The actual dialog text should read: Deleting a project will delete all files within the project location. Are you certain you want to delete the project named xxx?
Help	Context-based help is now available in the UI for the following commands: File > New > xObject > Resource > Image File > New > xObject > Resource > DTD File > New > xObject > Resource > JSP Component > Add Watch Tools > Profiles > Server Action > New Action > SQL Statement Help is also available at design time for the various SQL creation wizards available from the SQL Statement action (in the JBDC Component Editor).
Tomcat	Tomcat only supports J2EE 1.2 (WAR 2.2). The default when creating the WAR file project is 2.3. When deploying, the user must change this default.

Problems fixed in Version 6.0

Category	Description
Common	Corrected a cache synchronization problem. (TDR7824)
LDAP	Fixed a DOM hierarchy request problem when multiple users are using component doing an LDAP search. (TDR7825)
Web services	Added support for HTTPS/SSL via proxy. (TDR7673)
Oracle 9i, 10	Integration Manager now returns the correct data for Oracle timestamp column types. (TDR7819)
Baan, JD Edwards, Lawson, Oracle Applications, PeopleSoft, and Siebel Connects	The Polling Location, Response/Ack Directory, and Error Directory connection parameters for File listeners can now be evaluated as expressions. These connection parameters now have a context menu that allow Constant/Expression selection. (TDR7788)
JDBC, ECI	Fixed problem of undefined custom variables after rerun.
JBoss 4.0.2	Corrected a problem that caused an error running Composer Enterprise Server on JBoss 4.0.2. (TDR7843)
Common	Corrected a problem with importing new DTD resources. (TDR7844)
Schema Validation	Corrected a problem that caused a failure during validation if an XML element contained a single space character. (TDR7846)
Common	Corrected a problem in which Integration Manager cannot find a DTD after a template is created and the location of its DTD is later changed through the Properties dialog for the template. (TDR7848)
Web services	Corrected an erroneous error message that was displayed when a WSDL was created. (TDR7850)
Common	Corrected a problem in which new actions added to a component were not saved if the components Properties had been displayed immediately before adding the actions. (TDR7852)
Web services	Corrected problems which prevented creation of correct SOAP requests for complex RPC elements. (TDR7860, 7861)
Web services	Corrected a problem handling multiple namespaces in complex RPC. (TDR7862)
Web services	Corrected a problem executing a component that has no output document from within a Web service. (TDR7863)
JDBC	Corrected a JDBC thread contention problem between user interface modules, which occurred when switching between two JDBC actions. (TDR7869)
Telnet	Corrected an ArrayOutOfBounds exception and bad characters displayed in Telnet component when using certain encodings. (TDR7870)
3270 EPI	Corrected a thread leak in 3270 EPI connections (TDR7821)
LDAP	Corrected LDAP connection pool thread leaks. (TDR7827)
LDAP	Corrected a problem that caused an error attempting to drill-down in a replica tree in an LDAP component. (TDR7841)
LDAP	Corrected a problem in which project DOM changes were not propagated to cached connection components. (144853)
Baan Connect	Corrected a problem with the display of Baan Service connection parameters. (TDR7797)
Baan Connect	Corrected a problem with Baan table listener support. (TDR7798)
Oracle Applications Connect	Corrected a problem with a missing password field for Oracle connections. (TDR7807)
Web services	Corrected a problem that caused an error when refreshing the Web service URL in a browser. (TDR7840)