Skip to main content
Skip table of contents

Migrating SAP Services to SAP NetWeaver Adapting the Bridge

Which SAP Package am I using?

You can find out which SAP package you are using on the Runtime tab of your Bridge node instance (see Managing the xUML Runtime of the Node Instance). This tab provides information on the installed Runtime components and libraries.

If you have updated your Bridge to version 6.0.52.0, it looks like:

If you have a Bridge below 6.0.52.0 installed and once had uploaded the SAPNW package, it looks like:

The package you uploaded last, is the SAP package that is active.

Attention! The SAP package that is active is not necessarily the package displayed last in the list.

If you do not remember anymore which package has been uploaded last, you can get the information which SAP package is actually used from the standard log (bridgeserver log, see xUML Service Standard Log) of an xUML service using SAP.
The new SAP adapter will write some information on the used library to the service log.

  • If using the old SAP package, you will see:
    No bridgeserver log entry.
  • If using the new SAPNW package, you will see:
    [Info][Internal][SAPADLM][40][Constructing SAP_AddOn using sapnwrfcsdk-7.20]

Uploading the SAP NetWeaver Firmware to the Bridge

If you want to use SAP Netweaver on your Bridge, use an E2E Bridge Installer as of version 6.0.52.0 or just upload the sapnw firmware package to your Bridge as described in xUML Runtime Upload. A package upload will overwrite an older sap package that possibly has been installed before.
If you want to go back to the old sap package, just upload the old package and the sap firmware gets exchanged. The sap firmware package that has been uploaded most recently is the one that takes effect.

Please note that some xUML services using interfaces to SAP may not work properly anymore after having updated to SAP NetWeaver. You will have to rework these services first (see Adapting the Services and Service Migration Checklist).

We recommend to

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.