Steps to Install & Configure SAP Content Server 7.53 (File System) on Linux (SUSE)

Posted by — October 8, 2020 in SAP BASIS — 2 Comments

In this article, we would like to share to you, the steps to

  • To install SAP Content Server 7.53 using the file system approach and based on SUSE Linux Enterprise Server 15.
  • To configure content repository for SOFFCONT1 table.

Before we proceed further, you are advisable to see the following SAP Notes and documents.

Preparation

Download the following media files from the SAP launchpad.

  • SAP Content Server
    • Enter “SAP Content Server” into the search filed.
    • Select the desired version from the list
    • Select your operating system
    • Ensure to sort by “Change Date” in “Descending” order
    • Download the SAR archive of the latest SP
  • SAP Host Agent
    • Enter “Host Agent” into the search filed.
    • Select the desired version from the list (7.21 is the latest version as of 2019)
    • Select your operating system
    • Ensure to sort by “Change Date” in “Descending” order
    • Download the SAR archive of the latest SP
  • Software Provisioning Manager (SWPM)
    • “System Provisioning”
    • “Download Software Provisioning Manager”
    • SOFTWARE PROVISIONING MGR 1.0
    • Select your operating system
    • Ensure to sort by “Change Date” in “Descending” order
    • Download SWPM “for NW higher than 7.0x” (file name starts with “SWPM10…”)

Extract the SWPM using the SAPCAR.

Installation

Change directory to the extracted SWPM location and launch the SWPM using below command.

./sapinst

Copy the following URL and paste it to browser.

******************************************************************
Open your browser and paste the following URL address to access the GUI
https://HOSTNAME:4237/sapinst/docs/index.html
Logon users: [root]
******************************************************************

Enter the username and password.

Scroll down and look for Generic Options > SAP Content Server > SAP Content Server and SAP Cache Server (7.5 and later). Click Next.

Choose Custom. Click Next.

  • Typical Mode
    • If you choose Typical, the option is performed with default settings. As a result, you only have to respond to a small selection of prompts. If you want to change any of the default settings, you can do so on the Parameter Summary screen.
    • Note that if you choose the Typical setting and then choose Back after processing one or more input screens, the Custom setting is activated. You are now guided through all screens with the default parameters that have been applied in the background so far.
  • Custom Mode
    • If you choose Custom, you are prompted for all parameters. At the end, you can still change any of these parameters on the Parameter Summary screen.

Enter SAP System ID and the SAP mount directory.

The SAP System ID is an identifier for your SAP system. It must be unique throughout your system landscape.
The system is installed under /usr/sap/SAPSID/…. Common directories are linked to /SAP Mount Directory/SAPSID…

Enter the master password for all users.

If you want to set an individual password for each user, you can do this in the corresponding parameter section on the Parameter Summary screen. If you set individual passwords, a new master password does not overwrite these individual settings.

Leave the values to default and click Next.

The fields User ID, Group ID of sapsys and Home Directory should normally be left empty. If you enter specific user or group IDs, make sure they do not conflict with other IDs you enter later in the installation.

Specify the path to a download folder containing all software packages, or the paths to media locations or to several individual download locations of software packages.

The table below is updated with all packages detected at the specified Package Path when you choose Next.

While staying on this screen you can add or adjust paths for required packages by searching other locations. When all archives are specified and you do not wish to make any further adjustments, leave the above Package Path empty to continue

Click Next.

Choose SAP Content Server.

Enter the required instance parameters for the SAP Content Server instance.

The Instance Number and Host Name for the SAP Content Server instance are technical identifiers for controlling internal processes, such as assigned memory. They must be unique for this installation host.

Enter the network connection parameters.

For the SAP Content Server, we recommend using HTTP port 1090 and HTTPS port 1091. When migrating an existing SAP Content Server, make sure that you use the same HTTP Script as specified in OAC0. You can also adjust OAC0 to use the same HTTP Script as specified here.

Choose ‘Next’ to start with the values shown. Otherwise, select the parameters to be changed and choose ‘Revise’. You are then taken to the screen where you can change the parameter. You might be guided through other screens that have so far been processed.

Installation begin.

Installation complete.

Configuration

Verify the following URL with the web browser

  • http://HOSTNAME:PORT/sapcs?serverInfo
  • https://HOSTNAME:PORT/sapcs?serverInfo

The output shall be something like below,

serverType="SAP HTTP Content Server";serverVendorId="SAP";serverVersion="753";serverPatch="628";serverBuild="Aug  1 2020 (L)";serverStatus="running";serverDate="2020-09-02";serverTime="07:59:22";startUpDate="2020-09-02";startUpTime="07:49:30";lastAccessDate="2020-09-02";lastAccessTime="07:57:46";

Activate the following SICF service.

Launch the transaction code OAC0 and switch to change mode. Click on F5 to create a new repository.

Maintain the settings as below,

  • Content Repository name
  • Description
  • Document Area (depending on which document type and purpose)
  • Storage type
  • Version no.
  • HTTP server
  • Port Number
  • HTTP Script

Perform the connection test to the content repository.

Click on Send Certificate.

Click on CS Admin and jump to Certificates tab to activate the certificate. You will need to be in the change mode before you can activate the certificate.

Next, go to Settings tab, and maintain the parameters (this is for file system approach) and if you are using the MaxDB database, the parameter will be different. Please refer to SAP guide / notes for further information.

For the next step, we will apply SAP Content Server certificate into the SAP backend. For this example, we will use the self signed certificate method and you are always recommended to use the CA signed certificate.

Open the https://HOSTNAME:PORT/sap/admin/public/default.html, go PSE Management and click on Export Own Certificate.

Copy the cert and paste into the notepad as .cer. Open transaction code STRUST and apply the certificate in SSL client Anonymous and Standard.

Go to transaction code OACT. Change the SOFHTTP category to the newly created content repository.

In transaction code SKPR08, assign SOFFPHIO class to the new category of SOFFHTTP.

Testing & Verification

Use transaction code SE38 and enter the report name as RSCMST. Click on execute. Enter the repository and click execute.

Execute the following test.

  • RSCMSTH0
    • HTTP interface test using function group SFTP
  • RSCMSTH1
    • HTTP interface test using function group SCMS_HTTP
  • RSCMSTH2
    • HTTP interface test using function group SCMS_HTTP (docProt)

You May Also Like

RSWF_TEST_HTTP: Test HTTP Connection

Task/request SYNCMARK does not exist in system SID

“javax.rmi.CORBA.Stub” error when opening the Enterprise Services Repository & Integration Directory

Task SIDK123456 has the status “Release started”

2 Comments

  1. very useful.
    How to install content server to store docs on MaxDB instead file system?
    This post refers only CS installation with FS, Please provide documentation on MaxDB as well.

    Reply

  2. If I create content server using file system storage , where the all file will store in file system level is any specific location we should maintain where the file should store if yes how we maintain that storage path .

    Reply

Leave a Reply?