Friday, January 30, 2009

How to check SSL setting of your ABAP Stack?

You might need to use Secure Sockets Layer (SSL) protocol to access your web application running in SAP. You have followed all configuration steps to implement it and you wondering how to test it. SAP delivers test BSP application to check HTTPS configuration. You can use it like following: TA SE80 -> choose “BSP application” search for “system_test” -> navigate to page with flow logic called “test_sso2.htm” and run (test) it via right mouse click.

URL: Hostname:port/sap/bc/bsp/sap/system_test/test_sso2.htm

How to find out version of IGS

There is a very useful ABAP report called GRAPHICS_IGS_ADMIN associated with TA SIGS which you can use for almost whole administration of your IGS (Internet Graphic server) from ABAP Stack of your SAP landscape. Basically IGS is server engine for rendering of graphics content out of SAP systems (e.g. in case of BW it produces maps/charts for BEx reports). It does use RFC or HTTP for accessing it. As of version 7.0 IGS is integrated into WAS (but also available as standalone) but still is running outside of SAP kernel.
At selection screen of TA SIGS you specify RFC destination which IGS uses:

Right after you run it you get version of ISG:


Monday, January 19, 2009

How to find details about NW 7.0’s SPS ?

Sometimes it is very hard to navigate on Service Market place in order to find out what are components included in any particular Support Package Stack (SPS) of NetWeaver. For that purpose I’m providing following link:

Here you choose SPS no that you are interesting in and hit “Show Stack Information” button. You can find here product versions, SP levels, package no, Release- & Information Note (RIN), etc of all NetWeaver components like:

  • Application Server ABAP
  • Application Server Java
  • Adobe Document Services
  • Business Intelligence
  • Enterprise Portal
  • EP Core
  • EP Content
  • Content Server
  • Mobile Infrastructure (MI)
  • MI Client
  • Development Infrastructure
  • Developer Workplace
  • Developer Studio
  • Search and Classif. (TREX)
  • Process Integration (PI/XI)
  • J2EE Adapter Engine (PI/XI)
  • J2SE Adapter Engine (PI/XI)
  • Partner Connect. Kit (PI/XI)
  • Content PI/XI
  • Frontend

Sunday, January 18, 2009

Further checking of broken DSO objects

You might experience following error while loading data to DSO:

System error in program SAPLRS_EXCEPTION and form RS_EXCEPTION_TO_MESSAGE (see long text) Message no. BRAIN299
Unknown error in SQL interface Message no. DBMAN259
Error while extracting from source DSOXXX (type DataStore) Message no. RSBK242
Package 2 / 16.01.2009 15:28:21 / Status 'Processed with Errors' Message no. RSBK257

This is purely linked with technical problem with your ODS object. Solution is to recreate DDIC objects behind you DSO. Normal option would be to delete DSO object and create it again from scratch. Since usually there is no so much time to proceed like this you may try to fix it like following:

1. TA RSRV (Analyses and Repair of BI Objects) -> All Elementary Tests -> ODS Objects -> Foreign Key Relationship of Reporting-Relevant ODS Object and SID Table Characteristics -> put your DSO here -> Execute

Then you get message like:
Error: Too many specifications missing for InfoObject IOXXX         Message no. RSRV503
SID values missing for 2.097 specifications of characteristic IOXXX Message no. RSRV501

Moreover system generates for you an ABAP report called: GP_ERR_RSODSO_ACTIVATE. You can browse this report in TA SE38 and via ABAP syntax Check functionality you easily explore which DDIC object is broken.

2. To fix this broken DDCI object use the report RSDG_ODSO_ACTIVATE which activates the DataStore object. Run it in Activate mode. Note that this result in the creation of a new change log table and that existing data from the inconsistent change log table may be lost.
You may be able to determine from executing the report in check mode whether further inconsistent DataStore objects exist.