Unified Integration Framework (UIF)
Version 6.0
Release Notes
Updated June 20, 2000
- Summary
- Installation and Configuration
- Exception Management and Logging
- Documentation
- Known Problems
The Unified Integration Framework (UIF), was formerly known as BSP. These release notes detail the changes and known problems for UIF 6.0.
Installation and Configuration
Please make sure all iPlanet Application Server components have already been installed on the server machine.
- for Windows NT, run setup.exe in the insbsp directory
- for Solaris, untar the insbsp.tar file and execute setup in the insbsp directory from the command line
The machine should not be rebooted after the UIF installation if an adapter will be installed. To install any adapter on Solaris, do not remove the install.ini.<username> file in /tmp directory. Run the installer under the same user id.
Note: On some Windows NT machines, Uninstall does not work and the following error message appears:
Uninstall is unable to load the drive/temp/uninst/bsp/insbsp.dll
To workaround, copy the file mfc42.dll from the CD to the winNT/system32 directory. This will replace the existing mcf42.dll.
Exception Management and Logging
The exception and logging mechanism provides the following functions:
- writes messages into a default iPlanet Application Server log
- enables the administrator to switch between varying logging levels at runtime
Only one generic Unified Integration Framework (UIF) exception message is ever thrown. The exception messages that are thrown relate to data object APIs or enterprise connector errors. The programmer does not have to handle exceptions since the BspException extends java.lang.RuntimeException. The application programmer can safely skip writing special error-handling code.
Documentation
This product includes a Developer's Guide. For other documentation please refer to the docs directory.
Adobe Acrobat 4.0 and PostScript printer with PS level 2 fonts are required to print the PDF version.
Note: The documentation shipped with this product has been updated. Please download current documentation from:
Known Problems
Array Element Type Enforcement
Arrays are used to store elements of the same type; however, homogeneity is only enforced if using the addElem( ) method to add elements to arrays. Use the addElem( ) method, and not methods in the IBSPDataObjectList interface, to add elements to arrays.
createInstance( )
The createInstance() method creates an instance of an IBSPDataObject object (not an instance of IBSPDataObjectInfo).
DataObjects Cannot Be Shared
The Java API must not be used in such a manner that two dataobjects end up sharing the same dataobject (or some such restriction).
DataObject Is Not Thread Safe
Only sharing of read-only objects, such as DataObjectInfo, is supported.
dumpDataObject Method Dumps to OutputStream
IBSPDataObject.createDumpToOutputStreamVisitor (OutputStream os) has been added to allow dumping to any output stream, including an output stream on a file.
Duplicate Repository Nodes
Duplicate repository nodes are not allowed; however, this restriction is not enforced. Duplicate nodes cause unpredictable Repository Browser behavior; for example, the browser may not refresh properly. Errors may also occur if the XML file contains a duplicate node. Correct the error and reimport.
Hierarchy of DataObjectExceptions Has Been Added
java.lang.OutOfMemoryError netscape.bsp.dataobject.exceptions.IllegalPathException netscape.bsp.dataobject.exceptions.IllegalRecursionException netscape.bsp.dataobject.exceptions.FileNotFoundException netscape.bsp.dataobject.exceptions.FiledNameIsNullException netscape.bsp.dataobject.exceptions.FiledNameTooLongException netscape.bsp.dataobject.exceptions.TypeMismatchException netscape.bsp.dataobject.exceptions.IndexOutOfBoundsException netscape.bsp.dataobject.exceptions.MethodUnsupportedException
HTTP Port Missing in Sample URL
The Program menu link to the Samples page assumes the web server is running on standard http port 80. If this is not the case, the link fails. Manually insert the port number in the URL location on the web browser and the page appears.
IBSPDataObject.equals( )Method Has Been Added
This method allows comparison of two IBSPDataObjects.
Log File Too Large
Currently all connector data source XML files (sample, as well as template) will set the pooling debugLevel=1. The administrator can change this level to 0 directly from Directory Server user bsp tree.
startconsole.sh Has Been Removed from the Makefile
Ignore any instructions related to startconsole.sh. With the reduced stack size requirement of the repository, -ss options are no longer needed in shell scripts.
StringMaxLen
Replace GetElemStringMaxLen with FStringMaxLen.
UIF Runtime Connection Pool Exhausted
Applications must call disable( ) on an IBSPServiceProvider before exiting an EJB or servlet. If disable( ) is not called, the connection stays alive until it is timed out, possibly exhausting the connection pool.
Uninstall Does Not Work on Machines without Visual Studio Installed
The following error message appears:
Uninst is unable to load the drive/temp/uninst/bsp/insbsp.dll
Work around: Copy the file mfc42.dll from machine with Visual Studio to directory: WinNT/system32; and replace the existing mfc42.dll. Note: the cd contains the “mfc42.dll” file. On machines with Visual Studio installed the Uninstall works exactly as required and all the specified files are removed.
Uninstall Erases Common Files
During uninstall of SAP R/3 or PeopleSoft enterprise connectors, common files, such as libldobuffer.so (Solaris), ldobuffer.dll (NT), and console manager files may be erased. Workaround: after uninstall, manual re-copy all erased files from the backup directory ias/APPS/UIFbackup.
Uninstalling Enterprise Connectors
When uninstalling one of several connectors, such as SAP or PSFT, the Appltab file in the APPS/bin will be deleted. It is necessary to copy the Appltab file back for other connectors to function. Uninstalling a single connector will delete some files, but not de-register the connector; reinstalling will correctly update the node and files.
Use GX.Release( ) for Freelist Advantage
For freelists to be effective, the servlet /EJB should execute a GX.Release(obj) on any object returned by the UIF API as soon as it is done with it, and before exiting the EJB /servlet. This will return dataobjects to freelists and avoid unnecessary object creation under peak load. The following programming constructs are not recommended, since they implicitly create wrapped java objects, which can only be garbage collected and not GX.Released:
((IBSPDataObjectStructure)datablock.getDataObject("X")).getAttrString("Y")
and local variables implicitly go out of scope. A local variable must be explicitly GX.Released before it goes out of scope.
Copyright © 2000, Sun Microsystems Inc. All rights reserved.