Life cycle of SAP

 

Life cycle of SAP
Phases	Describtion of phase
Evalution	In the phase, SAP team will sits with product based company and Analysis their business.
Project prepartion	In this phase, Project planning will be done.Goals,scope,timeline,budget & establishing the project team.
Business blue print	Business processes mapping to corresponding SAP processes.
Realization	in this phase, actual configuration and customization of the system. only Development server will be designed here.
Testing	What ever the development they did in above, tests will be done.
Final preparation	Production server starts building.
Go-live	Few configurations where are specifically to production server can be done in this phase.
Sustain/support	To few errors in case of any and to adopt new features.
End of maintainence	SAP dont support for this versions.
Evalution	In the phase, SAP team will sits with product based company and Analysis their business.

why we need encrypt data volume in SAP HANA.

Encrypting the data volume in SAP HANA is crucial for ensuring the security and integrity of sensitive data. Here’s why it is needed:

1. Data Protection

Prevents unauthorized access to stored data, even if someone gains access to the physical storage.

Protects sensitive business data, such as financial records, customer information, and trade secrets.

2. Regulatory Compliance

Helps meet compliance standards like GDPR, HIPAA, PCI-DSS, and SOX, which require data encryption at rest.

3. Security Against Physical Theft

If the storage medium (disks, SSDs) is stolen or lost, encrypted data remains unreadable without the encryption keys.

4. Prevention of Data Tampering

Encryption ensures that data remains unchanged unless accessed through authorized SAP HANA mechanisms.

5. SAP Security Best Practices

SAP recommends enabling data volume encryption as part of its security guidelines to maintain a secure system landscape.

How SAP HANA Data Volume Encryption Works

Data volume encryption encrypts data pages before writing them to disk.

Uses AES-256 encryption algorithm for strong security.

The encryption keys are managed securely within SAP HANA Secure Store in the system database.

Would you like guidance on how to enable data volume encryption in SAP HANA?

To enable data volume encryption in SAP HANA, follow these steps:

---

Prerequisites

✅ You must have SYSTEM or DATABASE ADMIN privileges.

✅ SAP HANA version SPS 09 or later supports data volume encryption.

✅ Ensure that Backup Encryption is also enabled to prevent unencrypted backups.

---

Steps to Enable Data Volume Encryption

1. Check Current Encryption Status

Run the following SQL command in SAP HANA Studio or DBA Cockpit to check if encryption is already enabled:

SELECT * FROM M_ENCRYPTION_OVERVIEW WHERE NAME = 'DATA_VOLUME';

If ENCRYPTED = FALSE, encryption is not enabled.

---

2. Enable Data Volume Encryption

Run the following SQL command:

ALTER SYSTEM PERSISTENCE ENCRYPTION ON;

This command enables encryption for new and modified data pages.

Existing data remains unencrypted until rewritten (e.g., via table reload or reorganization).

---

3. Restart SAP HANA Database

Restart SAP HANA to apply changes:

SHUTDOWN IMMEDIATE;

Then, start SAP HANA again using SAP HANA Cockpit or command line.

---

4. Verify Encryption

After the restart, check the encryption status again:

SELECT * FROM M_ENCRYPTION_OVERVIEW WHERE NAME = 'DATA_VOLUME';

If ENCRYPTED = TRUE, encryption is successfully enabled.

---

Additional Steps (Optional but Recommended)

✅ Encrypt Existing Data

Since existing data is not automatically encrypted, consider the following approaches:

Reorganize Tables: Reload tables using:

ALTER TABLE <table_name> REORGANIZE;

Perform a Full Backup & Restore:

Take a backup.

Restore it to enforce encryption on all data.

✅ Enable Backup Encryption (Recommended)

Ensure backups are also encrypted to prevent data leaks:

ALTER SYSTEM BACKUP ENCRYPTION ON;

---

Key Considerations

⚠️ Performance Impact: Encryption slightly increases CPU load (~3-5%).

⚠️ Key Management: The encryption keys are securely stored in SAP HANA Secure Store.

⚠️ Recovery & Migration: Ensure you securely back up the encryption keys when migrating or recovering the database.

