Skip to Content

Post processing phase:   (Steps that need to be done after migration phase)

1. Patching:

  (a) Migration tool patches are delivered with SP 9 patches

  (b) Apply SP 11 directly

2. Development overview:

  Depending on development required by customer, several adoptions might be necessary

  (a) Since there is difference in the file system of EP 5.0 and NW’04, it might be necessary to change the hard coded file system paths

  (b) If migration is to be done on the UNIX platform, problems with case sensitivity will occur

  (c) Windows uses “” and UNIX uses “/” as a file separator, if problems occur, change the slashes.

  (d) HTTP 404 – File not found exception because of empty iViews and broken image links.

3.  Comparison between the directory structures of EP 5.0 and NW’04:

Directory structure of EP 5.0:


  Path to the folder:  irj root directory -> root

  Resources:  It contains publicly accessible (images, styles etc) used by components.

  Services:  It contains publicly accessible (images, styles etc) used by services.

  WEB-INF:  It is a private folder not publicly accessible.


  Path to the folder:  irj root directory -> root -> WEB-INF

  Deployment:  It contains deployed par/zar files.


  Path to the folder:  irj root directory -> root -> WEB-INF -> plugins -> portal

  Resources:  Private resources for components.

  Services:  Private resources for services.

  System -> data:  Default directory for PCD.

Directory structure of NW’04:


  Path to the folder:   usr/sap/Instance ID/JC00/j2ee/cluster/server0/apps/

  Portalapps:  Public accessible via http(s) used by portalapps

  WEB-INF:  Private folder not accessible publicly


  Path to the folder:   usr/sap/Instance ID/JC00/j2ee/cluster/server0/apps/

  portalapps:  Private resources for portalapps

4.  Portal Components Properties:

  In EP 5.0, each portal component has its own property file, but in NW’04, all the portal components use the same portalapp.xml file for properties. Migration will merge the properties files into single portalapp.xml file, but during this process, trailing white spaces are not removed.

  For this reason, runtime error will occur “failing to look up a system or database or anything else configured in portalapp.xml”.

  Solution:  Before migration process check the property files and remove white spaces. After migration process export the application, change the portalapp.xml file and redeploy the application.

5. Custom developments need to be redone in NW’04 system:

  (a) If EJBs were created and deployed in EP 5.0, redeploy them in NW’04

  (b) If additional JARs were copied to EP 5.0, they need be deployed to NW’04

6. Proxy Server Configuration:

  Note down the proxy details of EP 5.0 and reconfigure these settings in NW’04 in the following path.

  System -> System Configuration -> Applications -> -> Services -> proxy

7. Configuring Backend systems:

  (a) Set authorization method for working with backend systems by tickets

  (b) Re-establish trust between NW’04 and backend system

  (c) Specify gateway host and port for JCO iViews

8. Security:

  (a) If EP 5.0 is accessed via https then NW’04 has to be accessed via https

  (b) Assign group “Everyone” to the role “eu_role”

  (c) Admin role has changed, reassign admin role to admin users

  (d) Portal_user role is not migrated, content assigned to this role has to be reassigned

9.  Security Zones:

   In EP 5.0 every component is called via direct URL, but in NW’04 we have security zones for additional security. The security zone will be added to every imported component.

10.   Portal Themes:

  Style archives have to be processed manually.

  First download the portal style archives from EP 5.0

  System Configuration -> Styles -> Related Tools -> Style Archive


  Upload the archive file in NW’04 System Administration -> Portal Display -> Theme Archive.


  Later add your theme to a portal desktop and edit the main rule.

This completes the migration of portal platform of EP 5.0 to NW’04. Hope the migration process is clear. Please do get back to me if you have any queries or suggestions.

My next weblog in the migration of Portal series will explain you the KM Migration.

To report this post you need to login first.

1 Comment

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

  1. Karthick Eswaran
    Very good weblog.Thank you for clearing almost everything about the migration process.
    I have one doubt,Could you please clear me that as well.
    In EP5.0 I was using “pcdservice” and “pcdmanager”
    portal services to get the paths.
    getPortalComponentArchivePath(): e.g.: /system/irj/par/
    getGlobalPagePath() :e.g.: /global/pages/
    getServiceCataloguePath() e.g. : /global/services/installed/
    getJavaIviewPath() :e.g. : /global/services/java-iviews/
    getLocalServiceIviewPath() : e.g. : /global/services/service-iviews/local/
    getLogicalServicePath() : e.g. /global/services/logical/
    getServicePath() : e.g : /global/services/
    getPcdRootPath(IPortalComponentRequest request):
    e.g. : getPCDSession(request).getTransportEngine().getExportDirectory() + “../Pcd”

    I could not find the paths in EP6.0.Could you please tell me the exact paths in EP6.0 and what are all the methods available in EP6.0.



Leave a Reply