small info on LDAP CONNECTOR

USE

The LDAP Connector interface is a collection of function modules with which you can access a directory server using the LDAP connector

Configuring the LDAP connector

Prerequisites

Whoever starts the LDAP connector requires authorizations S_RZL_ADM9 

Procedure

1.Create a RFC destination of connection type T in transaction sm59 .(Need to specify the name of the RFC destination in capital letters).

2.Select Registered server program as activation type.

3.Use the name of the RFC destination as the program ID.

4.Under Gateway Options,enter the gateway with which the LDAP connector is to register.

5.Save your entries.

6.Now transaction LDAP (In the initial screen of the directory service maintenance),choose LDAP Administration-->Connector,or the Connector push button.The system displays the Display "LDAP Connector (Maintenance view)" View : Overview screen

7.Switch to change mode and select New entries .The system displays the new entries :Details of added Entries screen.

8.Enter the following data for the LDAP connector

Field    Meaning

Connector name    Name of the RFC destination for the LDAP connector

Application server   Name of the application server on which the LDAP Connector is to be   started

Status               Target status of the CCMS monitoring

Trace level               Possible trace levels

 TRACE OFF(The program start and all error messages are nevertheless always logged)                                     

9. Save your entries

10. To start the Connector,Choose start the Connector.

Operation of LDAP connector

When you start the LDAP Connector, the operating system displays an error message because the library is not found.

To operate the LDAP connector,the " libldapssl40.sl","libldapssl41.so" or "libldap41.sl" library is required on the HP-UX platform,depending on the release.The LDAp Connector requires a library for communication using the LDAP protocol.Please see the solution below.

Solution

cd /usr/sap//SYS/exe/run

On PA-RISC for 64-bit

#ln -s /usr/lib/pa20_64/libldap.sl libldapssll40.sl

#ln -s /usr/lib/pa20_64/libldap.sl libldap41.sl

ON IA for 64-bit

#ln-s /usr/lib/hpux64/libldap.so libldapssl41.so

Once the above is done.Please start the LDAP connector

Please execute the following for PA RISC server

/usr/sap/SID/SYS/exe/run/ldap_rfc -a LDAP -x sapgw00 -g hostname -l o -f /usr/lib/pa20_64/dld.sl

Please execute the following for Itanium server

/usr/sap/SID/SYS/exe/run/ldap_rfc -a LDAP -x sapgw00 -g hostname -l 0 -f /usr/lib/hpux64/dld.sl

RESULT

The LDAP Connector is available and can be selected in the Connector filed in the Directory service Maintenance screen

CHECK

To check the activation of the LDAP Connector,view the logs in the trace files dev_.trc i.e dev_ldap.trc using transaction ST11.

Knowing on HARDWARE SIZING

HARDWARE SIZING -----very big deal??? Estimating hardware resources always leave you with many scenarios.Firstly will give a quick abstract----

Approximation of the Hardware resources required to support a particular software application.

To do this there are many ways.ground level-->Firstly from the software product view ---Will know more about customer requirements,sizing questionnaires & calculate the resources from the experience side (experience->always working on sizing will be able to give the rough estimate)

But Most of the companies provide there own various tools for the sizing like IBM.Oracle,SAP quick sizer,HP -Unix.They would say for free though but again If you need the accurate resource you need to pay for it .....

From SAP point of view

The SAP going live Functional upgrade check which consists of several sessions and is part of SAP standard support ensuring basic safeguarding of customers upgrade projects where Certified Consultants perform each session through a remote connection.

For example the values of one system which need to be upgraded from 47E to ECC6 .Regarding system environment. Central instance has 34 cpu's on HP-UX with 143 GB memory & 6 appservers on linux each with 8 cpu's & around 31Gb of memory ,Db size is of 6 Terabytes..Note 0901070 note gave a very good explanation of the effect on system hardware after the upgrade & satisfied with my result after reading various documentation.

Quick view of SAP EURO CONVERSION from admin eye

Why we do conversion?

To support legal requirements.SAP has implemented the SAP euro conversion back in 1998.Designed in collaboration with auditors & certified.. Used by severall thousand SAP customers.

Which data is principally converted

Customizing data

Master data

Transaction data

Customer specific data is considered

Search function for customer reports

Search function for Datadictionary

Ok now will jump to my field SAP Basis tasks

Main steps to follow are ....

