Release Notes for iAS Enterprise Connector for R/3

Version 6.0 SP1[and for iAS version SP2]

Updated October 6, 2002




These release notes contain important information rfelating to version 6.0 [SP1] release of iAS Enterprise Connector for R/3. New features and enhancements, installation notes, known problems, and other late-breaking issues are addressed here. Read this document before you begin using iAS Enterprise Connector for R/3.

An electronic version of these release notes can be found at the Sun ONE documentation web site: http://docs.sun.com. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and manuals.

These release notes contain the following sections:




What's New in iAS Enterprise Connector for R/3, Version 6.0

These release notes detail the changes, resolved issues and known problems for the iPlanet Application Server Enterprise Connector for R/3, version 6.0 SP1 and for iAS version SP2 releases.




Software and Hardware Requirements

The following table lists the hardware and software requirements for installing and running the R/3 Enterprise Connector.



Table 1    Software and Hardware Requirements

Component

Requirement

Computer and Operating System 

One of the following systems:

  • Intel Pentium microprocessor running Microsoft Windows NT version 4.0 with Service Pack 5.

  • Sun SPARC running solaris 2.6.

 

Memory 

Per CPU: 256 MB minimum; 512 MB recommended. 

Available disk space 

Total disk space: 200 MB on Windows NT, 400 MB on Solaris. 

CD-ROM drive 

CD-ROM drive 

Network software 

TCP/IP 

Browser software 

One of the following browsers:

  • Netscape Communicator 4.5 or later

  • Microsoft Internet Explorer 4.0 (Windows NT only)

 

R/3 System 

Versions 4.5B, and 4.0B installed. 

Other software 

The following additional software is required:

  • iPlanet Application Server 6.0 SP1 or SP2

  • Unified Integration Framework 6.0 SP1

  • The iPlanet Application Server and Unified Integration Framework must be installed prior to installing the R/3 Enterprise Connector.

 




Installation Notes

Please make sure all iPlanet Application Server 6.0 SP1 or SP2 components and the Unified Integration Framework (UIF) SP1 have already been installed on the server machine. The iPlanet Enterprise Connector for R/3 must be installed on the same machine as the iPlanet Application Server.

Installation

Installation of the product is as follows:




Post-Installation Issues: iAS SP2 Users Only

Due to changes in iAS 6.0 SP 2 deployment tools and directory structure, files need to be copied manually to run the R/3 Connector 6.0 SP1 samples with iAS 6.0 SP2.

For NT:

The following tasks should be performed to copy the files manually for the following samples:

  1. BAPI_CUSTOMER_GETDETAIL

    Copy Execute.properties and Execute_properties.properties

    from

    <iAS Install Dir >\ias\APPS\BAPI_CUSTOMER_GETDETAIL\BAPI _CUSTOMER_GETDETAIL

    to

    <iAS Install Dir >\ias\APPS\BAPI_CUSTOMER_GETDETAIL

  2. BAPI_CUSTOMER_GETDETAIL_EJB

    Copy Execute.properties and Execute_properties.properties

    from

    <iAS Install Dir >\ias\APPS\BAPI_CUSTOMER_GETDETAIL_EJB\BAPI _CUSTOMER_GETDETAIL_EJB

    to

    <iAS Install Dir >\ias\APPS\BAPI_CUSTOMER_GETDETAIL_EJB

  3. BAPI_CUSTOMER_GETSALESAREAS

    Copy Execute.properties and Execute_properties.properties

    from

    <iAS Install Dir >\ias\APPS\BAPI_CUSTOMER_GETSALESAREAS\BAPI _CUSTOMER_GETSALESAREAS

    to

    <iAS Install Dir >\ias\APPS\BAPI_CUSTOMER_GETSALESAREAS

  4. BAPI_EMPLOYEE_GETLIST

    Copy Execute.properties andExecute_properties.properties

    from

    <iAS Install Dir >\ias\APPS/BAPI_EMPLOYEE_GETLIST\BAPI _EMPLOYEE_GETLIST

    to

    <iAS Install Dir >\ias\APPS\BAPI_EMPLOYEE_GETLIST

For Solaris:

