Technical Notes |
|
This document describes important information about version 9.6 of Verastream Integration Broker. In addition to this document, please see the file vsreadme.txt, located in the root folder of your product CD for further information. This document is presented in the following sections:
Verastream's Composite Component Interface Wizard guides you through the creation of a composite component interface, which is a definition of methods and parameters that wraps one or more Verastream components or other technologies together. All interface elements of a component, that is its methods, events, parameters, connection information, adapter metadata, table data, documents, and data sets defined within existing components can be reused without the need to redefine them in the composite component interface. For further details, see the Verastream online help.
The CSX configuration utility allows you to import and export CSX pool settings, thus enabling you to quickly and easily duplicate switches from one configuration to another. You can either import and export switch settings from either the graphical user interface of the CSX configuration utility or from the command line. For further details, see the Verastream online help.
Process Integrator now supports descriptions for objects.
In Process Integrator, when you drag a field and drop it on a parameter or field assignment of different type, a conversion function that performs the required conversion will be automatically inserted into your script.
While building a script in Process Integrator, statements that contain an illegal field or parameter assignment will be outlined in red in the Script Pane to indicate that they contain one or more errors.
Two new helper functions, dataInspector 'show' and externalProgram 'execute' have been added to Process Integrator. The dataInspector 'show' function allows you to display and modify selected data within your composite application during runtime. This makes it possible to inspect, at the data level, the current value of fields, structures, tables, and streams at any point during the execution of your composite application.
The externalProgram 'execute' function allows you to run an external program from within your composite application. In previous versions, this function was only available from the Verastream Scripting Language (VSL) scripts.
For further details, see the Verastream online help.
It is now possible to view and edit modules in Process Integrator. In previous versions, the only way to view and edit modules was from the Component Developer application. For further details, see the Verastream online help.
Data Integrator now supports descriptions for all objects in a scheme. Whenever you click a scheme object in Data Integrator, a new Description tab is available which you can use to create meaningful descriptions for scheme objects.
Data Integrator now supports the use of user-defined expression functions in Data Integrator schemes.
Verastream is now able to read COBOL Copybooks from partitioned data sets (PDS). For further details, see the Verastream online help.
Component Directory is now named VCP Component Directory Explorer to clarify that it is applicable only to Verastream VCP server components (not other component types). Running server components are highlighted in green for easy identification. The working directory and start command are shown at the bottom of the VCP Component Directory Explorer (rather than columns) to eliminate the need for horizontal scrolling to see this information.
Online help documentation is now automatically installed with the product. You no longer need to separately download and install online help after product installation.
Following is a list of known issues for this version 9.6 release of Verastream Integration Broker:
Following is a list of known issues for this 9.6 release of Verastream for Siebel and the Siebel adapter:
In Process Integrator, if you are unregistering a composite application using a user account and you provide invalid username/password credentials, the error message "Invalid password or no privileges to check passwords. Do you want to continue?" appears. If you click Yes, the composite application is unregistered, even though the username/password credentials are invalid.
A demonstration application file named bwschedule.lgc, which is part of a series of files installed in the examples/bwschedule folder intened to show Verastream Integration Broker's Schedule the SAP BW Scheduler abilities, cannot be opened in Process Integrator.
Because the SAP/R3 demonstration is a COM-based application, it will not function on the Solaris platform.
If you stop an outbound component that implements an Integration Object (IO) or Virtual Business Component (VBC) interface to Siebel, you cannot restart it. IO components fail to restart with no error message, and VBC components fail with the following error message:
External source for Buscomp does not support field managerThe sample composite application named busserv.lgc, which demonstrates how to use Business Services with Siebel, does not function on the Siebel 2000 platform.
You must make the following modifications to the Verastream Gateway Business Service on Solaris. Follow these steps:
#define GATEWAY_DLL "vssblgw.dll"to
#define GATEWAY_DLL "vssblgw.so"Verastream connects to Siebel through either Siebel COM Data Server or Java Data Beans. For instructions on how to connect to Siebel via COM or JDB, refer to Siebel Connection Management. If you connect to Siebel via Java Data Beans, you will need to do the following:
In Siebel 7.5, these are:
In Siebel 7, these are:
In Siebel 2000, these are:
| Siebel release |
Java Data Beans |
| Siebel 99.X (5.X) |
Not Supported |
| Siebel 2000 (6.X) |
Supported JDK 1.1.7 |
| Siebel 7 |
Supported JDK 1.2.2 |
| Siebel 7.5 |
Supported JDK 1.2.2 |
If your siebel.cfg file contains the following settings:
EnableScripting=TrueScriptingDLL=sscfjs.dlland you use COM to connect to the Siebel repository, when you attempt to add a record using account.addrecord, the following error messages display:
COMPONENT 'SiebelSAPLink' METHOD 'getSblLinkToSap: Cannot connect to serverRequest for Address '/.Demo/SiebelSAPLink' failed: Unknown addressTo work around this problem, comment out the two lines specified above in the Siebel.cfg file.
As shipped, the properties in the Siebel Business Component Account sample file (vs_vbc_acc7.sif) are incorrect. To correct the problem, follow these steps:
Remote Source = 'anything'
Service Name = 'Verastream VBC Integration'
Service Parameters = <empty>
If you connect to your Siebel Server through a Java Data Beans connection, the error message "Value not found in listbox" may display when you attempt to select a value for a property from a hierarchical list.
If you add a component from the Siebel repository to a composite application in Process Integrator and then delete it, the next Siebel component you add will default to the properties of previously deleted Siebel component. In some cases, these properties may be incorrect for the current component, therefore be sure to check the default properties of Siebel components you add from the repository.
If the Siebel Down Customers demonstration fails with the error message specified above, follow these steps:
@path/bin/nova.exe"@path/bin/nova.exe"If you see an error such as "Component can not connect to server" or "Registration failed" when running the Siebel Sample Integration Script, you may be able to fix the problem by editing the snregtab.dat file. In the file, change this line:
~C:\Program Files\Verastream\bin\nova.exe -w -eserve message so that it includes quotes around the path:
~"C:\Program Files\Verastream\bin\nova.exe" -w -eserve messageFinally, remove two spaces from the beginning of the line so that the line ends in the same place as before.
You can establish a live connection to a Siebel repository using JDB (Java Data Beans) or COM. If you have multiple connections using different types of connections, you may find that your connections are lost as you switch from one repository to another. If this happens, try to exit and then restart the Verastream Repository Manager. (This problem is due to a known Siebel issue.)