Updating Seeburger Adapters with PI 7.3 Upgrade

If you are planning to upgrade your XI system to PI 7.3 and have Seeburger adapter installed, check if 2.1.5 or newer version of Seeburger adapter is being used. As this version is supported in the newer PI release, all you need to do is take a backup of the configurations and simply upgrade XI. If you are using older release, ensure that any of the following minimum release is installed:
1.6Q10
1.7Q3
1.8
Any of the newer seeburger release after 1.8

If you are not using 2.1.5 or newer release, follow these steps when upgrading XI:
1. Stop all Sender channels, wait for all the transactions to complete and stop rest of the channels relevant to interfaces using Seeburger adapter
2. Export Seeburger addressbooks, Digital Signature configuration, Mapping Variables, Message Monitor entries, Message Splitter configuration, Property Store data and Resource Managment configuration from Seeburger Workbench
3. Copy the exported data to a backup location
4. Trigger the PI upgrade process
5. Select "UNDEPLOY" for all Seeburger components during the JAVA PREPARE phase BUILD_COMPONENT_LIST
6. Undeploy all Seeburger components just before downtime
7. Let the PI upgrade complete
8. Copy the exported data back to the original location
9. Install new Seeburger adapters (atleast v 2.1.5)
10. Copy the exported files to import directories and import the data from Seeburger Workbench

If you are already using 2.1.5 or newer version, follow steps 1, 2, 3, 4, 7 and 8. No need to updeploy and deploy Seeburger adapters.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are creat...
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,...
Read more