Installation SAP Content Server on Windows server 2008

Pre-Requisites

• Server running on Windows Server 2008 R2
• Install Java for launching SAP installation manager
• Install web server IIS 6
• Prepare SAP Installation Master (serial number 50098620 & 51038620 )
• Download the following files from SAP marketplace (found in software
  downloads in the latest Net Weaver Package download.) 50098620_2,
  50098620_3 and the relevant installation master e.g. for Windows 2008
  server on X64 51038620_12 

Install Content Server

1) Using 51038620 select correct folder for hardware in use on the server in this

example we are installing on e.g. IM_WINDOWS_X86_64 

2) In the folder find and launch sapinst.exe

 

3) Select 'SAP NetWeaver 7.0 including Enhancement Package...', then 'Standalone Engines', then 'Content Server', lastly 'Content Server and / or Cache Server' as shown below.

4) Click on the highlighted ‘Next’ button as shown below

 
5) Click on the highlighted 'Browse' button

6) Locate the file LABEL.ASC on the 50098620_2 download or DVD and click OK

7) Click on the 'Next' button to continue

8) De‐select Cache Server and select Database Instance and select ‘Next’

9) Review and modify, if required, the installation settings and select ‘Next'

 

10) Click on browse button

11) Locate the file SDBINST.EXE on the 50098620_3 download or DVD in the corresponding directory for the operating system and type and click 'OK'

12) Once selected click 'Next'

13) You will be prompted to enter the passwords for the user accounts 'superdba' and 'control'. Please make a note of what these passwords are as you will need them later.

14) Review database installation parameters and click 'Next' 

15) Review database log volumes, this is where the log files will be stored, and click on 'Next'

16) Review storage parameters for the database, amending the storage location if required, click 'Next'

 

17) Review and amend previous entries before starting the installation. Click 'Next' to start the install 

18) The Installation process will start with the progress shown on the screen 

19) When complete a message will appear telling you it was successful. Select 'OK' to finish

How to delete old batch sessions

Users have created tons of batch input sessions and processed them with SM35. The users did not care about deleting unwanted sessions and there are a lot of old sessions, with almost any status (in processing/in background/processed/errors). All of them are junk (in your terms), and have to be removed from the system.

Batch input session with status "incorrect / error" , we can delete directly from SM35. Follow on below steps :

1) Tcode SM35

2) Choose "incorrect" tab and displayed batch input sessions with status error

3) we can delete manually by selection sessions or individually

The batch-input sessions are located in the tables APQI and APQD. If that is so, please delete the corresponding entry from table APQL and after that you will be able to delete the “In Process” sessions from SM35 Tcode. Please use the session name to search the entry in table APQL.

For example : We try delete batch input session with "in process" and queue group name "REVAL CUST"

1) Choose "in process" tab on SM35

2) Highlight session name "REVAL CUST". Please noted the date and time of this batch session.

3) Delete the corresponding entry from table APQL with SE16 

4) Input the group name with "REVAL CUST"

5) Now we can see all "REVAL CUST" batch session entry. Matching the date and time from data batch session on SM35. If result was match, we can delete the batch session entry on SE16 (makesure client setting to be open repository SCC4)

6) Back to tcode SM35 and delete batch session "REVAL CUST"

You can delete unwanted sessions with abap program RSBDCTL6 at once and then setup a background job that deletes the sessions for a specific session, user who created the session, date range, older than x days etc. that runs on a regular basis.

Alternatively way : 

a) you can run program RSBDC_REORG.  However, tests showed that this program may not be suitable for sessions that have a status other than processed. 

b) you can run program RSBDCREO *only* deletes sessions which are in status “processed”. The reason for this is that this report is written for an automatic cleanup and therefore should never remove sessions that are not completely processed. The report also only deletes the logs for sessions which are already deleted (or scheduled for deletion in the same run).

This means that when you check both options on the initial screen of RSBDCREO, the following sessions and logs will be deleted:

     1. Processed sessions and their logs

     2. Logs for which no sessions exist anymore