NovellŇ
exteNd Composer™
5.0
|
|
|
5.0 |
January 2004
Welcome to Novell® exteNd ComposerTM, Version 5.0. These release notes include the following sections:
|
How to prepare for installing Novell exteNd Composer |
|
|
Software and hardware needed to run exteNd Composer |
|
|
Setup guide for exteNd Composer installation |
|
|
exteNd Composer enhancements in Version 5.0 |
|
|
Features in this release of exteNd Composer |
|
|
Known issues with this release of exteNd Composer |
Release note
updates To check for updates to these release notes, click here.
Release Notes
The release notes for each of the exteNd Composer solutions are installed with exteNd Composer. You may display the Release Notes for them by clicking on their link below.
Release Notes
|
exteNd Composer Web site For the latest exteNd Composer downloads, discussion forums, news, and information, click here.
Installing exteNd Composer
For a complete guide on Installing exteNd Composer 5 and the exteNd 5 Suite, see Installation Guide in the exteNd 5 Suite help.
System Requirements
This section describes the software and hardware needed to run exteNd Composer 5:
Development environment
|
Topic |
What's required |
|
Operating system |
One of the following:
|
|
Minimum RAM (memory) |
128 MB (256 MB recommended) |
|
Disk space |
100 MB |
|
Display mode |
True Color (32-bit), 800 x 600
or higher (1024 x 768) recommended |
|
Java 2 Runtime Environment |
JRE 1.4.2_01-b06 (installed
automatically) |
|
Database Connection |
MySQL Database Driver for the
supplied tutorial |
|
Mail Server Connection
(optional) |
Using SMTP and POP3 |
Server environment
|
Topic |
What's required |
|
Application server |
One of the following:
|
|
Operating system |
One of the following:
|
|
Database |
One of the following (Required for exteNd Composer Process Manager and the tutorials). Shipping with exteNd 5:
Supported by exteNd 5:
|
|
LDAP directory |
(Optional) exteNd Composer
supports the following:
- For Development Only
|
|
Web browser |
|
J2EE compatibility
This version of exteNd Composer enables you to develop applications for Java 2 Platform, Enterprise Edition (J2EE) Version 1.3.
Setup and configuration
To install exteNd Composer, perform the following steps:
1. Start Windows, if you have not already done so.
2. Insert the exteNd 5 CDROM into the CDROM drive
3. Simply follow the instructions on the screen.
What
is installed?
The exteNd Composer setup program creates a series of directories on your computer during installation (under C:\Program Files\Novell\exteNd5 by default). These directories and their contents are outlined below:
Composer -- the root directory where all exteNd Composer files are located.
Designer -- main directory containing all the run time files required by exteNd Composer
lib -- contains all exteNd Composer runtime libraries
bin -- contains the executable for exteNd Composer and is the base directory for all log files
Samples -- contains various projects and script objects created in exteNd Composer.
ActionExamples -- contains a project demonstrating various uses of the basic exteNd Composer action set.
CustomScripts -- contains samples of user defined ECMAScript functions organized into common library types such as date, string, etc.
DOMMethods -- contains a project demonstrating the use of various ECMAScript and DOM methods
ServiceProviders -- contains a project demonstrating the use of Service Providers
Tutorial –- contains the files required for the exteNd Composer Tutorial
Files -- contains the XML documents that you will need when going through the tutorial.
Lessons -- contains a pdf document entitled Composer Tutorial.
Solution -- contains the completed exteNd Composer Tutorial Project that will open as the default project when Composer is first started.
Docs -- this directory contains the documentation for the exteNd products including exteNd Composer.
Common – this directory contains directories and files shared by the exteNd products.
bin – contains the shared executables
images – contains the shared images
jre -- contains the Java 1.4.1_03 runtime required for exteNd Composer
lib – contains the shared runtime libraries
Resources -- contains shared resource files
WSSDK – contains shared Web Services SDK files
xc_api – contains shared exteNd Composer files
Troubleshooting:
If after starting exteNd Composer nothing happens, or the splash screen appears and then disappears, refer to the messages found in the system log that is located under the directory where exteNd Composer was installed. The default location is:
..\exteNd5\Composer\Designer\bin\Logs\xcsyslog.txt.
What’s new in Novell exteNd Composer 5.0?
Ease of Use
Providing the user with a
high productivity environment with which to integrate disparate systems has
always been a major design objective of Novell exteNd Composer. With Novell exteNd 5, exteNd Composer
continues to enhance user productivity by delivering new features that
significantly increases ease-of-use.
1. Tightly Integrated exteNd Suite: To enhance the out-of-the-box experience of the
user, the exteNd 5 Suites, including exteNd Application Server, exteNd Director
and exteNd Composer, share a common installation wizard with which users can
quickly install and deploy the exteNd products.
2. Deployment enhancements: exteNd 5 Composer
(Enterprise Edition) provides a new deployment metaphor that moves away from
the single wizard to one that provides significantly enhanced flexibility. The following new features make deployment
much easier for the user and provide the user with several new service trigger
options.
a.
Deployment xObject: A new deployment xObject that defines a deployment “profile” replaces the
previous (pre-5.0) deployment wizard. The deployment object will contain such
information as which service triggers to create, which resources to deploy,
etc. A workspace panel will provide the
mechanisms to define these. Multiple deployments can be defined.
b.
Server Profiles: The user will be able to create “server profiles”
that define a deployable server and all its necessary server-specific
information. During a deployment, the user can choose a server profile, a
deployment object and a user name/password to complete the deployment.
c.
New
Service Trigger Types:
extend 5 Composer introduces enhanced options with the introduction of support
for the following service trigger types:
i.
eMail Listener: The user can
specify the mail server, mailbox, user and payload type of the incoming message
to use for the trigger.
ii.
Timer: The user can deploy services that will be
“time triggered” or scheduled to execute at a specific time, day or interval
iii.
File: The user can deploy services that will poll
for files/file types in a specific directory at specific intervals.
iv.
JSP: The user can easily deploy services with a JSP
front end.
v.
Form: Services can be called as the result of
Submit on a Form.
d.
Additional
Deployment Options: The
deployment options have been expanded to include all standard J2EE options
(e.g. init, timed, mime type).
3.
Auto-Generation
of UIs: exteNd
5 Composer enables the user to auto-generate front
ends for the Composer Services.
a.
Java Server Pages
Wizard: exteNd 5 Composer introduces a new Java Server Page Wizard to auto-generate JSP
for Composer Services. Composer users
can also manually create JSP pages using exteNd Composer’s JSP editor. JSP Resources can be used with the Composer
Tag Library to test Web Services or create simple browser based access to Web
Services. The tags can invoke Composer
Services, handle multiple output documents, output values from the document,
perform looping and conditional branching, and handle faults.
b.
Enhanced JSP Tag Library: The JSP Tab Library now includes support for:
i.
A
new input converter class called “InputFromJavaObject”
- Converter classes construct or marshal XML documents from various sources of
data and pass them to Composer Services by the <composer:execute>
tag. The InputFromJavaObject
converter class will pass an XML document from two types of Java objects: a
String (i.e. a single input part) or an Array of Strings (i.e. multiple input
parts).
ii.
Multiple
Output parts from an exteNd Composer Service by enhancing
exteNd Composer tags to specify which output part is being referenced
iii.
Handling
Composer Faults in a JSP by providing a new <composer:fault> tag which can be used inside the JSP to
handle errors returned by a Service in a more friendly fashion.
c. Auto-generate Form Resource: exteNd 5 Composer enables the user to automatically
generate a Form Resource from either an existing XML Template in the current
project or by selecting a file from outside the project using URL / Local File.
d. Form Process Action:
The new Form Process Action allows the user to specify a Form within a Composer
Action Model. The Form Process Action
defines Form source data as input and defines an output in which to put the
results of processing the source data.
3.
Auto-Generation of WSDL
a.
Auto-generation of WSDL
from Services: The new Create
WSDL feature enables the user to auto-generate a WSDL by selecting a
Service Component and simply right-mouse clicking to select the Create WSDL… option. Using the Create
a New WSDL Resource wizard, the user can automatically generate WSDL
descriptions for the selected Service Component. The WSDL may be published to various Web
Service Registries.
b.
Automatically Generate RPC
Style WSDL using Samples which don’t have Schemas: Using the
new Create WSDL feature the user may
automatically generate RPC Style WSDLs using samples
which don’t have schemas. This is
helpful in the case where the user needs to publish a Web Service for an
existing Composer service that uses XML documents which refer to DTDs and, therefore, would not have any schemas. In order to publish such a Web service using
RPC style binding, WSDLs have to be created. When
there are no schemas, the only way to create WSDLs
for such services would be to create schemas from samples, which are used in
the Service. This enhancement enables
the user to create RPC style WSDLs using the
Service’s samples.
4.
Easier Navigation: The new
Navigator tabs feature enables the user to quickly navigate among the open xObjects. Using the
Navigator Tabs view, each open xObject is displayed
by clicking on its tab. Via a
right-mouse button menu on any tab, the user may close a xObject,
close all xObjects or close all xObjects
except for the xObject from which the right-mouse
button menu was displayed. Composer also
provides the option of displaying the open xObjects
using the traditional, non-tabbed interface.
5.
Quickly Insert Common
Actions: New Ctrl-keys on the New Action Menu enable
the user to quickly insert the more commonly used actions into an Action Model
without the need to navigate through the menu hierarchy. Ctrl-keys are provided for the following
actions:
a. Comment – Ctrl - E
b. Component – Ctrl - T
c. Decision – Ctrl - D
d. Function – Ctrl - U
e. Log – Ctrl - L
f. Map – Ctrl-M
6.
Manage Tasks: The new To-do task management feature enables the
Composer user to manage tasks which need to be accomplished for a Composer
project or for individual components within a project. As shown in the following illustration the ‘MergeProductandInventory’ XML Map Component has one To-do
item called ‘Update per new requirements’ which is complete as indicated by the
green check mark. The 3270 component
called ‘ProductInfoInquiry’ has two To-do items. The first ‘ProductInfoInquiry’
To-do item ‘Finish component’ is partially complete which is indicated by the
gray check mark. Double-clicking on a
Component task will display the component to which the task is associated. The last To-do item, ‘Check Test System
Availability’ is not linked to a Composer component. The ‘Check Test System Availability’ is a
task required for the overall project.
The user may add and delete tasks as required. Within the To-do list’s tree, the user may
increase or decrease the indent to organize the tasks.
7.
User-defined
Part Names and Multiple Outputs: Prior to
exteNd 5 Composer, users could have multiple inputs to a component, but these
inputs were always named Input, Input1, etc.
In addition, users could only have one output and it is always named
Output. exteNd 5 Composer enables the
user to rename the input and output parts to whatever names they choose (e.g.
more meaningful names like Purchase Order and Invoice). Also, multiple and or no parts will be
allowable for both Input and Output.
8.
Color Highlighted Custom
Scripts: The new color highlighted
script editor enables the user to more easily read a custom script.
9.
File / New Dialog: Composer’s
new File/New dialog provides the user with an interface consistent to that
which he/she experiences in exteNd 5 Director.
The consistent user interface across exteNd Director and exteNd Composer
enhances the user’s learning curve, productivity and overall experience.
10.
Watch Variables: Composer’s
new Watch Variables feature enables the user to select data items from various
aspects of Composer, assemble them in a single list, and examine their data
values during the execution of a Composer Service/Component. The Watch Variables feature provides users
with additional capability to debug Composer Services and Components at design
time.
Select a Watch Variable
View the Watch Variables’ Values
11.
Clear All Breakpoints: The
Composer user may automatically clear all breakpoints using the new Clear All Breakpoints feature. In an
Action Model, the user may clear all breakpoints by selecting the option from
the Animate menu or from the Right-mouse click menu. This clears all breakpoints. Previously, the user would need to manually
clear each individual breakpoint.
12.
Find / Where Used: A Uses Resources option has been added to
the Tools/Find dialog. This new feature
enables the user to search for components that use Individual resources. The user may use the Resource Type dropdown
to filter the list of Resource Names.
13.
Color Code Comments: To make it
easier for the user to quickly identify and read Comment lines in the Action
Model, the Action Model’s Comment lines are now automatically color coded
gray.
14.
Save All: A new Save All menu item has been added to the
File menu which allows the user to
optionally save all modified open components.
Previously the user would need to save each open component,
individually.
15.
Close/Maximize Buttons: Close and
maximize buttons have been added to the XML Tree view to enable the user to
easily gain the view necessary to adequately interact with large DOMs. Previously,
the user would need to manually expand and contract the display of XML
Documents in order to see large DOMs. Now the user can expand or contract the
display of the XML Document with a single click of the min/max button.
16.
Easier Access to XML
Features: Four new menu selections have been added to
the current XML Document RMB menu. The
addition of these new menu items to the XML right-mouse button menu allows the
user to access these features via a couple of mouse clicks from the more
intuitive XML right-mouse button menu.
a.
The
new Add to Display menu selection is
a cascading menu. When selected, a
sub-menu is displayed which lists all the documents not currently on display
and allows the user to select one. When
the user selects a listed document it will become visible and will be inserted
below the currently selected document (or at the end if the current document is
the last document).
b.
The
new Launch Editor menu selection
launches the Configuration-defined external XML editor to edit the current
document (like Edit Sample does for
XML Templates).
c.
The
new Load XML Sample… menu selection
enables the user to load an XML Sample using the right-mouse button menu. Previously, this feature was only available
from the from the File menu.
d.
Similarly,
the new Save XML As… menu selection
enables the user to save XML using the right-mouse button menu. Previously, this feature was only available
from the File menu.
17.
Load Resource Action: A new Load Resource Action has been added to
the Data Exchange menu which enables the Composer user to utilize XML, XSL and
Form resources existing in the current project.
The Load Resource Action loads an XML, XSL or Form resource from the
current project into a component.
18. Template Editor: The XML Template editor has been enhanced to
include the following new features on the XML Template’s right-mouse button
menu:
a. Create Schema… - creates a new schema as an XML Schema
Resource
b. Add Sample File… - enables the user to add a sample file to
the template
c. Create Sample File… - enables the user to create a
sample file and add it the template
19. COBOL Copybook Resource: Because of
the growing usages for COBOL data in Composer applications including those not
requiring any Connectors, the ability to convert COBOL data (stored in Composer
Byte Array objects) into XML and XML into COBOL data is being added to core
Composer functionality. Previously, this
functionality was available only in JMS Connect and CICS RPC Connect. COBOL Copybook Resources are used with the
advanced component actions Convert
Copybook to XML and Convert XML to
Copybook. Together, these actions
and resources enable the user to create applications which move XML data into
systems designed to accept COBOL formatted input and move COBOL formatted
output into XML data.
- Action
Enhancements: A Composer Action
Model, typically comprised of multiple Actions, performs all data mapping,
data transformation, and data transfer within components and services. The following Actions have been enhanced
in exteNd 5 Composer:
- Repeat for Element: Repeat for Element: The Repeat for Element dialog has been
enhanced to provide the option of always creating new elements. If the
destination for a Repeat for Element action already has existing nodes,
they would be overwritten in previous versions of Composer each time the
loop was processed. This
enhancement makes it possible to always force the creation of new
elements during iteration.
- Send Mail: The enhanced Send Mail Action enables
the user to include attachments, send mail to multiple recipients and
specify user ID and password for the mail server.
- Timeout for WS Interchange / XML Interchange: Prior to exteNd 5 Composer, the only
way to set a timeout on a Web Service Interchange or an XML interchange
was to add a connection. This
enhancement adds a timeout field to the XML Interchange and Web Service
interchange that overrides the connection timeout, if any.
- FTP Support for XML Interchange: FTP get/put
support has been added for XML interchange.
- FTP Support for File Read/Write: FTP get/put
support has been added for URL/File Read/Write.
- SOAP Message Headers: When a user
creates a Web Service in Composer the expectation is to receive a particular
Input document (i.e. SOAP Request) and send a particular Output document
(i.e. SOAP Response). Prior to exteNd 5 Composer, our focus has been on
the SOAP:Body or business document. However, the user may also need to
bundle SOAP header information to handle higher order tasks. In some
respects, SOAP Headers can be thought of as meta-data for the SOAP
Body. The optional SOAP Header
element contains application specific information (like authentication,
payment, etc) about the SOAP message.
To support SOAP Headers, exteNd 5 Composer introduces new message
part types called “Headers”. The
following dialog has been added to The New Web Service wizard now includes
the following dialog to enable the user to define the Input Header Parts
and Output Header Parts for the Service.
- Preferences and Project Settings: To provide an
easier and more logical means of modifying configuration parameters and
user preferences, new menu items and dialogs for Preferences and Project
Settings are introduced. From the
Tools menu item the user will select Preferences to edit the configuration
items related to the environment (e.g., Editor, Browser, Log, etc..) or
Project Settings to edit the project specific information (e.g.,
Subprojects, Project variables, etc…).
The
“Preferences” dialog provides the following tabs:
The
“Project Settings” dialog provides the following tabs:
- XML
Resource: XML is a new resource type in exteNd 5
Composer. Composer XML resources
can be used to store parameters or document skeletons.
- XSL
Resource: XSL is a new resource type in Composer
5.0. Composer XSL resources can be
used for server side XHTML generation in servlet based Service Triggers.
- JAR Resource: Composer provides the capability to
dynamically add jar files as resources that will be available to the
expression builder and custom script editor and are deployed with the
project as standard J2EE archive files.
- Image Resource: Image is a new
resource type in exteNd 5 Composer.
Image resources can be used by XSLT transformations, JSP Resources
and Form Resources for creating and deploying better User Interface
objects.
- Send
Mail: A new Connection Type,
Mail via SMTP Simple Authentication, can be used in SendMail
action in cases where the mail server requires a user ID and password.
- JAX-R: To enhance exteNd
Composer’s support of standards-based registry types, support for JAX-R is
added to provide ebXML registry support.
- Schema and WSDL Validation: Prior to extend 5
Composer, validating a schema or WSDL file performed a well-formed-ness
check (e.g. the syntax was checked).
In exteNd 5 Composer, validation performs the well-formed-ness
check and validates the file (e.g. semantic check).
- Fault Document Handling: extend 5 Composer provides Fault
documents for better handling of exceptions
and treats all exceptions as faults to be consistent with the Web Services
metaphor and SOAP support.
- CPU
Count: exteNd 5 Composer
will continue to be licensed on a per CPU basis. However, the exteNd products, including
Composer, will no longer carry out a programmatic CPU-count on the
installed server. The ‘honor
system’ approach is Novell standard procedure for maintaining compliance
as well as providing overall customer satisfaction.
- Rhino JavaScript Interpreter: The FESI ECMA
Interpreter has been replaced with the Rhino Java Script Interpreter in
exteNd 5 Composer. Rhino provides
more robust JavaScript capabilities, better performance and the ability to
add JavaScript support to HTML Connect.
Interoperability and Standards Compliance
exteNd Composer’s
interoperability is enhanced with the introduction of support for additional
platforms and open standards:
- Platform Support: exteNd
5 Compose introduces support for the following platforms:
- Linux
(SuSE Enterprise 8 and Red Hat Enterprise Linux AS 2.1) (Server side
only)
- Tomcat 4.1 (Professional Suite elements only)
- MySQL 4.1
- Open Standards: Open standards are a collection of efforts
toward a common goal of advancing the adoption of standards that permit
interoperability and provide the customer with a choice. There are many
organizations developing and promoting open standards. Among its members
are companies, industry groups, government agencies, and individuals. Support for the following standards is
introduced in exteNd 5 Composer.
a. WS-Security 1.0
b. SOAP
1.2
c. WSDL 1.2
d. WSIL 1.0
e. JDK 1.4
f. EJB 2.0
g. Rhino 1.5.4
Security Integration
exteNd 5 Composer continues
to enhance security integration with the introduction of the LDAP Expression
Editor.
1. LDAP Expression Editor: Directories such as eDirectory contain information
that is often required in Integration or B2B Web Service based projects. This information may be User Name and
Passwords for various systems, addresses (physical and email), organization
information, etc.
Prior to exteNd 5 Composer,
LDAP Connect could be used to create a component to access this
information. However, exteNd 5 Composer
introduces an even simpler option with the new LDAP Expression Builder which is
accessible wherever an Expression can be used, including Connections, XML Map
components, and all Connector components.
The Expression button can now be toggled between the familiar ECMA
Expression Editor and the new LDAP Expression Editor.
The ability to look up user
data at runtime is important in any application that has access control
requirements. exteNd 5 Composer allows you to leverage LDAP for this purpose.
JDBC Connect Enhancements
Easier SQL Statement Creation: A new, high productivity, SQL Statement wizard enables the user to create simple SQL statements for four commonly used SQL verbs: SELECT, UPDATE, INSERT and DELETE. This will enable the user to quickly create these statements via simple point-and-click rather than typing SQL statements. This enhancement will increase user productivity as well as make for a much more visual and appealing demonstration of JDBC Connect.
LDAP Connect Enhancements
Connection Pooling Support: To improve performance, Connection Pooling is now supported for LDAP Connect.
Tutorial
The tutorial shipped with exteNd Composer requires a
connection to a MySQL database. The
MySQL database is shipped and installed with exteNd 5. The tutorial database is
automatically configured upon installation.
The Composer tutorial database files are located under:
..\exteNd5\MySQL\data\ComposerTutorial
The tutorial also requires a connection to a LDAP directory
shipped with Composer. It can be started
from the Windows Start menu at: Programs | Novell exteNd 5.0 | Tools | LDAP
Utility.
Features in Novell exteNd Composer
The following is a brief description of the feature set of
Novell exteNd Composer. For a more
detailed look at the features and functionality please read the exteNd Composer
User Guide which is accessible from the Novell exteNd Composer menu. The exteNd Composer User Guide is also
available in hard copy from Novell.
The
Features can be classified into the following areas:
Data Integration - provide a method for integrating heterogeneous legacy systems within and between businesses by XML enabling the business processes in these systems as Web Services through a high performance XML Integration engine.
o Visually Mapping, Transforming, and/or Transferring XML data between XML documents.
o
Visually
XML enable external environments: RDBMS enablement is included in the core
exteNd Composer product. Other Composer
Connectors for 3270, 5250, CICS RPC, JMS, HTML, Telnet, EDI, SAP, etc. are
available for purchase separately.
o
Mapping,
transforming, and/or transferring XML document data via email.
o
Mapping,
transforming, and/or transferring XML document data with external sources via
XML Interchange or Web Service Interchange.
o
Developer
extensions can be developed with Java and ECMAScript
(JavaScript) scripting languages.
Data
Transformation -
provide powerful visual controls to allow for complex transformations of XML
content between documents:
o
Transfer
data from elements in one XML document to elements in another XML document.
o Copy the result from any valid ECMAScript/Java expression into an XML document element.
o Automatically translate and transfer codes between different XML document types via predefined code table maps.
o
Visually
perform simple and complex string manipulation transformations on XML
data. For instance, transform 123-Cat
to CAT123 (Select and Transform content by character occurrences and
absolute or relative offset lengths).
o
Test
data transformations at Design time using sample data and an action animator
for user driven walk through.
o
Perform
Deep (multi level XML hierarchy) Copy Mappings and Data Transfers.
o
Apply
String, Date, Math functions and operators to transformations.
o
Develop,
register and apply Custom functions.
o
Define
repeat and looping criteria in transformations for handling XML documents with
multiple instances of data. Repeats can be defined for Element Repeat, Data
value groups and functional expressions.
o
Apply
Aggregate calculations on multiple group levels.
o
Apply
Conditional expressions for logical branching of actions Try/Catch error
handling with Raise Error capability.
o
Read/Write
XML documents from/to user defined URLs.
o
Specify
user defined logging of any XML information available in the instance of the
component.
o Perform Static or Dynamic DOM tree transformations.
Highly Productive Visual Development - provide an environment where both business analysts and application programmers can become more effective in developing and deploying integration applications by providing:
o
GUI
Visual Design with user control of Window layouts
o
Create
Actions from selected elements on XML document trees
o
Drag
and Drop between elements on XML document trees
o
Add/Edit/Delete
Actions directly in the Action Model
o
Cut,
Copy and Paste Actions (with drag and drop)
o
Automatic
Action creation by visual Drag and Drop gestures
Runtime
Testing (Animation) -
Provide a method of easily testing and debugging the integration code from the
same interface used in development. Also
provide an easy way to test multiple sample documents, possibly from different
sources, all within the same session.
Execute
completed components and/or services within design environment. Animation provides many options for the
development including:
o
Start
and Stop of the debugging/testing environment
o
Pause
the execution
o
Set/Remove
Breakpoints
o
Step
Into/step over a loop or component call
o
Run
to Breakpoint/End
o
Disable/Enable
Actions
o
Load
XML Samples that may represent documents form different customers
o
Write
any DOM as XML Document
Basic and Advanced Mapping Actions - Allow users to construct sophisticated Action Models that define the steps for XML-based integrations. These actions include:
o
Comment
-- insert a Comment
o
Component
-- Call a Component
o
Decision
(If-then-else)
o
Declare
Alias
o
Function
-- Call a function
o
Log
o
Map
(element to element, branch to branch, etc.)
o
Send
email
o
Switch
o
Todo
o
Apply
Namespaces
o
Convert
Copybook to XML
o
Convert
XML to Copybook
o
Simultaneous
Components
o
Throw
Fault
o
Transaction
o
Try/On
Fault
o
xForm Process
o
XSL
Transform
o
Load
Resource
o
URL/File
Read
o
URL/File
Write
o
WS
Interchange (Web Service Interchange)
o
XML
Interchange
o
Browse
Waiting Activities (Process)
o
Find
Waiting Activity (Process)
o
Lock/Unlock
Waiting Activity (Process)
o
Process
Execute (Process)
o
Reassign
Addresses (Process)
o
Release
Waiting Activity (Process)
o
Break
o
Continue
o
Declare
Group
o
Repeat
for Element
o
Repeat
for Group
o
Repeat
While
o
o
Group
Aggregates (SUM, COUNT, MIN, MAX, AVG)
o
Selection
within Groups (WHERE)
o String and Numeric operations (+, -, /, *, comparison, logical)
o
Exec
SQL - JDBC available only in the JDBC Component Window
Standards
based Architecture -
exteNd Composer is 100% Java and XML and uses the standards from the W3C
including XML 1.0, XML 1.0 DTD and Schema definitions, XPath
1.0, XSLT, etc.
Deployment
– exteNd Composer
closely integrates with your application server. Users have the option to have exteNd
Composer create a variety of Service Triggers for their deployed business
objects and have these Triggers and business objects automatically installed
and compiled into the application server.
Additionally the user can choose to extend these Triggers or to invoke
the exteNd Composer Server Framework to instantiate those objects. Examples of deployment options include:
SOAP Service Triggers
Servlet based Service Triggers
EJB based Service Triggers
Reusable, extendable deployment
framework
Known issues
This release has the following known issues (workarounds are specified if known):
Composer
o
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 Forms
files that you have created in beta from the xhtml
directory to the form directory to use them.
o 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?
o The Help Menu items for Tutorials/Composer Tutorial and Documentation/Read Me are not working. You may access these files at:
..\Composer\tutorial\lessons\ComposerTutorial.pdf
..\Docs\help\Composer\relnotes.htm
o
When using the Help button (or the F1 key) in a
dialog, the browser may sometimes open the help page at the wrong location. If
this happens, go back to Composer and click the dialog's Help button (or use
F1) again. The Help page will open at the correct location on the second try.
o
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.
o Composer will allow you to create Functions with the same name within different Script files. Only the first one created can be made public.
o
xForms are not supported on WebSphere
4.0x or exteNd 4.0x.
o
To
make xForms work on WebLogic
6.1, the start up command file for WebLogic 6.1 must
be changed to have xalan.jar preceding the WebLogic classpath.
o
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).
o Rhino versus FESI -
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 v5.0 Rhino implementation. When upgrading to version 5.0 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 is also described. The potential problem areas include:
1. ECMAScript Keyword and Future Reserved Word Usage
2. exteNd Aggregate functions where(), min(), max(), sum(), avg(), and count()
3. Functions without a return statement.
1. 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 Composer’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 v4.2…
var instanceof = 12;
alert( instanceof )
In Composer v5.0, 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 v5.0 will cause component executions to fail.
Corrective Action:
When upgrading to version 5.0 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 v5.0. 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 v5.0:
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 |
|
|
|
|
2. exteNd Aggregate
functions where(), min(), max(), sum(), avg(), and
count()
Issue:
The exteNd aggregate functions are special extensions made to Composer’s ECMAScript implementation that provide powerful functionality across multiple nodes in XML document hierarchies. These functions allow the nesting of XPath expressions. In Composer v5.0, these nested XPath expressions must now be quoted strings. Below, is an expression that is shown in its valid for in v4.2 and v5.0. 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.0 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:
Composer v5.0 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 v5.0, 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.
3. Functions without a
return statement
Issue:
The Composer v4.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 Composer v5.0 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 v5.0 and ensure that every function contains an explicit return statement that gets evaluated.
When upgrading to version 5.0 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 v5.0. No application should go into a production environment without upgrade testing.
When upgrading to version 5.0 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 v5.0. No application should go into a production environment without upgrade testing.
o Do not use the words Input, Input1 -- Input(n), Output, Output1 -- Output(n). These are exteNd Composer-reserved words.
o If you copy four columns of data (e.g. 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.
o Validation is required after loading a new Sample document in Composer.
o
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 selecting the RMB on the DOM and picking
"Validate".
o 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.
o The Web Service Interchange action requires WSDL to exist in order to create one. If one attempts to create a WS Interchange action and no WSDL resources exist, a dialog will appear explaining this. If one does have WSDL resources and creates the WS Interchange, but after that deletes all WSDL, the user will be then unable to edit the existing action.
Workaround: Create a new WSDL resource and then edit the action.
o 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.
o 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.
XML
Mapping and Actions
o After editing a Map action the document tree(s) will redraw and only the current tree node will not collapse.
o 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 CHILDELMENT. 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>
o In the Map Action content editor you cannot select text that is not displayed inside the edit control visual boundary.
o
Closing
a loop action dialog with the enter key rather than a mouse click causes the
action model frame to scroll to the bottom.
o 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.
o
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.
o 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.
o 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.
o The Send Mail action allows one to choose a connection to send mail via an authenticated SMTP server. This feature does not work. A patch is forthcoming.
JDBC
Component Editor
o
If
a JDBC query returns certain unprintable characters, this can cause the
creation of an invalid XML document.
Workaround: Preprocess any documents containing this type
of information prior to writing out the XML document.
NOTE: exteNd Composer DOES handle and convert all XML reserved characters.
o When using drag and drop to build a JDBC Insert Operation, we have experienced the following behavior:
o When dragging a DOM element into the SQL STATEMENT pane single quotes are wrapped around all element names the column type is not recognized.
o Commas are not added after each value when dragging them into the SQL statement.
o
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.
o
The
keyword "FROM" is
missing from the Delete tree in the JDBC keyword selection menu.
o
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.
Importing
xObjects
o
When
importing, if a name has invalid characters, an incorrect error message is
displayed. For example, if you do an
import of anything in exteNd Composer and output in a file name of
"john><\Doe". Instead of
getting an invalid filename error and asking the user to retype a valid name,
the error is "Invalid XML component" and you are exited from the
window.
Animation
o
Composer
caches resources during animation. To
be sure that you are executing up-to-date resources during construction of a
component always save, close and reopen Objects prior to retesting.
o
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.
o Composer 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.
o
Animation
does not stop at the breakpoint set in 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.
Workaround: Set a breakpoint on the Component action in
the parent component. Run to that
breakpoint first and then Step Into the child component. Once in the child component, press Run To
Breakpoint, again.
WSDL
o
If
you have WS Interchange actions that access other Composer 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.0 updated WSDL for their old Composer
SOAP Service.
o
The
WSDL spec allows a MIME part not to 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 where this attribute is left out. 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 Composer 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.
o
In
Composer 5.0, when opening a WSDL created in a previous version of Composer
(e.g. Composer version 4.2), the user 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 5.0 uses WSDL 1.2. The error/warning is informational. It does not affect execution. The error/warning correctly indicates that a
WSDL 1.0 WSDL does not pass WSDL 1.2 validation.
o
All
WSDL definitions must contain a "name" attribute. When creating a new WSDL file that is NOT
associated with an existing Composer 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 Composer or copying WSDL in
from an external source, be sure to define a "name" attribute.
Composer 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
Composer):
<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 WSDL Generation
Limitations
o WSDLs that have RPC binding styles, currently have the following limitations:
o The message portion of the WSDL file can only contain message parts that are simple types. Complex types are not currently supported.
o exteNd Composer 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.
o It is not possible to generate WSDL documents for exteNd Composer services that use input or output documents that have a category of {System} and a template name of {Any}.
o When creating a new WSDL resource, use a valid QName as specified by http://www.w3.org/XML/Schema
Subprojects
o 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.
Deployment
o
When
deploying a Composer 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.
o
When
deploying any EJBs to WebLogic
8.1, the following warning will appear in the WebLogic
Console. This warning can be ignored.
<Warning>
<EJB> <BEA-010001> <While deploying EJB 'com.sssw.b2b.xs.ost
ore.com50.process.PEA.ResourceBean.GXSEJBResource', class
com.sssw.b2b.xs.ostore.GXSEJBResourceBean was loaded from the system classpath. As a result, this class cannot be reloaded while
the server is running. To prevent this behavior in the future, make sure the
class is not located in the server classpath.>
o
After deploying a project with a SOAP Service Trigger
and its associated WSDL resource chosen in the deployment panel, if you happen
to 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 WSDL
Resource via a browser the user will receive an error saying, "Unable to
retrieve the contents of the resource".
o
For
Composer services to be successfully deployed as EJB service triggers, or
process Components to be successfully deployed, it is necessary to perform a
quick step. In the Composer/lib folder
make a copy of the xcs-all.jar and name the copy
xcs-all-ws50.jar.
o
Tomcat
deployment JSP states to select EAR file when we deploy a WAR file.
o
Deploy
fails when a web service calls a process with multiple inputs.
o
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 IE
'Check for newer page versions' is set to 'Never'. To avoid the problem, change the setting to
‘Every visit to the page’.
o
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 IE, go into Tools, Internet Options, Temporary Internet files, Settings,
and change the Check for newer versions of stored pages to Every visit to the
page.
o
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.0. You will also
need to re-initialize the database.
o
Every
time a deploy is done and there is an EJB the following message appears in the
exteNd Composer 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)
o
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.
o
After
deploying an EJB servlet to exteNd Application Server using exteNd Composer
5.0, an error is generated when trying to access an EJB from exteNd Composer
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 Composer Configuration dialog. The Configuration dialog is accessed from the Tools/Configuration menu. The Novell HTTP Handler has some problems with secure sites when using Composer HTML Connect, therefore, we recommend using the Composer Handler unless you are accessing EJBs deployed to a Novell server.
o
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.
o
Deploying
to WebSphere: A typical deployment jar
file would look like this "tutorial.jar". The .jar extension CANNOT be uppercase
otherwise when deploying an EJB, the jar file will not be recognized by the
WebSphere Application Server and the user will get an error in the Deployment
report.
o
Two
users should not concurrently deploy to either WebSphere or WebLogic
Application Servers. The deployments in
this case might not successfully complete.
Configuration files
o
Anything
after a period is truncated from a project name. For example, if you create a new project and
call the project "Tutorial(5.0)" 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 Composer Pane.
o
If
installing Composer 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. |
Licenses
o When using a Professional license, some resources are not available including JSPs, Images, and Deployment resources. The server console currently reports these as Loaded with no license string. It also shows them as disabled, and if one tries to enable them, the user is unable to do so. This is expected behavior.
NTLM Authentication with Proxies
o
The
following steps describe how to configure NTLM authentication with proxy
support for Composer Server.
1. Make your settings in Designer via the Tools | Preferences | Designer
tab dialog.
2. Exit Composer.
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 appServer.
5. Paste the element into the Composer Server
xConfig.xml file in the ..\AppServer\Composer\lib
directory. Be sure to place it under the
<XCONFIG><SYSTEM> branch.
6. Restart the appServer.
Note: When restarting the App Server, you should use the following
case-sensitive command:
silverserver +dhttp.proxyHost=<name of proxy server> +dhttp.proxyPort=<portnumber>
Note: https through an NTLM proxy is not supported
exteNd Application Server
o The installation script to restart the Novell application server will stop but not restart it if the Novell application server was started w/ the -n "-nomonitor" command line switch.
WebLogic
Application Server
o When installing Novell exteNd Composer 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.
o 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 exteNd Composer. Then in the general tab check Deployed.
o 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
o For WebLogic, the installation of the Process50 database will be skipped since we cannot predict what database will be installed. Users will need to do this manually for WebLogic installs (e.g. the way it worked prior to 5.0) by accessing the Server Console and configuring the Process database using the RDBMS of their choice.
o Install to Weblogic 8.1 on Redhat hangs and needs to be manually stopped by install is complete.
WebSphere Application
Server
o Composer 5.0 consoles cannot be accessed when WebSphere 4.0.2 and WebSphere 5.0 are in secure mode. Once the Composer console has been installed in a secure WebSphere environment, you must go into the WebSphere Administrators console, click on the exteNd Composer enterprise application. Scroll down to the 'Map security roles to users/groups' link and click it. Finally, specify either specific users and/or groups to map to the Composer Administrators role, or you can provide looser control with 'All authenticated', or no restriction with 'Everyone'. Once you have finished your elections, remember to save the changes so that the applications configuration is updated. Once saved, a restart of the exteNd Composer application is necessary for the security mapping to take affect.
o When installing to a secure WebSphere 5.0 server, ensure the Global Security >> Java 2 Security is NOT checked/enabled. If this is checked/enabled the Composer Consoles will fail.
o The user may deploy to multiple web applications within a single Application Server in WebSphere as well as multiple EJB Containers.
o For WebSphere, the installation of the Process50 database will be skipped since we cannot predict what database will be installed. Users will need to do this manually for WebSphere installs (e.g. the way it worked prior to 5.0) by accessing the Server Console and configuring the Process database using the RDBMS of their choice.
o For exteNd’s implementation of Web Services (WSSDK) to run under WebSphere 5.0, we need to manually copy the ../Composer/lib/saaj-api12.jar file to the .../WebSphere/AppServer/java/lib folder.
o
When running a process in the WebSphere 4.0 app
server, if the project does not contain any scripts, an error is displayed on
the server console: "The requested
resource 'ver1/process/PS/functions/Function.xml'. This is informational only. It can be prevented by adding at least one
Custom Script Resource that contains at least one function in all projects that
contain process components.
Tomcat
o 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.
Netware
o For Netware, the installation of the Process50 database will be skipped since we cannot predict what database will be installed. Users will need to do this manually for Netware installs by accessing the Server Console and configuring the Process database using the RDBMS of their choice.
Red Hat
o The app server is designed to run under the root uid. If this is not done, there will be errors during deployment of Composer objects. If one chooses not to run the app 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.
Other Issues
o WS Interchange Header Support: A header may be added via the WS Interchange action however the change is not included in the runtime.
o The Timer Trigger has an option to fire recurring weekly where on chooses the day the trigger is to fire. The days are off by one. If one wishes the trigger to fire on Monday, select Tuesday. Note: It is not possible to fire on weekly on Saturday. This can be worked around by firing daily on Saturday.
o Changing the log level from the exteNd Composer Console does not take affect until after the server has been started.
o Custom script functions called thru the "userfunc:" escape mechanism within xpath expressions must return objects with a toString() method that returns the desired output.
o 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.
o Composer 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.
o Under certain circumstances changing Servlet types of an already deployed application causes errors during server import/build.
o 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. This problem can be fixed by downloading a new copy of the soap envelope schema. This can be found in http://schemas.xmlsoap.org/soap/envelope/. It should be placed in the D:\Program Files\NovellSuite\exteNd5\Common\Resources\SchemaCatalog directory.
Installation Procedure:
o After installing exteNd Composer Enterprise Edition v5.0 on WebSphere 4.0.4, the service under NT Server must be restarted as well as the Application Server within the Administration Console of WebSphere Application Server.
o Note: The user will then be able to verify the install was a success by accessing the exteNd Composer Enterprise Edition Console. (Example: default_host/exteNd Composer/console)
o When installing the Composer Connectors to the core exteNd Composer Enterprise Edition the user must only restart the Application Server within the WebSphere Administration Console. The user may then verify the installs by using the exteNd Composer Enterprise Edition console.
o As an aside, the user should be cautious when installing to multiple instances of the Application Server on WebSphere because multiple installs should only be used to establish multiple Application Servers with various configurations. These configurations do not include exteNd Composer Enterprise Edition or any of the Composer Connectors due to the fact that there is only one xconfig.xml under Composer/Designer/bin.
Manual Uninstall Procedure:
o In the WebSphere Administration Console, find the Application Server where exteNd Composer is installed. Within the Application Server, there is a Servlet Engine that hosts the available web applications on that particular Application Server.
o Within the Servlet Engine there should exist an exteNd Composer web application. The user must then shut down the current Application Server and remove the exteNd Composer Web Application and its contents.
o Under the Application Server the user must then remove the command line arguments that reference exteNd Composer. 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.
o The user must also remove the Dependent Classpath associations that exist under the core node in the Administration Console under the default tab (General).
o The final step would then be for the user to remove the exteNd Composer folder from within the WebSphere parent directory (WebSphere/AppServer/exteNd Composer).
o Note: When removing the exteNd Composer 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 exteNd Composer folder from the WebSphere parent directory.
Copyright © 2004 Novell, Inc. All rights reserved.