Note no 534036

Data backup

Switch of archive logging

Adjust database parameters

Data backup

1.A backup before conversion is required to have a valid restore point,Also for documentation purposes before live conversion

2.Another backup after conversion is recommended to have a restore point after conversion incase the system must be restored at a later stage for reasons independent of the conversion..Only for live conversion.

System settings

1.Switch of archive logging

2.Adjust database parameters

3.SAP note 173993 contains general recomendations & best practices.

4.User lock for downtime-Specific functionality to lock users during conversion downtime,Determine and maintain users that should be excluded from being locked

IT IS CRUCIAL THAT NO CURRENCY RELEVANT SETTINGS ARE EVER TRANSPORTED BETWEEN CONVERTED & NON-CONVERTED SYSTEMS

ANALYSIS ----->SYSTEM SETTINGS----->CONVERSION

System settings is the part which we take care .

Note 534036 is the best one to follow for my SAP release.Normally there is a note 173993 Cluster : System settings during Euro LC changeover note belongs to 4.6C which is not our release so I went ahead with Note 534036.It gives an overview for system settings not direct for EURO-conversion, but I think it's a generally issue.

Well will put the main changes of the parameters below( well our SAP system is of 124 cup's & 7 application servers......So the changes are as below)We did 3 test runs so showing the difference of parameters between test run & production run

Comparing Test & Production

1. db_file_multiblock_read_count 32 32

2. Oracle sessions 300 800

3. Oracle Processes 200 1000

4. shared_pool_reserved_size 50M 524288000(500M)

5. shared_pool_size 500M 2634022912(2512M)

6. Redologs 500M 500M

7. undo_retention 172800 (48hrs) 43200 12hrs (48hrs)

8. pga_aggregate_target 209715200 838860800

9. db_writer_processes 5 12

10. REC/CLIENT =OFF (logging of changes in tables has been deactivated

11. tcp.nodelay=YES

12. Refresh of statistics

13. Spool retention(SAP_REORG_SPOOL should not run in the system)

We increased the table spaces as specified below. but this is independent of the total space of your database

Our database is of around 6 tera bytes. so we have to increase as below

14. DB Space(PSAPQAS) 200GB(need to increase after index rebuilds)

15. TEMP table space(PSAPTEMP) 110Gb

16. Undo space(PSAPUNDO) 250GB

17. Below are the indexes need to be created as per our system.

Create index COEP~3 with MANDT,KOKRS,BUKRS

Delete index as per EWUINDEX program(Tech team will do this)

Create index GLPCA~5 fileds RCLNT/RBUKRS

Create index ZJCISLNA~5 Fileds RCLNT/RBUKRS

For larger databases according to the following

Formula:Minimum number of batch processes = (DB size in GB / 75 GB + 1) Batch processes + 1 batch process from class A.

As per our business requirement.they need a backup system(new system) accessible after euro conversion(online with reporting facility) without any batch processes & no updates running so that no changes to the system will be possible...After few months of euro conversion again we got the request the need of few background & update & a few printers to be active for the users need later agreed on paying 200.00 euros for just the monthly backup of the system for 1 year..After that they are fine having that system offline.but that system needs to be available for next 10 years.

Just FYI the whole phases of EURO CONVERSION

We did 4 test runs before we move to production.The activities of the run

'ANALYZE' phase and activities post-shut down, pre-"conversion"

'FILL' phase

'GENERATION'

"CONVERSION" MOST CRITICAL PHASE (duration assigned - TEST1 run post SAP Optimizing -12 hrs, TEST2 run - 39 hrs, TEST3 run - 7 hrs)

'RECON' phase

COEP index deletion

GLPCA and other index recreation - SECOND CRITICAL Phase ( TEST1 run 26 hrs, TEST2 2nd run 15 hrs, TEST3 3rd run - 4 hrs)'POST' Phase

MODULE SPECIFIC ACTIVITIES

Custom program for Hyperion mapping

Validation

Well The final run was very fast.the whole euro conversion process is done comfortably in 2 days.

My very first Blog & Introduction

Greetings World



I am very new to this blogging world.Well getting noticed :-).Firstly Hello everyone.Would take a little time to introduce myself though... chandu working as SAP BASIS(Administration).... If the blogging continues (means if I spare some time)you would be knowing lot. .That would be for today guys.Will get back with my favourite topic someother time:-) Happy reading