Would you like assistance with key management or performance tuning after enabling encryption?

Key Management & Performance Tuning for SAP HANA Encryption

After enabling data volume encryption, it's crucial to manage encryption keys securely and optimize system performance.

---

1. Key Management in SAP HANA

Where are the Encryption Keys Stored?

SAP HANA securely stores encryption keys in the Secure Store in File System (SSFS).

The key file is located at:

/usr/sap/<SID>/SYS/global/security/rsecssfs/data/SSFS_<SID>.DAT

The SSFS master key is stored in:

/usr/sap/<SID>/SYS/global/security/rsecssfs/key/SSFS_<SID>.KEY

Key Management Best Practices

✅ Backup the SSFS Key Files

Since encryption keys are needed for recovery, always back up both:

tar -cvf SSFS_Backup.tar \

/usr/sap/<SID>/SYS/global/security/rsecssfs/data/SSFS_<SID>.DAT \

/usr/sap/<SID>/SYS/global/security/rsecssfs/key/SSFS_<SID>.KEY

Store the backup securely (e.g., external encrypted storage).

✅ Rotate Encryption Keys Regularly

To rotate keys without downtime:

ALTER SYSTEM ENCRYPTION KEY RENEW;

This generates a new encryption key and updates encrypted data.

✅ Restore SSFS Keys During System Recovery

If migrating or recovering SAP HANA, restore the SSFS key files before starting the database.

cp SSFS_<SID>.DAT /usr/sap/<SID>/SYS/global/security/rsecssfs/data/

cp SSFS_<SID>.KEY /usr/sap/<SID>/SYS/global/security/rsecssfs/key/

---

2. Performance Tuning After Enabling Encryption

CPU Optimization

Since AES-256 encryption increases CPU load (~3-5%), optimize SAP HANA’s performance:

✅ Enable Hardware-Accelerated Encryption (AES-NI Support)

SAP HANA automatically detects AES-NI (Intel/AMD) for faster encryption.

To check if AES-NI is enabled:

cat /proc/cpuinfo | grep aes

If not supported, consider upgrading hardware or adjusting workload distribution.

✅ Monitor CPU Utilization

Use the following query to check CPU load:

SELECT * FROM M_LOAD_HISTORY WHERE MEASUREMENT = 'CPU';

If CPU usage is consistently high, consider scaling up hardware or adjusting parallel processing.

---

I/O Performance Optimization

✅ Enable Data Compression

Data compression reduces I/O load by minimizing storage size:

ALTER TABLE <table_name> COMPRESS FOR OLTP;

✅ Optimize Page Load Behavior

Adjust global.ini parameters for better read performance:

[persistence]

page_load_io_parallelism = 16

✅ Use Fast Storage (NVMe SSDs)

If experiencing slow write speeds, move encrypted volumes to high-speed SSDs for better performance.

---

Monitoring & Troubleshooting Encryption Performance

✅ Check Encryption Performance with System Views

To monitor encryption performance impact:

SELECT * FROM M_ENCRYPTION_STATUS;

Look for high ENCRYPTION_CPU_TIME values.

✅ Monitor Read/Write Latency

SELECT * FROM M_VOLUME_IO_TOTAL_STATISTICS;

If WRITE_TIME increases significantly, consider upgrading disk speed.

---

Final Recommendations

✔️ Regularly backup SSFS keys to avoid encryption-related recovery issues.

✔️ Monitor CPU and disk performance after enabling encryption.

✔️ Optimize storage & enable compression to balance security and performance.

✔️ Use AES-NI acceleration for faster encryption processing.

Would you like specific guidance on backup strategies, high availability, or disaster recovery with encrypted SAP HANA?

Backup Strategies, High Availability, and Disaster Recovery for Encrypted SAP HANA

Since your SAP HANA system has data volume encryption enabled, backups, failover, and disaster recovery must ensure encrypted data remains secure and recoverable.

---

1. Backup Strategies for Encrypted SAP HANA

Key Considerations

Backup Encryption: If data volume encryption is enabled, backups must also be encrypted.

SSFS Key Backup: Encryption keys are required to restore encrypted data.

