BW35 Post Install steps

BW 3.5 System Basis Post-Install and initial configuration steps…

The intention of this guide is to provide a general guideline usable on BW 2.x through 3.5 systems to set basic transactional and basis settings for standard performance. Many default system settings are not optimal, or are not landscape specific for a customer. This list provides generic, grouped settings for better over all performance, or a baseline for when certain activities will be used later in an implementation. (i.e. workflow or info broadcasting)

There are three supplemental documents referred to – these are not needed but nice to do: “How-To REALLY install BW 3x Statistics”“Initiating Workflow/Webflow settings”“Connecting a BW system to EP6.0”

All recommendations are consolidated from appropriate SAP tuning notes and conference presentations, as well as actual EarlyWatch and Go-Live check reports.

Pre-upgrade or copy functional steps

Before backing up a system for copy or upgrading it or applying a PI patch, to preserve data integrity, the following steps must be followed by the functional team:

RSA7 delta queues must be cleared – run delta process chainsSend all data to final data targetActivate all ODS requestsPromote all requests to downstream data targets (data marts)Roll up aggregatesRun hierarchy change runSuspend all process chains and background jobs

Basis steps after this:

Run Temp Tablespace cleanup report SE38 SAP_DROP_TMPTABLESRebuild Indexes SE38 SAP_INFOCUBE_INDEXES_REPAIRFix InfoObject inconsistencies RSD1 – repair InfoObjectsDisable RFC’s (//dummy hostnames) prevents accidental data transfers

Validate proper logical systems and RFC connections to other source systems

Reconnection to source systemsRSA1-source test, restore or replicate connections, re-import global settings and exchange ratesRestart (activate/schedule) process chains

2500 City West Blvd., Suite 800, Houston, Texas 77042 Phone: 713.980.7600 Fax: 713.706.4014 www.myITgroup.com

After the standard SAP install or upgrade:

Log on to client 000,

SPAD – create LOCL printer, and set LP01 as dummy.





Adjust users SAP* and DDIC:




Copy user to the basis administrator:


Assign printer LOCL:

…and any other admins that may apply patches or resolve TMS issues.


RZ10 – utilities-import profiles of active servers


In SBIW – Transfer Application Component Hierarchy


Initialize system Log in SM21:


Run SICK

In SE38 – RSCPINST



Check SLICENSE and install a license.


Perform Post-Install actions and STMS configuration in SE06


Run STMS



Verify Web server is running SMICM



Go to SICF and activate web services – initially it looks like:


After:


Under BC – activate BSP and any graphics, mime, printing or other services.

Get hardware key from SLICENSE and apply for permanent license:



The new license takes effect on system restart.

Get and apply java license key too…

Check, adjust and add work processes -

Apply kernel patch, SPAM, BASIS, ABA, BW35 and BICONT patches. SR1 starts you at SP9, BW sp10 causes an upgrade to PI-Basis 2005.1

Use Saint to add ST-PI and ST-A/PIInitialize SDCCN


To run the RTCCTOOL report you’ll need to configure OSS1 transaction/RFC.

You are now ready for the client copy:

SCC4 to create – add all landscape logical systems in BD54 when askedLog into new clientSCCL – copy client using SAP_ALL and client 000 users

When complete, set system time in STZACRun SGEN for post-install and bsp’s

Set login client: RZ10login/accept_sso2_ticket 1 login/create_sso2_ticket 2 login/system_client 100


Set system time zone in STZAC to GMT or your local TZ or stay on Central European time…

Then restart and initialize RSA1 the BW Admin workbench


Then run SGEN for BSPs and all objects


Set permitted characters in RSKC


Set up logon group PUBLIC in SMLG


Setup default 24 hour normal operations mode in RZ04


Assign to timetable:Opmode-timetable. Select change


Double click on 00:00 shift double-click on 23:00 and assign to DEFAULT



For emergency shifts of processes, you can use 15 minute intervalsNow maintain profiles:


Instances/operation modes button – create


Save and assign



Install Demo content and technical content:


Set Master Data autoSID in RSCUSTV9


Create background userSPRO



Set process chain post processing – RSTPRFC


Activate BEx personalization RS_PERS_ACTIVATE


Set default traffic light color when no data is available in source system (default is yellow) (RSMONCOLOR)


Create a flatfile source system, SAP_DEMO (flatfile), and connect to the R3 client

Entry by nitin




Now that you have a connection, transfer exchange rates and global settings.If you have more than one connection, transfer again from the master system, then update from all others, then update again from the master…usually this is the primary R3/ECC system. These are client independent, so only transfer per system, even if you have multiple client sources. This is a one time activity – some installations may bring currency exchange rate values over as master data.


Do mapping of all logical system names, and suggest source system IDs – RSA1-Tools-


Suggest and save


Then do mappings…the target source systems change to all test or all production if in those environments


In the transport connection, create a default BEx development bucket transport and set Object Changeability settings as they would be in production (they no effect on development)


Typical sample – each of these object sets are a business decision since it affects what power users can and cannot do in the system.

Object Changeability:AGGR Aggregate Changeable OriginalANMO Mining Model Everything ChangeableANPR Analysis Process Everything ChangeableANSO Model Source Not ChangeableAQQU InfoSet Query Not ChangeableBRSE Broadcast Setting Changeable OriginalCRWB Crystal Report Changeable OriginalCTRT Currency Translation Type Not ChangeableDEST Open Hub Destination Not ChangeableDMMO Data Mining Model Changeable OriginalELEM Query Element Everything ChangeableEVEN Event Processing Chain Changeable OriginalISIG InfoPackage Group Changeable OriginalISIP InfoPackage Everything ChangeableITEM Web Item Everything ChangeableQVIW Query View Everything ChangeableRAPA Reporting Agent Scheduling Pkg Changeable OriginalRASE Reporting Agent Setting Changeable OriginalRRCA RRI InfoCube Receiver Not ChangeableRRQA RRI Query Receiver Not ChangeableRSPC Process Chain Everything ChangeableRSPT Process Chain Starter Changeable OriginalRSPV Process Variants Changeable OriginalSPOK InfoSpoke Not ChangeableTMPL Web Template Name Changeable OriginalXLWB Workbook Changeable Original



Routine maintenance checks:RSD1 Repair InfoObjects - check post-patch and after major transports or content activation. Execute repair until you see this green light


RSA7 delta queue – basis team reviews for delta entries, functional team clears queues before PI patch or upgrade by running delta loads.

SE38-SAP_INFOCUBE_INDEXES_REPAIR – schedule weekly!



SE38-SAP_DROP_TMPTABLES – clears PSAPTEMP Tablespace – scheduled weekly*** DO NOT RUN WHILE OTHERS are using system – it clears their current activity ***


DB13 – set database checks Check DB consistency once per week (Sunday 10a) (CBO/Table statistics update)


And start the normal basis jobs via SSAA:


System connection parameters:SBIW-General-Data Load parameters (ROIDOCPRMS Table) – set for all landscape LS


You may have to define new LS in BD54. Set new defaults to 20000kb, (lines-100,000 by default), Info IDOC freq=10 15 or 20 per data packet, 3 (background) processes, no target system to run on (yet) and 3 max dialog…parallel processing depends on available dialog and background processes in the target system – ideally at least 15 so 3 means you can run up to 5 extract jobs in parallel…there is a targets and PSA in parallel setting in InfoPackages that may also affect this…proper extract schedule planning prevents issues.

Final – copy or transport this to all landscape systems


RSCUSTV6 (flatfile) – defaults are bad. Set to 10, 20000 (20MB) and 1,000,000 for PSA partition


RSCUSTA2 (ODS/internal system activations and load settings)


RSCUSTV18 (DB Connect) 10000 is good for records, package size 20000 or 30000 is ok


RSRCACHE/RSCUSTV14 cache parameters – show ST03, RSRTSet cache parameters to cluster table for now

Set initial default menu – SSM2 to RS00


Test SM65


Online Help – SR13 set for SAP help online at help.sap.com – always is current version!


OSS1 for SDCC


TREX – SRMO and RSODADMIN

Install TREX per manual – note the service name exactly – it is case sensitive. If on the local server use the instance’s gateway – If not, install the SAP gateway service.

Create RFC in SM59 per guide

SRMO – create SSR




RSODADMIN – walk through this screen top to bottom to schedule the jobs and index current content – leave as below:



IGS setup and test: IGS installs with the java stackSM59 Edit generated RFCs for IGS – delivered:


Corrected for your IGS destination (as seen in IGS.XML file on server) – fill in SID to program ID and the abap stack gateway information:

Test RFC:


Then test the IGS with SE38 – BW_IGS_ADMIN, and BW_IGS_CHART_TEST


If you see this on chart test, it works!

HINT: you can access this directly on web via admin port, in this case 40080 as seen in igs.xml filehttp://sapbidev:40080


http://sapbidev:40080/

This direct connection tells you the installed IGS version, which you don’t get from within the system. This is default NW2004 SR1 version:


BW STATSSee “How-to REALLY Activate BW Statistics” document – activate Technical DataSources, content…then RSA1-Tools BW Statistics for InfoProviders - select all, save without transport


Select trashcan from here and delete all old stats from RSDDSTAT tables to date…there’s junk in there. Schedule this job variant periodically later.

- hit trashcan to delete

This runs a step RSDDK_STA_DEL_DATA


Activate and assign Administrators to the SAP_BW_TCONT role for workbook access in PFCG or SU01 then select this menu with the “other menu” button as below, and save workbook to favorites.


Set default web protocol – RSCUSTV15


RSCUSTV21 – default templates – if different from delivered 0ADHOC and 0ANALYZER (nothing to set now)

RSCUSTV11 – set branded default BEx style sheet (later)

Integrate with portal EP60 from SPRO…see “Connecting a BW system to EP6.0” guide. Settings are in RSPOR_SETUP report. This screen is from SPRO - IMG


Workflow – auto-customize – see “Initiating Workflow/Webflow settings” for detailed steps if you are actually using or implementing workflow.



Email – SCOT / SMTP


Turn stuff on and connect to send internet mail by editing SMTP node


Assuming you have installed the BI pre-calculation service, you can run the RSPRECADMIN tool to configure it – from a GUI on the box you installed the service:

Create service shows this box to fill in:

Maintenance SE38 Report RSRD_BOOKMARK_REORGANIZATIONThe BI precalc service requires that you have MS Excel installed on the server or PC running it.


The last step is to fine tune your instance profiles and database parameters per SAP performance notes…starting with those recommended in the Installation or upgrade manual. This is a list I used mid-2005 for BW 3.5:

NOTES: R3 425207, 103747 (v57 11/30/05), 88416 (v14 6/7/04), 404546 (Performance), 101717 (Process Restart) == BW 184905 (Collective) 192658 (Basis parameters for BW v30 1/20/06) Table Buffers 480710 (v13 12/27/05) resource mgmt trfc 74141 (v65 11/4/05)

Here is an partial example of a tuned instance profile (BW31/Oracle9203/unix – so it is OLD and INCOMPLETE don’t use it!):

#.*************************************************************************#.* *#.* Instance profile BW0_DVEBMGS01_SAPBW0CI *#.* *#.* Version = 000001 *#.* Optimized by user = D.Samuels x28061 *#.* Generated on = 03/11/2004 *#.* *#.* Notes:103747,192658,414220,480710,74141, 146289 and 101717 *#.* BW0 has 4 CPU, 32GB RAM and 40 processes *#.* *#.*************************************************************************

abap/buffersize = 400000abap/heap_area_dia = 2000000000abap/heap_area_nondia = 2000000000abap/heap_area_total = 2000000000abap/heaplimit = 20000000abap/swap_reserve = 20971520abap/timeout = 900abap/use_paging = 0auth/auth_number_in_userbuffer = 9000DIR_DATA = /usr/sap/BW0/DVEBMGS01/dataDIR_PAGING = /usr/sap/BW0/DVEBMGS01/dataDIR_REORG = /usr/sap/BW0/DVEBMGS01/dataDIR_ROLL = /usr/sap/BW0/DVEBMGS01/dataDIR_SORTTMP = /usr/sap/BW0/DVEBMGS01/dataDIR_TEMP = /tmpDIR_TRANS = /usr/sap/transdbs/ora/array_buf_size = 1000000em/blocksize_KB = 4096em/global_area_MB = 255em/initial_size_MB = 8192em/stat_log_size_MB = 20em/stat_log_timeout = 600enque/table_size = 16384exe/j2ee = TRUEgw/cpic_timeout = 60gw/max_conn = 2000gw/max_overflow_size = 25000000icm/HTTP/j2ee_0 = PREFIX=/, HOST=localhost, PORT=33000, CONN=0-20

…etc

CONGRATULATIONS, you have completed all foundational setup steps for your BW system…it is now ready to release to developers…and should not require much attention for a long time.

Dave Samuels, Director, SAP Business Intelligence Practice, myITgroup. C:617-899-1038


Documents

BW35 Post Install steps