SAP Security Online!
 
Web SAPSecurityOnline.com
 
   
 
 
 
 

 
  Enterprise Portal- Installation Guide

Installing SAP Enterprise Portal on Win2K/Oracle.

 

Installing Oracle 9.2 for SAP Enterprise Portal 6

Prerequisite for Unix
Set the display  DISPLAY <your IP>:0.0
If you are using cshell $ setenv DISPLAY <your_ip>:0.0

OSS Note : 668312

  • /oracle for oracle directory
  • SAPinst requires JDK (Java 2 SDK, Standard Edition)
  • Installation directory /temp/sapinst
  • change the kernel parameters in /etc/system as in the OS Dependencies guide.

Installing Portal Platform, Content Management

  • Oracle Drivers
    • An Oracle JDBC driver (needed if you install DB on a different server)
    • A language support driver
  • SAP JAVA Cryptographic Toolkit
  • System Analyzer, a part of the Enterprise Portal Installation

J2EE engine installation directory : /usr/sap/<SYSTEM_NAME>/

Now we are starting the installation :

Installing Oracle 9.2 for SAP Enterprise Portal 6.0

Pre-requisite :

  1. Oracle Directory /oracle
  2. Java Development Kit (Java 2 SDK)
    • If you are using Solaris 9. Remove previously installed JDK 1.4.1 using "pkgrm SUNWj3dmo SUNj3man SUNWj3dmo”
    • Install JDK 1.3.1.10 using “/sapcd/jdk/j2sdk-1_3_1_10-solaris-sparc.sh” under “/opt”
    • Setup JAVA_HOME to “/usr/java
    • check the JRE ext directory
  1. Install Oracle 9i
    • Create a temp directory “/temp/install”
    • Run SAPinst in “/temp/install” “/sapcd/epsp2/SAPINST/UNIX/SUNOS_64/sapinst”
    • When the SAPINST Gui comes up, choose “I agree”
    • Choose “New Installation” in the “Install or Upgrade”
    • Select “Database Server” for “Choose an installation option”
    • In the next screen, “New” Oracle Instance with “<YOURSID>” as SID
    • for SAP DBA tools, “/usr/sap/dbatools”
    • For Portal Platform Schema ID, choose “PCD” (taking default value for Development), for Content Management Schema ID, choose “WCM” (taking default value for Development)
      • Password : PCD / password
      • Password : WCM / password
    • Provide the location of Database CD’s
      • CD RDBMS Oracle 1 : /sapcd/oracd1
      • CD RDBMS Oracle 2 : /sapcd/oracd2
      • CD RDBMS Oracle 3 : /sapcd/oracd3
    • Database Administrator : ora<sid> / password
    • Database User SYS : SYS/ password
    • Database User SYSTEM : SYSTEM / password
    • Database Instance RAM : 1024
    • Listener Port : 1527 (Default Value)
    • Shows up the filesystem : It is the same as WAS except for sapdata upto 7
    • Install Oracle 9.2
    • Patch Oracle 9.2 runInstaller (to extract cpio file use : “cpio –idmv < 9204_solaris64_release.cpio” (“products.jar” will show upgrade the runInstaller)
    • Continue with the Oracle Patch Installation
    • Continue with the Database Installation in the SAPINST GUI (post-processing and etc)

Continuing with the Portal Platform Installation

  1. Download and install “SAP JAVA Cryptographic Toolkit” extract the downloaded SAP Java Cryptographic Toolkit to a temporary directory, and specify this directory during the installation
  2. Verify the installation readiness with the System Analyzer
    • Run System Analyzer by executing “prerequisite” under the <Enterprise Portal Installation CD>/ANALYZER
    3. (According to OSS note 668312, download the attached “prerequiste.zip” and use it)
  1. Create a new installation directory “/temp/ep_install” and chmod to 777
    • Execute “/sapcd/epsp2/SAPINST/UNIX/SUNOS_64/sapinst”
    • In the SAPINST GUI, select “New Installation” for Install or Upgrade?

“Portal Platform, Content Management & Collaboration” for Choose an installation type.
System Name : “<YOURSID>_PORTAL” , Instance Number “00”,
1024 Mb for the maximum heap size for JVM

  • Group Information for SAPSYS group for user “j2eeadm” j2ee stand alone user : GroupID : 102
  • User Information for “j2eeadm” user : UserID : 1025 with home directory : /home/j2eeadm, password “password”
  • Directory for cryptographic libraries “/sapcd/sar/cryp”
  • Oracle Database Connection Information for Portal
    • Oracle hostname           “<fully qualified hostname>”
    • Oracle instance name    “<YOURSID>”
    • Oracle listener port       “1527”
    • Schema id                    “PCD”
    • database User password  “password”
  • Certificate screen,
    • Portal System ID : <YOURSID>
    • Sub Organization Unit : <Your company name>
    • Organizational Unit : EnterprisePortal
  • Check Install Application Sharing Screen,
    • Check “Install Application Sharing server now, on the portal machine”,
      since we are installing CM on the same portal machine
  • Connection Information for Oracle Database Connection Information for CM
    • Oracle hostname           ““<fully qualified hostname>””
    • Oracle instance name    “<YOURSID>”
    • Oracle listener port       “1527”
    • Schema id                    “WCM” : see above!
    • database User password  “password”
  • Ignore TREX
  • Verify the installation parameters and Start the installation

Message : when you complete the post installation procedure, access the portal using the following URL : http://yourhostname:50000/irj/.

Tricks :
Login to dispatcher console
execute :/usr/sap/<YOURSID>_Portal/j2ee/j2ee_00/admin/go and use “j2eeadm/<password>” & change the port number to 50008

Upgrading the Sap J2EE engine 6.20 (OSS_Note : 616501)

Package is located at /sapcd/jeepat

  1. Take the SAP J2EE engine down and Oracle Database on
  2. execute /sapcd/jeepat/visual.sh
  3. choose existing J2EE engine Folder as “/usr/sap/<YOURSID>_Portal/j2ee/j2ee_00”
  4. choose “Upgrade” for installation method

Trick :
Use “root” to start the SAP J2EE engine.
In order to start, execute “/usr/sap/<YOURSID>_Portal/j2ee/j2ee_00/cluster/dispatcher/go”
There are some permission problems with the “j2eeadm” user

To access the SAP J2EE Administrator, use port 50004 for “No layer” Type.
Use the “Administrator” with blank password for this!

Running Patch 2 for Portal Platform 6.0 SP2

  • Ensure SAP J2EE engine is running
  • Start and Logon to “J2EE Engine Administrator”
    • Select the “Server”node -> services -> deploy. In the deployed components window, expand the server node
    • Click the “servlet_jsp” node.
    • Select “irj” and press the “Stop Application” button.
    • Keep the SAP J2EE Engine Administrator window open.
  • Open the SAP Software Delivery Manager
    • go to /usr/sap/<YOURSID>_Portal/java/sdm/program
    • execute ./startSDM.sh
    • In the SDM Deployment tab, click the plus sign(+) icon, browse to the Patch 2 CD (/sapcd/eppat/UME/ume.swc), and navigate to the UME directory. Select UME.swc.
    • In the SDM Deployment tab, click the plus sign(+) icon, browse to the Patch 2 CD (/sapcd/eppat/Portal/catalog1.swc), and navigate to the Portal -> Catalog directory. Select catalog1.swc.
    • In the SDM Deployment tab, click the plus sign(+) icon, browse to the Patch 2 CD (/sapcd/eppat/Portal/catalog2.swc), and navigate to the Portal -> Catalog directory. Select catalog2.swc.
    • In the SDM Deployment tab, click the plus sign(+) icon, browse to the Patch 2 CD (/sapcd/eppat/Metamatrix/catalog3.swc), and navigate to the Metamatrix directory. Select catalog3.swc.
    • Choose Next
    • In the lower central part of the screen, use “Use existing deployment parameter values”.
    • continue Next until you reach the screen with “Start” button
    • Choose “Start” to deploy the Software Catalogs (*.swc) files
    • When deployment is finished, choose “Confirm”
    • Quit the SDM and restart the SAP J2EE Engine.
  • Running Patch 2 for Content Management Prerequisites
    • SAP J2EE Engine is running.
    • You read SAP note 682652, for CM Patch 2 installation.
    • You have installed Content Management (CM) according to the instructions in Installing Portal Platform, Content Management and Collaboration for SAP Enterprise Portal 6.0 SP2, located on SAP Service Marketplace at service.sap.com/ep60 → Documentation & More → Installation.
  • The installation of Patch 1 for CM is not a requirement. If you have not applied it yet, proceed with Patch 2 installation.
    Procedure
    The following steps describe the procedure for running Patch 2 for SP2 for both UNIX and Windows platforms. Instructions that are specific to one or the other operating system are indicated as such.
    To prepare for running Patch 2 for CM:
  • Download the patch from service.sap.com and unzip to /sapcd/eppat.
  • Log in with account j2eeadm. Make sure that the user has access to the SDA files that you need to deploy for running the patch.
  • Make sure that the $DISPLAY, JAVA_HOME and PATH system variables are set correctly.

To apply the CM patch:

  • Ensure that the SAP J2EE Engine with the initial portal is running.
  • Open the SAP Software Delivery Manager:
  • Navigate to the SDM by typing:
    cd /usr/sap/<YOURSID>_PORTAL/java/sdm/program
    Open the SDM by typing:
    ./startSDM.sh
    The SAP Software Delivery Manager opens.
  • In the SDM Deployment tab, click the plus sign (+) icon, browse /sapcd/eppat/CM_COLL/catalog1 and run the first CM and Collaboration SWC, kmc.swc.
  • Apply the second CM and Collaboration SWC, streamsrv.swc, from folder  /sapcd/eppat/CM_COLL/catalog2
  • Choose Next.
  • Continue to choose Next in each of the subsequent screens until you reach the screen with the Start button.
  • Choose Start to deploy the Software Catalogs (*.swc) files.
  • When deployment is finished, choose Confirm and quit SDM.
  • After the confirmation message appears, restart SAP J2EE Engine.

This may take several minutes to one hour.

To complete the CM patch installation:
Verify that the CM patch installation is successfully completed. To do so:
a.   Open the file:
usr/sap/<YOURSID>_PORTAL/j2ee/j2ee_00/cluster/server/cf_installation.report
b.   Make sure that the following line appears:
"The upgrade sequence completed successfully."

To check the installation status, see the console logs:
/usr/sap/<YOURSID>_PORTAL/j2ee/j2ee_00/cluster/server/managers/console_logs/*<time stamp>.log

Patch Deployment Verification

Checking and Fixing *.ERR Files with the System Analyzer
Use- The System Analyzer tool is a convenient way of checking the portal system for errors and applying fixes where available. For more information about using the analyzer, see Verify Installation Readiness with the System Analyzer in the portal installation guide on SAP Service Marketplace, at service.sap.com/ep60 → Documentation & More → Installation.
Procedure
1.   Launch the Analyzer. To do so, go to the folder:
/usr/sap/<YOURSID>_PORTAL/j2ee/j2ee_00/Analyzer/

2.   Run the following file:
./go

  • From the Navigation panel, choose Analyzer → Files → Backup Files.
  • From the right-click menu, select Analyze. The analysis results are displayed in the output area.
  • If *.err files are listed, use the Fix option from the right-click menu to turn them to *.bak files.
  • To redeploy, restart the SAP J2EE Engine.
  • Repeat the Analyzer test. If you find more *.err files, contact your local support
    center/software supplier.
  • Manually Check for *.ERR files Procedure
    Checking for undeployed PAR files:
    After restarting the SAP J2EE Engine, go to the following directories:
    /usr/sap/<YOURSID>_PORTAL/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/ WEB-INF/deployment
    /usr/sap/<YOURSID>_PORTAL/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp /irj/root/WEB-INF/deployment/pcd
    Check each PAR file.
    • A file that was successfully deployed will read: <name of file>.PAR.BAK
    • A file that was not successfully deployed will read: <name of file>.PAR.ERR
    To check for deployment errors on an NT machine, follow the same paths as described in this section. The log file on NT will have a .log extension.
    Checking for undeployed EPT files:
    1. After restarting the SAP J2EE Engine, go to:
    /usr/sap/<YOURSID>_PORTAL/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp /irj/root/WEB-INF/deployment/pcdContent
    2.   Check each EPT file.
    • A file that was successfully deployed will read: <name of file>.EPT.BAK
    • A file that was not successfully deployed will read: <name of file>.EPT.ERR
  • Manually Rename *.ERR files Use
    If the patch deployment checks indicate that error files have been created, try to fix the errors by renaming the files.
    Procedure
    To manually rename *.ERR files on UNIX platform:
    If there are *.PAR.ERR or *.EPT.ERR files after deployment, go to the directory where those files are located and run one of the following lines:
    • For *.PAR.ERR files:
    ls -d *.par.err | sed 's/\(.*\)\.par.err$/mv & \1.par/' | sh

    • For *.EPT.ERR files:
    ls -d *.ept.err | sed 's/\(.*\)\.ept.err$/mv & \1.ept/' | sh

    These commands remove the ERR suffix from the file name (all *.PAR.ERR files to PAR; all *.EPT.ERR files to EPT).
    Restart SAP J2EE Engine. Log in with account j2eeadm
    To manually rename ERR files on Windows platform:
  • Rename the *.PAR.ERR and *.EPT.ERR files manually, using Windows explorer or any other Windows means/
  • Restart SAP J2EE Engine.

If the error persists open a CSN message with SAP customer support and provide the corresponding log file <name_of_file>.PAR.LOG or <name_of_file>.EPT.LOG.

Error after installation
            Element got disconnected with the following error message

            System can’t write to file ./managers/log/thread/WARNING

Checked the file permission and found that only root has write permission changed it so that j2eeadm is the own and group is sapsys
 



 
Copyright © 2005 - 2007 SAP Security Online.com All Rights Reserved.