Types of Backups

✅ Full Database Backup (Recommended for Encrypted Data)

Encrypts the backup automatically when data volume encryption is enabled.

Can be scheduled via SAP HANA Cockpit or run manually:

BACKUP DATA USING FILE ('/hana/backup/full_backup');

Validate backup encryption:

SELECT * FROM M_BACKUP_CATALOG WHERE ENTRY_TYPE_NAME = 'complete data backup';

✅ Incremental & Differential Backups

Incremental Backup: Saves changes since the last backup.

Differential Backup: Saves changes since the last full backup.

To create incremental backups:

BACKUP DATA INCREMENTAL USING FILE ('/hana/backup/incremental_backup');

✅ Log Backups (Continuous Protection)

Ensures minimal data loss by saving transaction logs.

Must be stored securely:

BACKUP LOG USING FILE ('/hana/backup/log_backup');

Enable automatic log backup in global.ini:

[persistence]

log_backup_interval = 900

Backup Best Practices

✔️ Backup both the encrypted data and SSFS keys.

✔️ Store backups securely in a different location (e.g., cloud storage or offsite).

✔️ Automate backups with a schedule using SAP HANA Cockpit or a script.

✔️ Test backup restoration regularly.

---

2. High Availability (HA) for Encrypted SAP HANA

High Availability Setup Options

✅ System Replication (Recommended for SAP HANA with Encryption)

SAP HANA System Replication ensures real-time failover between primary and secondary instances.

Steps to Configure System Replication with Encrypted Data

1️⃣ Enable System Replication on Primary:

hdbnsutil -sr_enable --name=PRIMARY_SITE

2️⃣ Register the Secondary System:

hdbnsutil -sr_register --name=SECONDARY_SITE --remoteHost=<primary_host> --remoteInstance=<instance_number>

3️⃣ Start Replication:

hdbnsutil -sr_start

4️⃣ Check Replication Status:

SELECT * FROM M_SERVICE_REPLICATION;

System Replication Considerations for Encrypted SAP HANA

✔️ Ensure encryption keys (SSFS) are replicated to the secondary system.

✔️ Use synchronous replication for critical data (prevents data loss).

✔️ Test failover scenarios regularly.

---

3. Disaster Recovery (DR) for Encrypted SAP HANA

Key Considerations for Disaster Recovery

Both data and encryption keys (SSFS) must be backed up and recoverable.

Use geo-redundant storage for backup retention.

Disaster Recovery Plan

✅ Step 1: Restore SAP HANA Backup in a Disaster Scenario

1. Copy backup files to the new server.

2. Restore the database:

RECOVER DATA USING FILE ('/hana/backup/full_backup');

3. Restore log backups if needed:

RECOVER LOG;

✅ Step 2: Restore SSFS Encryption Keys

1. Copy the SSFS backup to the new system:

cp SSFS_<SID>.DAT /usr/sap/<SID>/SYS/global/security/rsecssfs/data/

cp SSFS_<SID>.KEY /usr/sap/<SID>/SYS/global/security/rsecssfs/key/

2. Restart SAP HANA:

HDB start

✅ Step 3: Verify Data Integrity After Recovery

Check encryption status:

SELECT * FROM M_ENCRYPTION_STATUS;

Ensure system is running in normal mode:

SELECT * FROM SYS.M_DATABASE;

---

Final Recommendations

✔️ Always back up SSFS keys along with encrypted data backups.

✔️ Use system replication for HA to minimize downtime.

✔️ Test backup restoration and DR drills at least once per quarter.

✔️ Store backups securely in offsite/cloud storage for disaster protection.

how to recover SAP HANA database. if data volumes are encrypted. using Hana studio.

if i dont have ssfs key and data. what error i will get

Recovering an Encrypted SAP HANA Database Using SAP HANA Studio

When data volume encryption is enabled in SAP HANA, recovering the database requires both:

1. The database backup (full + log backups)

2. The SAP Secure Store in File System (SSFS) key

If the SSFS key is missing, SAP HANA cannot decrypt the data, and you will get an error.

---

1. Recovery Steps in SAP HANA Studio

Step 1: Start Recovery in SAP HANA Studio

1️⃣ Open SAP HANA Studio and connect to the system.

2️⃣ Go to Backup and Recovery → Recover System.

3️⃣ Select Recover Database from Backup.

4️⃣ Choose the latest Full Data Backup from the catalog.

5️⃣ Click Start Recovery.

Step 2: Provide SSFS Key for Encrypted Data

If the system is encrypted, SAP HANA will look for the SSFS key files in:

/usr/sap/<SID>/SYS/global/security/rsecssfs/

If the SSFS key exists, SAP HANA decrypts the data and restores the database.

✅ Verify Successful Recovery:

Run:

SELECT * FROM M_ENCRYPTION_STATUS;

If ENCRYPTED = TRUE, encryption is intact, and recovery is successful.

---

2. What Happens If the SSFS Key is Missing?

If the SSFS key is missing, SAP HANA cannot decrypt the data. You will see errors like:

Error Messages in SAP HANA Studio

1. Error: Authentication failed. Cannot open Secure Store

This happens if the SSFS key file is missing or corrupted.

2. Error: Encrypted data cannot be read. Missing encryption key.

This means SAP HANA cannot decrypt the data volumes.

3. Error: Recovery failed: Cannot read encrypted data

The backup is restored, but the system cannot decrypt the database.

📌 Command Line Error (if recovering via CLI)

hdbsql RECOVER DATA USING FILE ('/hana/backup/full_backup');

Output: Could not decrypt persisted data. Recovery failed.

---

3. How to Fix the Issue? (If SSFS Key is Missing)

✅ Option 1: Restore SSFS Key Backup

1️⃣ Copy the SSFS backup from a secure location (if available).

2️⃣ Restore it to the correct location:

cp SSFS_<SID>.DAT /usr/sap/<SID>/SYS/global/security/rsecssfs/data/

cp SSFS_<SID>.KEY /usr/sap/<SID>/SYS/global/security/rsecssfs/key/

3️⃣ Restart SAP HANA:

HDB restart

✅ Option 2: Restore Without Encryption (Only If No SSFS Backup Exists)

⚠️ Warning: This will erase encrypted data, and you will lose all encrypted records.

1️⃣ Delete the encrypted database volumes:

rm -rf /hana/data/<SID>/mnt00001/*

2️⃣ Start SAP HANA in a new, unencrypted mode:

HDB start

3️⃣ Restore a backup that was not encrypted.

🚨 If all backups are encrypted and SSFS is lost, the data is unrecoverable.

---

4. Final Recommendations

✔️ Always back up SSFS keys when performing a full backup.

✔️ Store keys securely in a separate location (e.g., external drive, cloud).

✔️ Test recovery scenarios in a non-production environment.

Would you like a script to automate SSFS key backup along with database backups?

Monitoring memory Usage of table

 Memory is SAP HANA is used for a variety of purposes.

 First, the operating systems and support files are using memory.

second, SAP HANA has its own code and stack of program files that alsoconsume memory.

Third,memeory is consumed by the column and row store where data is stored.

Finally, SAP HANA needs memory for its working space where computations occur, temporary results are stored, and shared user memory consumption occurs.

In short, physical memory is the maximum memory available, some of which is used by the operating systems and files.The allocated limit is what is "given" to SAP HANA, and the remaining memory is free space.These allocations are important because you're using preallocated memory pools, and you can't rely on Linux operating system information for memory management.However,you can get this information in many other ways.

In addition to the memory consumption and memory tracking information in the preceding sections, you can also obtain memory information using SQL statements. In the M_SERVICE_MEMORY view, you can  execute a set of predefined SQL statements provided by SAP, including those shown below:


To access these statements, open the SQL console from the context menu of the VIEWS folder in  the SYS schema.


Total Memory Used by All Row Tables:
Select round (sum(USED_FIXED_PART_SIZE +USED_VARIABLE_PART_SIZE)/1024/1024) AS "ROW Tables MB" FROM M_RS_TABLES;

Total Memory used by All Column Tables:

Select round (sum(MEMORY_SIZE_IN_TOTAL)/1024/1024) AS "Column Tables MB" FROM M_CS_TABLES;

Total Memory Used by all column Tables in a Schema

Select SCHEMA_NAME AS "Schema", round (sum(MEMORY_SIZE_IN_TOTAL) /1024/1024) AS "MB" FROM M_CS_TABLES GROUP BY SCHEMA_NAME ORDER BY "MB" DESC;

For column tables, SAP HANA sometimes unloads infrequently used columns from memory to free up space when the allocated memory threshold is near the used capacity.So, when memory consumption is estimated, it's important to look at all column tables, not just those currently loaded in memory. You can see all column table sizes in a schema by using the SAP provided SQL statement:


Total Memory by column Tables in a schema:

Select TABLE_NAME AS "Table", round (MEMORY_SIZE_IN_TOTAL/1024/1024, 2)as "MB" FROM M_CS_TABLES WHERE SCHEMA_NAME = 'SYSTEM' ORDER BY "MB" DESC;

Select TABLE_NAME AS "Table", round (MEMORY_SIZE_IN_TOTAL/1024/1024, 2)as "MB" FROM M_CS_TABLES WHERE SCHEMA_NAME = 'XJRM63' ORDER BY "MB" DESC;

Different types of Nodes

Different types of Nodes available in webide :

• Join
• Non Equal join
• Union
• Minus
• Intersect
• Graph
• Projection
• Aggregation
• Rank
• Table Function
• Hierarchy Function
• Anonymization

  Calculated Column: A column which can be built on top of original columns in the view. it can also be used independently for eg to display static values , set flags and so on.

Mapping  tab: you are settle the required set of columns and assigning them to the next node.

How to get hardware key of the ABAP system at OS LEVEL

 Login with <sid>adm

Cmd:

Saplikey -get

Output:

HARDWARE KEY = **************

Enqueue work process utilized percentage monitoring

 in this post, how much enqueue WP is filled info will be shown.

Practical steps:

1. Access the T-code SM12.

2.Resultant screen will looks like below:

     

3. Perform the below highlighted navigation.

    More --> Extra --> Statistics.

4. Maximum no of lock entries supported by the server is 441075

   Current filled level is 334519

Conclusion:

Almost 75%+ portion is filled.

Different kinds of HA DR replication modes and operation modes

 

Lock Client of SAP system

 1. SCCR_LOCK_CLIENT (to lock the client)

2. SCCR_UNLOCK_CLIENT (to unlock the client)

This function is used to lock \ unlock client from logins. When you lock a client, all users try to log on A client will show message “A client currently blocked from entering.” A client will be available for entry only available to users SAP * and DDIC.

To lock:

1. Run t-code : SE37
2. Enter the name of the module SCCR_LOCK_CLIENT
3. Press F8 to activate

4. Enter the number of client and press (F8).

To unlock:

1. Run t-code : SE37
2. Enter the name of the module SCCR_UNLOCK_CLIENT
3. Press F8 to activate
4. Enter the number of client and press (F8).

My reference:

https://blogs.sap.com/2014/12/02/lock-client-of-sap-system/

Concept of swap-in and swap-out

 During normal operation a Linux system tries to keep all application data in physical memory. Linux uses swap-space to store inactive memory pages, evicted from the systems physical memory, in order to free up physical memory capacity. The operation of evicting memory pages from the physical memory to the swapspace is called "swap-out". The operation of restoring pages from the swap-space into the physical memory is called "swap-in".

My Reference:

https://launchpad.support.sap.com/#/notes/1597355

How to extend the EBS volume size of EC2 instance.

This post will answer the below question:

1.How to extended the EBS volume size of EC2 instance.

Thumb rule:

• Whatever the availability zone the EC2 instance is running, in the same region the EBS volumes are available. the reason behind this rule is hard disk also should be near to mother board.
•  if in case the EC2 instance and EBS volume are in 2 different availability zones then manually need to make that available in single availability zone.

Advantage with EBS:

• can increase the EBS volume size and type on fly. No need to stop or shutdown the system.

Practical steps:

1. login aws console.

2.Navigate to services -->compute -->EC2-->Running EC2 instance -->select the correct EC2 instance.  where the modification of EC2 instance is required.

3. Under Elastic Block Store  --> click on volumes.

     Here in the availability zone column, each EBS disk can be found here.

              in the Volume Type column -->EBS type info is available.

   To extended the size of one particular EBS drive -->select the correct EBS drive -->Actions dropdown --> Modify volume.

4. Here in the below highlighted field the default size of EBS drive is 500GiB and can change the size here. just by enter the required size here in the highlighted field.

5.with in short time the additional storage will add in to the EC2 instance. & To adopt this additional storage few steps need to perform at OS level. This detail steps will be available in the below highlighted links(window or Linux) and finally click on YES to conform adding additional storage.

6.Then the below conform & succeeded screen will appears as shown below.                                           

7. if you click on refresh button as shown below the additional storage will update (services -->compute-->EC2 --> Running instance -->select the correct EC2 instance )

Now in the 3rd EBS disk size increase to 1000GB,can observe in the screenshot below

How to access putty session of AWS EC2 instance using Google chrome extension

Practical steps:

1. Open Google chrome.

2.Search for ssh chrome extension as shown below.                                                                            

3. Will find the below highlighted official link.Click on it.                                                                       

4.Then the below resultant screen will appears,Click on Add to chrome.                                             

5.Then in the chrome apps list , SSH app will added as shown below.

6.Double click on the above highlighted icon.

  Then enter the user id - ec2-user (Default for all EC2 instance in AWS)

                          host name - enter the public ip of host.

7.open cmd prompt by presing windows key + R , enter cmd in the prompt and press enter.

• Navigate to download directory, where the private key is download.                                                 
• by issuing the command:   to generate the public key                                                                                                               

ssh-keygen -y -f  Mykp.pem >Mykp.pub

Here:                                                                                                                   

Mykp.pem  is key name which is download at the time EC2 instance launch.

Mykp.pub  is the name of public key, which could be different from individual.

• Now rename publlic key.by removing the extension.by running the below command:

ren MyKP.pem MykP

8.Now click on import option here.

9. Provide the path of private key and public key.and click on enter option, which is available at right bottom side of the page.

Hurrah got putty access of EC2 instance through google chrome extension.

Cross region replication of S3 bucket

 

Contentserver installation and configuration

Content Server Installation & Configuration

 

 Contents

Intellectual Property Disclaimer 3

1        Abstract: 4

2        Technical Prerequisites 5

3        Installation Process 6

4        Testing the Connection to the Content Server 26

5        Creating Content Repositories 27

6        Database Manager GUI Installation. 31

7        Backup 35

8        MaxDB and ODBC upgrade 36

9        How to Install IIS role 40

 

 

1      Abstract:

Purpose:

 

Knowledge Provider is a component of SAP Web Application Server and provides the general infrastructure for storing and administrating documents. SAP Content Server is based on the MAX DB and is available on Windows Server (OS Versions are mentioned in PAM).

Both the MAX DB database, which serves as a Content Server, and the Content Server itself are provided with every SAP system installation. This provides the required technical infrastructure for all document-oriented applications and business scenarios that do not require long-term archiving. Because SAP Content Server is integrated via the HTTP interface, the actual storage medium used is transparent to the SAP applications.

 

Need:

 

A content server is an external storage system. It can be accessed via the HTTP Content Server Interface. We can able to move the real data from SAP table to content server repository. The real data type can be anyone on the following format doc,xls,ppt,tiff,gif,jpg,cad etc.

 

Solution:

 

By using this functionality, we will get free space in SAP database level.

 

Benefits:

 

1.    The database is much better suited than a file system to the administration of large amounts of data. Internally at SAP, the SAP Content Server has been used for several release cycles to administrate all documentation

Database administration tools, which are easy to use, are delivered with it. These can be used to make automatic backups.

2     Technical Prerequisites

Hardware:

 

To install the software components, including MAX DB, you need at least 300 MB of hard disk space. You also need as much hard disk capacity as you specified for the data files and the log files for the each partition.

 

Main Memory             : At least 512 MB

Processor                    : Possible: 1 CPU Recommended: 2 CPUs

Network Protocol        : TCP/IP

Software:

 

OS       : Microsoft Windows 2008 Server or Microsoft Windows 2012 Server (with IIS)

Further Information:

 

The SAP System that you want to link to the SAP Content Server must be at least release 4.6C. The hardware platform and operating system used in the SAP System do not limit the SAP Content Server in any way. The HTTP interface ensures that the SAP System is platform-independent.

 

Note:

In the IIS 7.0/7.5, all the roles are not selected during the installation by default,

Please make sure all the below roles are included and IIS 7.0/7.5 is installed.

 

Kindly refer the installation guide to set up the required roles for IIS. We have to install the roles as per the guide before go live of this content server project.

 

 

1      Installation Process

The following sections provide the steps that you have to perform to install SAP Content Server using SWPM.

 

 

 

 

Kindly check with Wintel Team to install the latest IIS on OS level.

 

We  have faced some issues during the installation.Kindly follow the SAP note number 1571945 to fix and move forward.

4     Testing the Connection to the Content Server

 

1. Open a Web browser on a host that is connected to your local network.

2. Navigate to the following URL:

 

Ex: http://<hostname>:<portno.>/ContentServer/ContentServer.dll?serverInfo

 

Output:

 

5   Creating Content Repositories

 

1. In transaction OAC0, create at least one content repository for your Content Server.

2.Go to SE38 and run the report RSCMSPWS to set up the OS level password for your content server.

4.Click on CSADMIN tab or use CSADMIN tcode to set few Content server Repository settings

·         Parameter need to be configure as per our content server configuration.

 

6.  Database Manager GUI Installation

 

kindly Provide the server details & SUPERDBA or CONTROL password to take the admin mode on our content server database.

 

 

·         List of Administration Tasks

7.Backup

Bat file script for backup which need to be schedule every day in task scheduler.

 

dbmcli -d CD1 -u control,xxxxxxxxx -uUTL -c backup_Start DATA_BKUP Recovery

 In this case, we are keeping last two successful backup to restore if necessary.

·         Delete script:

 

del X:\CSBACKUP\fullbkp_old1.bkp

 

·         Rename Script :

 

RENAME X:\CSBACKUP\fullbkp.bkp fullbkp_old.bkp

 

·         Rename1 Script :

 

RENAME X:\CSBACKUP\fullbkp_old.bkp fullbkp_old1.bkp

8   MaxDB and ODBC upgrade

                    Download the MaxDB upgrade guide from service market place.

 

We have two approaches for this DB upgrade:

 

7.5 or later           : In-Place upgrade

7.9                        : patch Installation

 

Here we have MaxDB 7.6, so we are go with in-place upgrade.

 

1. Download the MaxDB 7.9 version and call the DBUPDATE.BAT in cmd.
2. DBUPDATE.BAT –s SAPSID –d CSSID –u SUPERDBA,xxxxxxxxxx

ODBC Upgrade:

9      How to Install IIS role

 

Go to server ManageràRolesàAdd Role servicesàInstall

 

References:

 

·         Installation Guide -SAP Content Server for Windows 2008/R2

·         Upgrade to SAP MaxDB Database 7.9: Windows

·         http://wiki.scn.sap.com/wiki/display/MaxDB/HowTo+-+SAP+MaxDB+Recovery+with+Database+Manager+CLI

·         http://documentation.commvault.com/hds/v10/article?p=products/sap_maxdb/backup_basic.htm

·         http://documentation.commvault.com/hds/v10/article?p=products/sap_maxdb/backup_adv.htm

·         http://help.sap.com/saphelp_nw70/helpdata/en/59/fba637fcf7dc39e10000009b38f8cf/content.htm?current_toc=/en/6e/58593c95403d56e10000000a11405a/plain.htm&show_children=true

·         http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/ff90895b605dc6e10000000a42189c/content.htm?frameset=/en/4c/f8a20fb08b2136e10000000a42189e/frameset.htm&current_toc=/en/65/ea8b7b4a9041ada98be49d3b89ac86/plain.htm&node_id=37&show_children=false