IBM WebSphere Adapter for mySAP.com CSD 1 - Readme

Welcome to IBM(R) WebSphere(R) Adapter for mySAP.com CSD 1

This file contains information you need for installing IBM WebSphere Adapter for mySAP.com CSD 1. For the most up-to-date information about WebSphere Adapters, visit the Web site: http://www.ibm.com/software/ts/mqseries/adapter/ws/

This CSD contains the following modifications:

The resource adapter archive is now plugable into WebSphere Studio Application Developer Integration Edition (WSADIE 4.1.1) and provides tooling support in this environment. As a result the service oriented programming model of WSADIE is extended with the capability of accessing SAP R/3 data and business logic. After importing and deploying this version of the resource adapter in WSADIE, it is possible to browse BAPIs/RFCs of SAP R/3 systems and add WSDL (Web Service Definition Language) representations of the desired function modules. The WSDL representations can further on be used to generate Java proxies for these BAPIs/RFCs (Java beans and/or stateless session enterprise beans). These beans can be used in customer developed applications/servlets/enterprise beans to access SAP R/3. The WSDL representations can also be used in the service flow editor of WSADIE. A possible usage scenario is the composition of multiple BAPI/RFC calls and/or invocations of other services, e.g. a CICS transaction or a web service.
An additional resource adapter archive (sapcsd_notx.rar) with transaction attribute set to NoTransaction is provided, i.e. the resource adapter will not take part in global transactions. This behaviour may be necessary if you are using the WebSphere Adapter for mySAP.com in a 2PC (two phase commit) scenario with last resource optimization and an additional 1PC resource. Since last resource optimization only works with one single 1PC resource this scenario wouldn't work with the original resource adapter archive (sap.rar, sapcsd.rarwith transaction attribute set to LocalTransaction). The default behaviour of the sapcsd_notx.rar is to autocommit every BAPI/RFC call. Please be aware of the consequences when using the resource adapter in the NoTransaction mode. E.g. the following scenario is possible: During a global transaction some BAPI calls are exectuted successfully, i.e. they are autocommited. Due to an error when accessing one of the resources participating in the transaction, the transaction fails and will be rolled back. This will lead into a state where the changes made in SAP R/3 remain persistent, whereas the other resource updates are discarded.

Documentation

The documentation for deploying IBM WebSphere Adapter for mySAP.com CSD 1 is provided in both a searchable Adobe Acrobat Portable Document Format (howto.pdf) and in HTML format (howto.htm).

Both are installed in the installation root directory by the WebSphere Adapter for mySAP.com installation package.

Installation

The installation program for WebSphere Adapter for mySAP.com CSD 1 on the various platforms is written in Java. It has been tested with Java Development Kit 1.3. Other versions of the Java Development Kit may work, but are not directly supported.

If there is a problem during installation, the file log.txt will be created in the installation root directory. Check the status messages in this file for more information.

Before deploying the WebSphere Adapter for mySAP.com in WebSphere, the J2C Runtime has to be installed.

Windows NT and Windows 2000 Specific

To install on Windows NT and Windows 2000, insert the CD-ROM. If autorun is enabled, the installation process will start. If it is not, run the setup.exe file in the 'win' subdirectory.

AIX Specific

To install on AIX, you must have root permission, and run the sapj2ee program in the 'aix' subdirectory.

The X-Windows client must be running for this installation program to work.

On some AIX systems the installation directory entry field in the installation program displays as white text on a white background! If this affects you, exit the installation program, use the style manager color utility to modify the system color pallette, and then start the installation program again.

Solaris Specific

To install on Solaris run the sapj2ee program in the 'solaris' subdirectory.

If the install window appears too small, resize it to be larger.

If you see an hour glass displayed instead of the normal mouse pointer on some of the installation panels, you can still use it to select buttons.

If you cannot scroll the text in the license agreement window using the mouse, click in the license agreement window, and use the cursor-up and cursor-down keys to scroll the text.

HP-UX Specific

To install on HP-UX copy the files of the 'hp-ux' subdirectory to the /tmp directory and run the install.sh shell script from there.
Please ensure, that the Java environment is set in your path.

At the end of the log.txt file there may be three messages: the first one indicating that checking the required disk space could not be performed, the second one indicating that the date and time could not be changed, and the third one indicating that the file permissions could not be changed. These messages can be ignored.

On some HP-UX systems you might see the console message:
Unable to resolve install: ServiceException: (error code = 305; message = "getS).
This message can be ignored.

With some X-Windows managers, font errors may occur, which can cause the installation to fail. Installing from a remote Intel-based system is normally successful.

With some CD-Rom device drivers the file names on the CD-Rom are displayed suffixed by a ';1'. To overcome this problem, you have to mount the CD-Rom with the following option: -o cdcase.

Linux Specific

To install on Linux run the sapj2ee program in the 'linux' subdirectory.

Creating deployable resource adapter archives

After successfully finishing the installation steps described above, there will be among other files two resource adapter archives (sapcsd.rar and sapcsd_notx.rar) on the hard disk. In order to make them deployable in WebSphere Application Server (WAS) and/or WebSphere Studio Application Developer - Integration Edition 4.1 (WSADIE 4.1) an additional step has to be performed. This step requires the resource adapter archive (sap.rar) coming with WebSphere Adapter for mySAP.com Version 1.0. On a command line / shell switch to the directory specified during the installation and invoke the following command:

java -cp sapcsd.jar com.ibm.sap.bapi.csd.CreateSapRar <WAS Adapter for mySap.com V1.0 sap.rar> sapcsd.rar <Filename of the target resource adapter, e.g. sap.rar>

Repeat the step for the sapcsd_notx.rar:

java -cp sapcsd.jar com.ibm.sap.bapi.csd.CreateSapRar <WAS Adapter for mySap.com V1.0 sap.rar> sapcsd_notx.rar <Filename of the target resource adapter, e.g. sap_notx.rar>

The resulting resource adapter archives can be deployed in WebSphere Application Server and/or Websphere Studio Application Developer Integration according to the description in the howto.htm and howto_wsadie.htm documents.

Hints and tips

General

If you encounter any problems running the SAPJ2EE program in your environment under AIX, Linux or Solaris, try running the install.sh file from the 'hp-ux' subdirectory to install the program in your environment.

Uninstallation

The uninstall program for Websphere Adapter for mySAP.com removes the previously installed files from the system.

Windows NT and Windows 2000 Specific

To uninstall the WebSphere Adapter for mySAP.com, on the Windows' task bar, select Start -> Programs -> IBM WebSphere Adapter -> Uninstall WebSphere Adapter for mySAP.com.

AIX Specific

To uninstall the WebSphere Adapter for mySAP.com, run uninst-sapj2ee from the installation root directory.

Solaris Specific

To uninstall the WebSphere Adapter for mySAP.com, run uninst-sapj2ee from the installation root directory.

HP-UX Specific

To uninstall the WebSphere Adapter for mySAP.com, run uninstall.sh from the installation root directory.
Ensure, that the uninstall.sh has the required attributes (Executable flag). If not, issue a chmod command to modify the attributes.

Linux Specific

To uninstall the WebSphere Adapter for mySAP.com, run uninst-sapj2ee from the installation root directory.

To remove the resource adapter from Websphere, start the WebSphere Application Server Administrator's Console, right-click on the SAP Resource Adapter, and select Remove.

Late-Breaking News

There is no late breaking news.

Trademarks

The following terms are trademarks of IBM Business Machines Corporation in the United States, other countries, or both:

IBM, VisualAge, AIX, RS/6000, WebSphere

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, Windows 2000, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

mySAP.com is a trademark of SAP AG.

Other company, product, and service names may be trademarks or service marks of others.

------------ End of readme ------------