The following tasks should be performed to copy the files manually for the following samples:

  1. BAPI_CUSTOMER_GETDETAIL

    Copy Execute.properties and Execute_properties.properties

    from

    <iAS Install Dir >/ias/APPS/BAPI_CUSTOMER_GETDETAIL/BAPI _CUSTOMER_GETDETAIL

    to

    <iAS Install Dir >/ias/APPS/BAPI_CUSTOMER_GETDETAIL

  2. BAPI_CUSTOMER_GETDETAIL_EJB

    Copy Execute.properties and Execute_properties.properties

    from

    <iAS Install Dir >/ias/APPS/BAPI_CUSTOMER_GETDETAIL_EJB/BAPI _CUSTOMER_GETDETAIL_EJB

    to

    <iAS Install Dir >/ias/APPS/BAPI_CUSTOMER_GETDETAIL_EJB

  3. BAPI_CUSTOMER_GETSALESAREAS

    Copy Execute.properties and Execute_properties.properties

    from

    <iAS Install Dir >/ias/APPS/BAPI_CUSTOMER_GETSALESAREAS/BAPI _CUSTOMER_GETSALESAREAS

    to

    <iAS Install Dir >/ias/APPS/BAPI_CUSTOMER_GETSALESAREAS

  4. BAPI_EMPLOYEE_GETLIST

    Copy Execute.properties and Execute_properties.properties

    from

    <iAS Install Dir >/ias/APPS/BAPI_EMPLOYEE_GETLIST/BAPI _EMPLOYEE_GETLIST

    to

    <iAS Install Dir >/ias/APPS/BAPI_EMPLOYEE_GETLIST




Upgrading From the Enterprise Connector for R/3 Version 6.0.

Due to changes in the repository structure to support internationalization (I18N), you need to recreate all the R/3 datasources after installing the UIF and the R/3 connector. You also need to perform datamining after you recreate the datasources. All user mapping information is overwritten, however, you may backup user mapping information for a given datasource from the previous version and use it in this release.

The procedure for backing up and re-using user mapping information is as follows:

  1. Before installing the UIF v6.0 SP1, backup the ENTITY_MAPPINGS nodes from each R/3 Datasource in the UIF repository, using the

    Repository Browser's export utility (for example, DS1userbackup.xml DS2userbackup.xml...).

  2. During UIF installation, the installer prompts you to overwrite the existing BSP node. Select YES to overwrite the existing BSP node.

  3. Use any editor to change all the occurrences of "sap" and "SAP" to "R3" in the exported XML file (for example, DS1userbackup.xml).

  4. Save the modified XML as DS1user.xml.

  5. For NT: Copy the repository.dtd file from the <iasinstalldir>\ias\APPS\adapters\sap\samples\metadata directory to the directory where modified XMLs are stored.

    For Solaris: Copy the repository.dtd file from the <iasinstalldir>/ias\APPS/adapters/sap/samples/metadata directory to the directory where modified XMLs are stored.

  6. Import the DS1user.xml using the Repository Browser's import utility under the corresponding DataSource DS1.

Change all references to Sap (for example "SAPproperties") in the Servlet/EJB Source code to R3 (for example "R3properties").

Note that the AutoCommitProperty parameter that was in SapProperties has been removed.




Documentation

This product includes an Administrator's and a Developer's Guide. The installer copies these publications to the ias/APPS/docs/sap subdirectory of the root installation directory of your iPlanet Application Server. These documents are available online in PDF and HTML formats. To locate these files, use the following URL:

http://docs.sun.com

Adobe Acrobat 4.0 and PostScript printer with PS level 2 fonts are required to print the PDF version.

The following lists corrections to the documentation posted on the web site.

Documentation Corrections in the Developer's Guide


Code Example 3-5 Setting Up and Executing the Function Item

Change:

public void execute () throws Exception, BspException

to

public void execute (String WebUserId) throws Exception, BspException

After the following code:

sp = getServiceProvider(runtime);

if( sp != null )

