Version 2.3.1.18	SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT

These Release Notes contain last-minute installation and configuration hints. Please read the Readme for more technical information.

• Stopping RPC Server

• About Hyperlinks

• Deinstallation

• What's new in 2.2.1

• Migrate to 2.2.1

• What's New in 2.2.1.01 - 05

• What's New in 2.3.1

• Xalan and Ant

• Migrate to 2.3.1

• Ping Wizard supports IDoc XML Gateway Adapter

• Migrate EntireX Communicator

• Datatype I4

• Platform Encoding

• Microsoft C Compiler

• What's New in 2.3.1.02 - 03

• What's New in 2.3.1.04

• What's New in 2.3.1.05

• What's New in 2.3.1.06

• What's New in 2.3.1.07

• What's New in 2.3.1.08

• EntireX Communicator 7.3 on AIX 5.3

• What's New in 2.3.1.09

• What's New in 2.3.1.10

• What's New in 2.3.1.11

• What's New in 2.3.1.12

• What's New in 2.3.1.13

• What's New in 2.3.1.14

• What's New in 2.3.1.15

• What's New in 2.3.1.16

• What's New in 2.3.1.17

• What's New in 2.3.1.18

Stopping RPC Server

A new function has been implemented for the Rpc2Rfc kernel to deregister this process on webMethods EntireX Broker. Deregistration runs when this process receives a signal SIGTERM. To activate the signal handler, you must set the environment variable EXX_SERVER_ADDRESS.

The signal handler is implemented in the shared library. The server loads this library at the first RPC call and the signal handler becomes active.

Currently this feature has only been tested on Sun Solaris.

To deactivate the new source code, you can set the define statement -D EXX_GATEWAY_NO_SHUTDOWN in makefile.

About Hyperlinks

In some cases, the documentation points to the SAP R/3 Gateway web application in this format: http://YourGateway:8080/sapr3gateway/manager/index. Copy this URL, paste it into your browser's address line and change the host name YourGateway to yours.

Deinstallation

