Skip to Content
Is quite typical that a NetWeaver Portal becomes easily from an “SAP systems entry point” to a “business critical system”; the reason for this evolution is that several users (executives, sales, stakeholders, partners, technicians, customers, etc.) start using this Portal for the daily work. On the Portal they can find all tools and information to perform their work easier and faster, but we have to take into account that all this is based on iViews, Business Packages and connection to backends systems (SAP and non-SAP systems).

Keep the service level provided from this Portal to end-users at highest possible level is a new challenge for IT organizations, on this blog i’d like to provide some recommendations for this purpose.

The recommendations are divided in two areas:

Essential tools: here you will find the minimal tools required to maintain your Portal running minimizing any downtime situation.

To be consider: this area contains other recommendations that you should be considered if they apply to your business. In the case your portal becomes a “business critical portal” they are strongly recommended.


Essential tools :


– SM Diagnostics:

A key requirement for an efficient and a safer support of IT solutions is the ability to perform root cause analysis with speed and efficiency. Solution Manager Diagnostics provides all functionality to centrally analyze a complete SAP NetWeaver system landscape. It also reduces the time needed to train a support consultant in root cause analysis for SAP NetWeaver. It is mandatory to install one Solution Manager Diagnostics within your SAP NetWeaver solution landscape if you run applications based on SAP Web AS JAVA. Active Global Support performs root cause analysis on incoming incidents on Solution Manager Diagnostics.

More information can be found at following links:

– NW Support Platform (application):

The SAP NetWeaver Support Platform is an open platform to develop and run small utilities (known as plug-ins) that perform support oriented activities on any and all components of NetWeaver. Is included by default as of WebAS 6.40 SPS16, but if your Portal is on a previous version you can deploy it as indicated on SAP Note 812688

Detailed information about this great tool can be found at:

– Portal Content Director (PCD) Inspector tool:

With the PCD Inspector tool, you can perform a deep analysis of objects stored in the PCD, it is useful in case of problems and give you an exact “as is” information about any object on PCD

Detailed information on following links:

The PCD Inspector can be downloaded from here

– UME Consistency Check:

The last but not the least is the UME Consistency Check tool, this tool helps you to remove logical inconsistencies in the UME database, the installation procedure and some extra information about “how to use” is mentioned on SAP Note 818947.

The tool is delivered as a Portal application (PAR) file, to get it please open a customer message under component BC-JAS-SEC-UME, asking for it.


To be considered :


– Develop your own Plug-inn over the NW Support Platform

If your business demand some extra check that aren’t included as standard on the SAP NetWeaver Support Platform you can develop your own plug-inn, this is explained on the document and links mentioned before.

– High Availability:

If the services provided by the Portal to end-users require 24×7 availability, should be great if high availability solution supports the Portal, there exist some restrictions that must be consider and evaluated, just refer to following links for further information:

– SAP Premium Support for your NW Portal

Well, i don’t want to use this blog as “marketing” but SAP has released a new support level named Premium Support, if your NW Portal is a business critical system, this support level will be a great help.

Have a look on SAP Service Marketplace for further details

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Dagfinn Parnas
    Like you are saying, alot of portals are going from information portal to a desktop for the user with lot of critical applications.

    It is natural to want to isolate these critical applications from each other, both in different processes but also different servers. However, the overhead of having too many EP systems can be significant if you start having a separate EP system per critical application. If you have one portal, and even if it is a complete HA solution, you can still crash it easily by implementing a portal component which runs in an inifinite loop. One by one the servers will be “hung” and reduce your servers to noisy coffe tables with built in heat.

    What I would like is:
    1. Portal applications(packages of portal components) are “transformed”  into J2EE applications (but with high dependency to irj). This might not be needed if business packages are converted to for example web dynpro.
    2. The possibility of running a J2EE application in a separate process (this is possible in other J2EE application servers, like Websphere)
    3. An easy way of defining a subset of servers an application is running on, and  making this transparent from the portal perspective. Web dispatcher might be an option, but as far as I’ve heard it doesn’t scale up to very large portals.

    Also see thread /thread/124780 [original link is broken] for some more ideas

    Cheers
    Dagfinn

    (0) 

Leave a Reply