{

Add the following lines:

IBSPDataObject config=sp.getConfig();

config.setAttrFString("WebUserId",WebUserId);

Documentation Corrections in the Administrator's Guide


High-level System Architecture

In Chapter 1 in the High-level System Architecture section, the text should read: "Before you receive a client request, the daemon needs to be started manually. See Launching the Daemon in Chapter 2. The connector notifies the daemon of the request using a proprietary protocol. The daemon either creates a new worker process to process the request or passes on the request to an idle worker process.


Entity Mapping

You must create at least one entity and one user after creating a new data source.




Resolved Issues

The following issues have been resolved in the iPlanet Application Server Enterprise Connector for R/3 6.0 Service Pack 1 release. T



Table 2    Resolved Issues

ID

Summary

393945 

Exceptions now contain the RFC error code.  

395617  

You can now modify POOL parameters such as MaxPoolSize and SteadyPoolSize with the Management Console. 

398166 

The sample has been replaced with a clearer, more descriptive sample. 

402121 

An entity can not be deleted if there are mapped users. 

480141 

Improved Pooling. 

480141 

The R/3 connector can now be used with R/3 systems configured for load balancing. 

499981 

Internationalization (I18N) support. R/3 National Language Support is included in the iPlanet Application Server Enterprise Connector for R/3 SP1.  

516498 

The documentation and code has been revised to contain references to R/3 instead of SAP. 

519068 

A screen has been added at the end of the procedure for creating a new data source using the Management Console. The new screen will alert the user if there is an existing data source with the same name and ask, Yes or No, if the existing data source should be over-written. If you choose the Yes option, the data source will be over-written; if you choose No, the data source that you created will be deleted. 

N/A 

You do not have to restart the Management Console after editing a data source. 

N/A

 

A Refresh button was added to the Repository Browser that allows the user to refresh the repository without closing the repository and re-activating. 




Known Problems and Limitations


ID:519658

iPlanet Application Server Registry Corruption on Solaris

Problem:

The installation of the iPlanet Application Server Enterprise Connector for R/3 may corrupt the ias/registry/reg.dat file.

Workaround:

Before you install the connector, backup the ias/registry/reg.dat file. You will then be able to recover the registry contents.


ID:519994

RFC exceptions may cause an increase KJS memory usage.


ID:519984

The number of workers ranges from zero to maxpoolsize. The number of workers does not decrease even when there is little or no usage of the connector.


ID:517183

Uninstaller Removes Common Files in Multi-connector Installation

When uninstalling one of several connectors, such as R/3, PeopleSoft, or CICS, the common directories /ias/Apps/console and /ias/Apps/ecu may be deleted. It is necessary to copy these directories back to Apps directory from /ias/Apps/UIFbackup for the R/3 connector to function correctly.

To uninstall a connector from a Windows NT that has multiple connectors installed:

If you want to uninstall a connector from an NT machine that has more than one connector installed, perform the following tasks.

  1. Uninstall the connector. Refer to Chapter 2 in the Administrator's Guide.

    During the uninstallation procedure the connector files shown in the right panel, as seen in the screen capture below, are removed from the iPlanet/iAS6/ias directory and moved to the UIFbackup/console directory. The connector files need to be copied back to their original location.



  2. Copy the console specific directories, the top level directory and the connector specific directories to the ias/Apps/console for the following folders:

    • constants

    • exceptions

    • ftp

    • gui

    • model

  3. All the other directories, with all their included files, and the LocalDebug.class should be copied back.

  4. Copy the following connector files to the console directory: Appltab and ldobuffer.dll.

To uninstall a connector from a Solaris machine that has multiple connectors installed:

If you want to uninstall a connector from a Solaris machine that has more than one connector installed, perform the following tasks.

  1. Uninstall the connector. Refer to Chapter 2 in the Administrator's Guide.

    During the uninstallation procedure the connector files are removed from the iPlanet/iAS6/ias directory and moved to the UIFbackup/console directory. The connector files need to be copied back to their original location.

  2. Copy the console specific directories, the top level directory and the connector specific directories to the ias/APPS/console for the following folders:

    • constants

    • exceptions

    • ftp

    • gui

    • model

  3. All the other directories, with all their included files, and the LocalDebug.class should be copied back.




How to Report Problems

If you have problems with your system, contact customer support using one of the following mechanisms:

Please have the following information available prior to contacting support. This helps to ensure that our support staff can best assist you in resolving problems:

Copyright © 2002 Sun Microsystems, Inc. All rights reserved.

Last Updated October 06, 2002