To remove the installed SAP R/3 Gateway web application, use the Manager of the Application Web Server. With the Remove link, the Tomcat Manager (or http://YourGateway:8080/manager/html/list) will remove the complete installation from the file system immediately without requiring confirmation. (Please check this if you have a version of Tomcat older than 4.1.29.)

What's new in 2.2.1

• Documentation

• New Configuration

• COBOL Client Generation

• Easy Navigation

• New Upload Feature

Documentation

Several sections have been added to the SAP R/3 Gateway documentation:

• About Hyperlinks

• Deinstallation

• Worker

• Optimization Tools

• Configuration of System Manager

New Configuration

Some parameters were fixed in makefiles. Now with version 2.2.1, these parameters are defined in the System Manager. This has the following advantages.

• There is one central configuration base.

• There are fewer configuration steps in makefile.

• There is a GUI component.

The following new parameters are transferred by an environment variable from System Manager to the Makefile when the Compile and Link job is started.

• The directory of RfcSdk installation

• The directory of webMethods EntireX installation in Windows platform

• The IDL filename

• The library name used in the IDL

• The asynchronous library name used in the asynchronous IDL

• The executable program name of Rfc2Rpc kernel

If you have an older version, please read the migration steps in the section Migrate to 2.2.1 to use this feature.

COBOL Client Generation

This version contains new features for COBOL client generation. The COBOL client acts as an RPC client for the Rpc2Rfc kernel and with a local sub-program calling convention to call an ABAP business function. When generating the COBOL client stub, it is possible to generate a ready-to-start program. See the section Generate Stub for COBOL Client for more information about installation and configuration.

Easy Navigation

The webapps/sapr3gateway directory contains an index.html file. This file redirects you to the index main menu of the web application. It is now possible to go directly to the web application with URL http://YourGateway/sapr3gateway or from the Tomcat Manager web application list.

However, with this feature, the Browse File System tool will not work. If you want to continue to use the Browse File System tool, delete or rename the file index.html.

New Upload Feature

The new upload and setup feature allows you to transport single files or ZIP files from your desktop to the SAP R/3 Gateway web application. This feature will be used by Software AG's support center to install updates or patches.

For additional information refer to the sections Migrate to 2.2.1 and Upload and Setup.

Migrate to 2.2.1

This section describes how to update from version 2.1.1 to version 2.2.1. If you have a 2.1.1 installation and you have made any changes, it is possible to migrate and to save your configuration.

To migrate from version 2.1.1 to version 2.2.1

1. Back up the current web application (refer to the section Backup). The backup tool starts a shell script to collect all the files in the directory and subdirectories webapps/sapr3gateway.

2. Copy the update archive 2.2.1 to webapps/sapr3gateway.

3. Decide whether you want to update the makefiles (see the section New Configuration under What's New in 2.2.1). The next 2 steps are optional. In both cases, the update medium does not contain any IDL file.

4. If you wish to update the makefiles, extract the whole update archive with the following command in directory webapps/sapr3gateway:

   jar -xvf sapr3gatewayUpdate221RC7.zip

5. If you do not wish to update the makefiles, extract the update archive with multiple commands. The following list includes each file or directory and excludes the makefiles.

   jar -xvf sapr3gatewayUpdate221RC7.zip ShellScriptSrv.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip AttachManager.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip brokerHWM.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip deployRpc2RfcToDev.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip deployRpc2RfcToInt.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip deployRpc2RfcToProd.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip dev.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip devAdmin.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip devPMQClient.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip docu.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip frameAdmin.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip GASServer
   jar -xvf sapr3gatewayUpdate221RC7.zip index.html
   jar -xvf sapr3gatewayUpdate221RC7.zip jobs.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip parameter.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip resourceAdmin.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip rpcPing.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip SystemConstancy.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip scheduler.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip setupWizard.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip update.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip version.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip configSetup.xsl
   jar -xvf sapr3gatewayUpdate221RC7.zip Rfc2Rpc/dev/revision.xml
   jar -xvf sapr3gatewayUpdate221RC7.zip Rfc2Rpc/dev/rfcsrv.tpl
   jar -xvf sapr3gatewayUpdate221RC7.zip Rfc2Rpc/dev/rfcstd.c
   jar -xvf sapr3gatewayUpdate221RC7.zip Rpc2Rfc/dev/rfctab.c
   jar -xvf sapr3gatewayUpdate221RC7.zip Rfc2Rpc/dev/cobol.mak
   jar -xvf sapr3gatewayUpdate221RC7.zip Rfc2Rpc/dev/cob_ftp.tpl
   jar -xvf sapr3gatewayUpdate221RC7.zip Rpc2Rfc/dev/CobolServer.tpl
   jar -xvf sapr3gatewayUpdate221RC7.zip META-INF
   jar -xvf sapr3gatewayUpdate221RC7.zip WEB-INF/lib
   jar -xvf sapr3gatewayUpdate221RC7.zip Natural
   jar -xvf sapr3gatewayUpdate221RC7.zip PMQServer
   jar -xvf sapr3gatewayUpdate221RC7.zip PerformanceMeasuring
   jar -xvf sapr3gatewayUpdate221RC7.zip Ping
   jar -xvf sapr3gatewayUpdate221RC7.zip setup
   jar -xvf sapr3gatewayUpdate221RC7.zip docu
   

6. After extraction it is necessary to restart the System Manager. Do this with the Tomcat manager http://YourGateway:8080/manager/html/list) Stop and Start buttons for the web application SAP R/3 Gateway.

7. Some of the parameters in the previous version of the makefiles are placed in the configuration of System Manager. Therefore, the parameter IDL Library must be added to the Development Configuration.

   • In the Rpc2Rfc (SAP Server) dialog under Development on the Configuration menu (or http://YourGateway:8080/sapr3gateway/manager/devAdmin?cfg=1)

     • set the value for IDL Library to R3RFC.

   • In the Rfc2Rpc (SAP Calls External Server) dialog under Development on the Configuration menu (or http://YourGateway:8080/sapr3gateway/manager/devAdmin?cfg=2)

     • set IDL Libarary to RFCRPC

     • set IDL Asynchronous Library to PMQ

     • set Make Result to rfcrpc.exe on Windows or rfcrpc on UNIX

8. Check the last step and recompile all kernels on the Development option.

9. To install the new upload feature, the sapr3gateway/WEB-INF/web.xml (http://YourGateway:8080/sapr3gateway/manager/dir?readfile=$SM_HOME/WEB-INF/web.xml&EditFileDescription=web.xml&edit=) file must be changed as follows.

   1. Add this servlet XML node:

          <servlet>
              <servlet-name>setup</servlet-name>
              <servlet-class>FilterServlet</servlet-class>
              <init-param>
                  <param-name>config</param-name>
                  <param-value>/configSetup.xml</param-value>
              </init-param>
          </servlet>
      

   2. Add this servlet-mapping XML node:

          <servlet-mapping>
            <servlet-name>setup</servlet-name>
            <url-pattern>/setup/*</url-pattern>
          </servlet-mapping>
      

   3. Restart the SAP R/3 Gateway web application.

What's New in 2.2.1.01 - 05

Up to release 2.2.1 some updates are in Software AG's global extranet Empower. The following files have been changed and updated.

What's New in 2.3.1

• IDoc XML Gateway Documentation

• Upload with Backup

• Rfc2Rpc Table Support

• Interface Development

• Tomcat 4.1.31

IDoc XML Gateway Documentation

The IDoc XML Gateway documentation contains all configuration, concepts and implementation steps (see the section IDoc XML Gateway). In addition, the business concepts of using the SAP R/3 Gateway in various environments are explained in the separate section Integration Scenarios.

Upload with Backup

An optional backup of existing files has been added to the upload feature (see the section Upload and Setup). Before an existing file is overwritten, it is saved in a ZIP container.

Rfc2Rpc Table Support

The handling of tables has been changed in the Rfc2Rpc kernel if the number of records is greater than defined in the IDL (see the section Support of Tables).

Interface Development

Examples have been added to the documentation for IDL and interface development for Rpc2Rfc (in Calling Scenarios) and Rfc2Rpc (in Develop IDL).

Tomcat 4.1.31

The CD contains the new Tomcat version 4.1.31 to suppress the Xalan and Ant problem.

Xalan and Ant

Tomcat 4.1.30 delivers a newer Ant version than Xalan 2.4 requires. If the following symptom appears on your installation, follow the instructions under "resolution".

Symptom:

The menu Version Info or the HTTP command http://YourGateway:8080/sapr3gateway/manager/xalan Version throws an exception with the message: java.lang.NoClassDefFoundError: org/apache/tools/ant/launch/AntMain.

Resolution:

Download Ant 1.5.4 from archive http://archive.apache.org/dist/ant/binaries and install ant.jar in $TOMCAT_HOME/common/lib or delete ant.jar in $TOMCAT_HOME/common/lib. (This option should only be selected if Ant is not used by any other web applications. Ant is not used by the SAP R/3 Gateway.) The change will take effect after Tomcat has been restarted.

Migrate to 2.3.1

It is possible to migrate from version 2.2.1 of Software AG's SAP R/3 Gateway to version 2.3.1. The CD contains a ZIP file sapr3gatewayUpdate23100.zip which has all of the changes between these two versions. The patches and hotfixes 01-05 are also included. The following files are not on the update medium:

• IDL files

• System Manager configuration file config.xml

• WEB-INF/web.xml

To migrate from version 2.2.1 to version 2.3.1

1. Backup the current installation (with the backup tool, for example; see Backup).

2. Upload the ZIP file sapr3gatewayUpdate23100.zip with the Upload and Setup tool.

3. Restart the web application sapr3gateway.

4. Migration to 2.3.1 is now complete. Continue with installation of the optional component IDoc XML Gateway (see the section Installation).

Tip:
It is possible to install the new SAP R/3 Gateway alongside the previous one in the web application server. To do this, rename the WAR file (e.g. add a version number to sapr3gateway) before completing the deployment process.

Ping Wizard supports IDoc XML Gateway Adapter

The Ping Wizard has switched to the new IDoc XML Gateway Adapter. Therefore, the old web applicaton exxr3xmlgateway.war is no longer delivered. The stylesheet ping supports the old adapter. You do not need to make any changes to the timer task command (see the section Scheduler). Call the Ping Wizard stylesheet to make any changes to the new adapter, after which you can remove the old one.

Migrate EntireX Communicator

If you upgrade your EntireX Communicator installation on UNIX from v6 to v7 or v71 to v72, the UNIX setup will place the software in its own version directory and create a new sagenv script.

To change only the runtime for the running kernel tasks (Rpc2Rfc and Rfc2Rpc), you can set the version directory of EntireX (EXX_VERS) on the System Constants page. After this has been set, you must restart the kernels.

Tip:
After restarting the kernels, this Rpc2Rfc kernel version writes to the System Log. Alternatively, set the environment variable ETB_STUBLOG=1 (Rpc2Rpc and Rfc2Rpc) and check the created file for version information. This file is created in the same directory as the running task with the process ID and extension etb. This step makes sure that the new EntireX runtime will be used. Do not forget to undo this trace setting afterwards.

To recompile the kernels

1. Change the EntireX version directory EXX_VERS on the System Constants page.

2. Set the new sagenv script SAG_ENV_SCRIPT on the System Constants page.

3. Delete all old generated source code on the Jobs page by executing Rpc2Rfc clean up Dev files and Rfc2Rpc clean up Dev files.

4. Go to the Developer page and execute Compile and Link for Rpc2Rfc and Rfc2Rpc.

5. Go to the Running Task page and stop all tasks in the development environment.

6. Go to the Deployment page and copy all new generated kernels into the run directory.

7. Start the kernels.

Datatype I4

On 64 bit platforms, a problem can occur with data type I4 in the Rfc2Rpc kernel.

Symptom:

The ABAP clients receive the exception EXX00010083. (The System Log also displays the message ERX Call stub: Parameter out of value space. Location of wrong Parameter...).

Resolution:

We recommend replacing the data type I4 by data type P. Please contact Software AG support if you cannot use this solution.

Platform Encoding

The XML-RPC servlet, a component of IDoc XML Gateway (IDoc type generation), needs the platform character encoding (default character encoding) setting of JVM.

Symptom:

During IDoc type generation in IDoc XML Gateway, the System Log displays the error message Broker Error 0022 0437: Some chars unconvertible to target CP.

Analyze:

To see and trace the character encoding used, set and activate the following JVM properties.

entirex.sdk.default.trace.level=STANDARD
entirex.sdk.default.trace.filename=STDOUT

1. After activating the JVM properties, restart the sapr3idocxmlgateway web application

2. Generate the IDoc type.

3. In Tomcat, the trace is written to $TOMCAT_HOME/logs/catalina.out.

4. Analyze the log for encoding print outs.

Resolution:

Set the JVM property:

file.encoding=To_Your_Need__Platform_Encoding

After the property has been activated, restart the sapr3idocxmlgateway web application.

Microsoft C Compiler

Symptom:

When compiling the Rpc2Rfc server or the RfcIdl tool, the Microsoft Windows C-Compiler aborts with error message fatal error C1902: Program database manager mismatch; please check your installation.

There is a compiler option /FD to generate .pdb files for debugging information.

Resolution:

Delete the /FD compiler option in the makefiles Rpc2Rfc/dev/MakefileNT and RfcIdl/MakefileNT.

What's New in 2.3.1.02 - 03

This documentation has a new pipeline view section. In detail, the following files have been updated.

What's New in 2.3.1.04

This update also contains the files of the previous fix. In detail, the following files have been updated.

What's New in 2.3.1.05

This documentation has a new Clone Environment Wizard section. The Clone Environment Wizard makes it possible to create an environment in which multiple IDLs of Rpc2Rfc or Rfc2Rpc kernels can be run in parallel. This update also contains the files of the previous fix. In detail, the following files have been updated.

What's New in 2.3.1.06

The software requirements are changed for EntireX 7.2.1. Patch 68 is required.

This update also contains the files of the previous fix. In detail, the following files have been updated.

What's New in 2.3.1.07

This update also contains the files of the previous fix. In detail, the following files have been updated.

What's New in 2.3.1.08

This update also contains the files of the previous fix. In detail, the following files have been updated. The main changes of this update are to support EntireX 7.3 Developer's Kit. The Setup Wizard contains addional steps for configuration.

EntireX Communicator 7.3 on AIX 5.3

Symptom:

When linking the Rpc2Rfc, Rfc2Rpc server or the RfcIdl tool, the linker aborts with the following error message:

ld: 0711-317 ERROR: Undefined symbol: .iconv_open
ld: 0711-317 ERROR: Undefined symbol: .iconv_close
ld: 0711-317 ERROR: Undefined symbol: .iconv

The character encoding conversion library is missing.

Resolution:

Add the parameter -liconv to the linker option in the makefiles. To change the makefiles, go to guimenu and Development, and select Makefile to start the editor.

What's New in 2.3.1.09

This update also contains the files of the previous fix. In detail, the following files have been updated.

What's New in 2.3.1.10

This update also contains the files of the previous fix. In detail, the following files have been updated:

What's New in 2.3.1.11

This update also contains the files of the previous fix. In detail, the following files have been updated:

What's New in 2.3.1.12

This update also contains the files of the previous fix and supports new SuSE Linux Enterprise Server 11 platform. In detail, the following files have been updated:

What's New in 2.3.1.13

This update also contains the files of the previous fix and supports the new Windows Server X 64 Bit platform in conjunction with webMethods EntireX 8.2. In detail, the following files have been updated:

Upload the full content of sapr3gatewayUpdate23113.zip only on new SAP R/3 Gateway. On existing and running nodes, upload the partial ZIP files (e.g. build/ManagerUpdate23113.zip) to save your local changes in configuration files (e.g. Makefiles).

What's New in 2.3.1.14

This update is only a new build of 13 and contains the changes since 05. Please read What's New in 2.3.1.13 for relevant changes.

What's New in 2.3.1.15

This update contains all changes from version 2.3.1.05 to version 2.3.1.13 and fixes the following files.

To support EntireX 8.2.2, this update contains new Unix Makefiles. When the new EntireX runtime is used, the linking step in all Makefiles must be executed because library libss.so has been removed.

What's New in 2.3.1.16

This update contains all changes from version 2.3.1.05 to version 2.3.1.15 and fixes the files in the following table.

This update version has been tested with EntireX 9.5 SP1.

What's New in 2.3.1.17

This update contains all changes from version 2.3.1.05 to version 2.3.1.16 and fixes the files in the following table.

What's New in 2.3.1.18

This update contains all changes from version 2.3.1.05 to version 2.3.1.17 and fixes the files in the following table.

www.softwareag.com

Copyright © 2004-2015 Software AG, Darmstadt, Germany.

SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT