Find in this Blog

Thursday, March 12, 2015

SSO- Configuration

How to configure the SSO (Single sign on) for Portal?  What are the steps needs to be taken?
 
Single Sign On with Portal to SAP Backend Systems 
  
Single Sign On (SSO) is good documented in the SAP world. This guide to give you a complete working example of how you can enable SSO in your environment.
Step 1 - Setting the logon method as Single Sign on 
1.1 Log in to your Portal as a System Administrator. 
1.2 Choose System Administration --> System Configuration --> System Landscape
1.3 Find the system you want to assign Single Sign on to and open it
1.4 Choose User Management as Property Category
1.5 Set Logon Method to SAPLOGONTICKET
What we have done now is to set the system you want to use as a Single Sign On logon method. Do this to each system you want to connect.
Step 2 - Create a Portal Certificate 
1.1 Log in to the Visual Administrator
1.2 Choose Server --> Services --> KeyStorage --> TicketKeystore
1.3 Delete SAPLogonTicketKeypair-cert and SAPLogonTicketKeypair
1.4 Choose Create (Create button in the Entry field) and  
type in the following information: 
a. mark Store Certificate  
b. Common Name: Your <SID> (just example) 
c. Entry Name: SAPLogonTicketKeypair  
d. Store Certificate: Mark it 
e. Key Length: 1024 
f. Algorithm: DSA 
g. Press Generate
Now you will have two entries in the TicketKeyStore:
SAPLogonTicketKeypair 
SAPLogonTicketKeypair-cert
Step 3 - Export the Portal certificate 
3.1 Choose Server --> Services --> KeyStorage --> TicketKeystore
3.2 Choose SAPLogonTicketKeypair-cert and press Export (Export button in the Entry field)
a. Fill in a name of the Certificate 
To keep track of your certificate, call it the SID of the Portal
b. Choose either X.509 or Base64 Encoded Format
Step 4 - Import the Portal certificate to the Backend System 
4.1 Log in to the Backend System 
In my example, I log in to ERP 2004
4.2 Run transaction STRUSTSSO2
4.3 Press Import Certificate (Button in the Certificate field)
a. Open the generated certificate from step 3 with the right file format that you choosed in step 3.4
4.5 Press Add to Certificate List button (Button in the Certificate field)
4.6 Press Add to ACL button (Button in the Certificate field)
a. Enter the <SID> of your Portal
b. Enter Client 000
4.7 Press Save
Step 5 - Export the Backend certificate to your Portal
5.1 You are still in the transaction STRUSTSSO2. Doubleclick the Owner Certificate and choose Export and store in on the file system
5.2 Log into Visual Administrator 
Choose Server --> Services --> KeyStorage --> TicketKeystore and press Load and choose the Certificate
5.3 Set the Backend System as "ACL" in the Portal 
Choose Server --> Services --> Security --> Provider --> Ticket
Choose the Authentication tab and add the following on the com.sap.security.core.server.jass.EvaluateTicketLoginModule:
trustedsys<Number>=<ABAP_SID>, <CLIENT> (for example, ABA, 200)
trustediss<Number>=<ISSUER_DISTINGUISHED_NAME> (for example, CN= ABA)
trusteddn<Number>=<SUBJECT_DISTINGUISHED_NAME> (for example, CN=ABA)
You have set up a trusted relationship between your portal and the backend system. To do so with several system, run this guide again from step 4

Tuesday, February 10, 2015

Not able to open 'Memory Overview' Editor

Symptom
  • When you choose the option, "Open Memory Overview" under system context menu in HANA studio, below error appears in the studio.
  • Error while opening 'Memory Overview' editor; Reason: You do not have the required privilege.

memory.png


Environment
SAP HANA Revision 70 and above


Reproducing the Issue
  1. Open HANA studio
  2. Run "Open Memory Overview" under SYSTEM menu
  3. You face the error: "Error while opening 'Memory Overview' Editor."


Cause
The user is missing a privilege which is "sap.hana.admin.roles::Monitoring"


Resolution
You can execute statement below in HANA Studio.
call GRANT_ACTIVATED_ROLE('sap.hana.admin.roles::Monitoring','<userName>');

Thursday, January 22, 2015

ORA-25153: Temporary Tablespace is Empty

BR0301E SQL error -25153 at location stats_tab_collect-69, SQL statement:
'EXECUTE stmt_1d'
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"CCSELTAB"', ESTIMATE_PERCENT => 30, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => T
ORA-25153: Temporary Tablespace is Empty
ORA-06512: at "SYS.DBMS_STATS", line 23829
ORA-06512: at "SYS.DBMS_STATS", line 23880
ORA-06512: at line 1
BR0886E Collecting statistics failed for table SAPSR3.CCSELTAB
BR0280I BRCONNECT time stamp: 2015-01-22 18.09.23
BR0883I Table selected to collect statistics after check: SAPSR3.SDBAR (1/1:0:0)
BR0280I BRCONNECT time stamp: 2015-01-22 18.09.23
BR0881I Collecting statistics for table SAPSR3.SDBAR with method/sample C ...
BR0280I BRCONNECT time stamp: 2015-01-22 18.09.23
BR0884I Statistics collected for table: SAPSR3.SDBAR, rows old/new: 1/2
BR0280I BRCONNECT time stamp: 2015-01-22 18.09.23
BR0850I 1 of 5 objects processed - 0.001 of 0.004 units done
BR0204I Percentage done: 20.00%, estimated end time: 18:09
BR0001I **********________________________________________
BR0280I BRCONNECT time stamp: 2015-01-22 18.09.23
BR0883I Table selected to collect statistics after check: SAPSR3.TBTCS (37/463:920:462)
BR0280I BRCONNECT time stamp: 2015-01-22 18.09.23
BR0881I Collecting statistics for table SAPSR3.TBTCS with method/sample C ...
BR0280I BRCONNECT time stamp: 2015-01-22 18.09.23
BR0301E SQL error -25153 at location stats_tab_collect-66, SQL statement:
'EXECUTE stmt_1a'
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"TBTCS"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => TR
ORA-25153: Temporary Tablespace is Empty
ORA-06512: at "SYS.DBMS_STATS", line 23829
ORA-06512: at "SYS.DBMS_STATS", line 23880
ORA-06512: at line 1
BR0886E Collecting statistics failed for table SAPSR3.TBTCS
BR0280I BRCONNECT time stamp: 2015-01-22 18.09.23
BR0879I Statistics checked for 34001 tables


Solution

SQL> alter tablespace PSAPTEMP add tempfile='H:\oracle\gwd\sapdata1\temp_1\temp.
data1' reuse;
alter tablespace PSAPTEMP add tempfile='H:\oracle\gwd\sapdata1\temp_1\temp.data1
' reuse
                                      *
ERROR at line 1:
ORA-02236: invalid file name


SQL> alter tablespace PSAPTEMP add tempfile 'H:\oracle\gwd\sapdata1\temp_1\temp.
data1' reuse;

Tablespace altered.
SQL> commit;
Commit complete.
SQL>