SAP Software Provisioning Manager : with screenshots

Posted by Ishteyaque Ahmad Mar 13, 2013

"Have you heard, now sapinst will not be used. All the installation/system copy/uninstallation will be done through this new "thing" SWPM" -- This is what a friend of mine told me.

We were discussing that the moment we settle down with some tool/version or any module, SAP changes it in such a way that we need to re-learn it all over again, which is certainly not a good feeling!

BUT this is not the case this time... so what is SWPM? it is a Master of Master of Master DVD. You don't have to do anything new, just run the sapinst present in the DVD, and you are going to get these all extra options, no more running around for different DVDs for different versions or modules etc, sometimes SAP does good job too . I have done more than 100 installation+system copy with help of these two DVDs and take my word they are just same good old sapinsts minus some bugs.

For any operating system it has two avatars. One DVD for 7.3 and its EHPs and second DVD for rest of non-7.3s. Lets take a look at the screenshots of these two DVDs so that you can have idea what all is out there.

Note 1806601 - SYB Media list for installations based on NW 7.0 incl. EHPs

Note 1806816 - SYB- Media list for installations based on NW 7.3 incl. EHPs

=====================================================================================================

SAP Software Provisioning Manager (SWPM) for SQL Server from Microsoft

My other Blogs, if you have time...

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-I

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-II

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

Escaping tough moments of SPAM or SAINT

Multiple/Bulk transports with tp script for Unix (AIX, Solaris, HP-UX, Linux)

Holistic Basis View: BusinessObjects BI 4.0 SP 2 Installation & Configuration

How to Rename the Oracle Listener & Change Listener port for SAP

OSS1 & RFC connections SAPOSS, SAPNET_RFC, SDCC_OSS

Start/Stop SAP along with your Unix Server Start/Stop

Interrelation: SAP work process, OPS$ mechanism, oracle client & oracle shadow process

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-2

Holistic Basis View: BusinessObjects BI 4.0 SP 2 Installation & Configuration

List of Newly added/converted Dynamic parameter in NetWeaver 7.3

Sunset for ops$ mechanism: No more supported by Oracle & Not Used by SAP

Essential Basis for SAP (ABAP, BW, Functional) Consultants Part-I

Essential Basis for SAP (ABAP, BW, Functional) Consultants Part-II

Essential Basis for SAP (ABAP, BW, Functional) Consultants Part-III

Escaping tough moments of SPAM or SAINT

Posted by Ishteyaque Ahmad Jul 4, 2012

While GRC installation, SAINT & SPAM gave me quite a hard time and this taught me couple of things related to the OCS queue and their cleaning.

Before reaching to the OCS queue cleaning, I am going to describe some of the tips which we should follow before starting work with SPAM/SAINT.

1. Import maintenance certificate for the system (if it's already expired) either through the solution manager or get it from service market place.

2. Update the latest patch of SPAM.

3. Disable archive logs in the case of Oracle.

4. Set maximal number of parallel import processes for one transport requests.

Execute STMS_DOM and double click on the system in which SPAM/SAINT is going to be executed and add a new parameter PARALLEL, its value will decide how many maximal number of parallel import processes for one transport requests will be allowed in a system. For detail please refer SAP Note 1127194 - R3trans import with parallel processes

5. Tweak the setting for parallel Import through SPAM/SAINT

Goto SAINT -> Extras -> Settings

On the tab "Import Queue" put the values for Parallel Import, I generally keep the value for 'Max. Number of Parallel R3trans Processes' equals to total number of CPU on the server. SAP suggest to keep it 4 as initial value. For detail please refer SAP Note 1309506 - SPAM/SAINT with parallel R3trans

To save time, keep the value 'Never' for ABAP/Screen Generation.

OK, lets move to the issues part.

1. Whenever any error comes check SPAM or SAINT logs first

2. Check tp log.

Execute tcode STMS_IMPORT Goto -> tp System Log

3. Check transport import log from STMS_IMPORT, applicable only if transport already started.

OCS queue cleanup:

If you are in the intial stage of SPAM/SAINT and you want to remove the queue and redo it again you can do it, Provided SPAM or SAINT hasn't reached the phase

013	SCHEDULE_RDDIMPDP

One can always keep an eye on the phases and compare it with report SA38 -> RSSPAM10 (SPAM/SAINT: List Import phases by scenario).

This reports describes each phase for SAINT and SPAM.

Lets say we have verified the phase it has not reached SCHEDULE_RDDIMPDP phase and we want to start everything afresh then how to do it?

First try to work with function modules for OCS queue cleanup.

Goto SE37 -> OCS_RESET_QUEUE

You can put tool name as SPAM or SAINT whichever is required and execute.

Another function module is SPAM_RESET_STATUS

If any of the above function module is not helping in cleanup and throwing error the proceed manually.

Goto OS level and identify carefully the data file and the co-file for SAP components involved in SPAM/SAINT. The files present in EPS/in are read and related data file and co-file are extracted to /usr/sap/trans data and cofiles directory. After that, they gets added to import buffer.

Remove or rename data file and co-file for those particular components.

Rename the buffer file, goto /usr/sap/trans/buffer and identify your SID named file and rename it like <SID>.old

Now login to SAP. If its SPAM goto Extra -> Reset status -> Queue

In case of SAINT you just need to click on 'Back' button till it reaches initial screen.

Below are some reports related to SPAM/SAINT, probably not all will be available but you can check in your system and use them when needed.

Name Title

RSSPAM00 Classify Transport Objects for Support Package Systems

RSSPAM02 SPAM: Find Support Package Overshooters in Add-On Upgrade/Installation

RSSPAM03 SPAM: Uploading OCS Packages from file system

RSSPAM05 Support Package Directory

RSSPAM07 SPAM: Queue Status

RSSPAM08 SPAM: Displaying errors during test import

RSSPAM09 SPAM: Display objects locked in requests

RSSPAM10 SPAM/SAINT: List Import phases by scenario

RSSPAM12 SPAM: Determine Conflicts Between Support Packages and Add-Ons

RSSPAM15 SPAM: XPRA for Clearing during SPAM update

RSSPAM17 Reset of processed object lists of the OCS conflict check

RSSPAM18 Displaying Open Conversion Requests in the Data Dictionary

RSSPAM19 Display the Open V3 Update and Data Extraction Requests

RSSPAM22 Display required note corrections

RSSPAM23 Display the TMS transport requests which should be imported before

RSSPAM30 Execution of OCS Package Import

My other Blogs, if you have time...

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-I

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-II

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

Multiple/Bulk transports with tp script for Unix (AIX, Solaris, HP-UX, Linux)

Holistic Basis View: BusinessObjects BI 4.0 SP 2 Installation & Configuration

How to Rename the Oracle Listener & Change Listener port for SAP

OSS1 & RFC connections SAPOSS, SAPNET_RFC, SDCC_OSS

Interrelation: SAP work process, OPS$ mechanism, oracle client & oracle shadow process

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-2

Holistic Basis View: BusinessObjects BI 4.0 SP 2 Installation & Configuration

List of Newly added/converted Dynamic parameter in NetWeaver 7.3

Holistic Basis View: BusinessObjects BI 4.0 SP 2 Installation & Configuration

Posted by Ishteyaque Ahmad Jun 12, 2012

Those who wish to install and configure SAP BusinessObjects Business Intelligence platform 4.0 Support Package 2 or other versions, some basic questions come to their mind like

Question 1 : Will there be any separate SID for BObj?

Question 2 : Will it have its separate Database?

Question 3 : Will it be installed like normal SAP systems with sapinst?

Even if you know answers, but you want to understand the installation flow or you need bit more detail on deployment process...

My intention is to cover these points right here in this blog.

Simultaneously I am also assuming that readers will or already gone through the latest installation guide as well.

Question 1 : Will there be any separate SID for BObj?

It will not like SAP SID but you have to give name to the Node example is in above figure.

Question 2 : Will it have its separate Database?

Yes, you need an already install database and you need to create 2 schema and tablespace for data and temporary tablespace for each schema. BObj installation will not install any database on its own but it will ask you to connect with existing one.

Question 3 : Will it be installed like normal SAP systems with sapinst?

No, The installation will not be done through sapinst, it will be done through script in Unix, Its more like brtools or if you done ccms agent registration from OS where it provide you text based menu/options and you input your options. For windows there will be wizard which will ask for same set of menu/options, like normal software installation in windows.

By looking at above figure, one more question may arise:

Question 4 : Lets say if we use NetWeaver Java then where we need to create the User IDfor BObj?

The WebServer Tomcat or NetWeaver Java will only be used to host the interface or as frontend. All the User ID and password will be created inside BObj Box.... in default scenario like below where authentication is "Enterprise". Here SAP can be selected also but in that case we need to create alias for each User ID and that will be searched. We will discuss it further after end of installation phase.

Installation flow:

Oracle Database preparation

You need to prepare one pre-installed Oracle database. You can use your existing oracle database used for any of your SAP system, there we need to create two schemas and their tablespaces. Do not worry about space needed for these extra tablespaces, The size of tablespaces after my installation was not more than 30MB each. But please select that DB where you can afford much more space than that.

Lets see how to do it.

For the simplicity of this blog, lets decide the name of those two schema names orabo4 and audbo4.

Create a orabo4 tablespace and a temporary tablespace bo4temp

Now create schema user orabo4 and grant it access like below.

We can check if it is working fine or not like below

Similarly we will create tablespace bo4aud, temporary tablespace audtemp and a schema user bo4aud.

Note: There is no restriction on selecting the schema name tablespace name but for some unknown reason, I try to keep it like SAP naming conventions.

When this is done, we are good to go for next step

Business Object Installation

To keep this blog short, I have kept the screenshots for installation phase in below locations. Please follow the link to view the step by step screenshots.

When you go through the screenshots, specially watch out for these 3 screens.

BObj Node name
How to connect with oracle
There was an oracle error & its simple solution

Create an OS User for Admin, in our case we have got bobadm user, login with this ID and start script as shown in below links.

Screenshots : BusinessObjects BI 4.0 SP 2 Installation part-1

Screenshots : BusinessObjects BI 4.0 SP 2 Installation part-2

Business Object deploy-able files generation

Now the installation of BObj is done, its time to deploy these installed components on WebServer or NetWeaver Java, in this example we have used NetWeaver Java so we will proceed with this in this blog.

To do this first we have to create deploy-able files on the server where we have installed the BObj.

When we will get those files then we will move them on the server where our NetWeaver Java is installed.

If you have noticed last two screens of installation it tells the path from where we have to start the wdeploy.sh script in our case it is.

/usr/sap/BOB/sap_bobj/enterprise_xi40/wdeploy

Login with bobadm on BObj server, goto the specified location of wdeploy.sh and check installed component with the command

./wdeploy.sh sapappsvr73 listapps

Here sapappsvr73 is parameter because we are going to use NetWeaver7.3, detail you can get in Installation guide

It will provide details of all the installed components.

With this command it will create deploy-able files

./wdeploy.sh sapappsvr73 predeployall

For me it took around 12 minutes to generate those files.

if you will watch the screen you will find the location where files were getting created, which was at location

/usr/sap/BOB/sap_bobj/enterprise_xi40/wdeploy/workdir/sapappsvr73/application/

Business Object deployment on NetWeaver Java

Copied the directory /usr/sap/BOB/sap_bobj/enterprise_xi40/wdeploy present on BObj Server.

to my NetWeaver AS Java lets say its SID is NW3

/usr/sap/NW3/sap_bobj/enterprise_xi40/wdeploy

This means I created sap_bobj/enterprise_xi40 directory inside /usr/sap/<SID> and copied entire content of wdeploy directory there.

Login with nw3adm user at OS level and goto location /usr/sap/NW3/sap_bobj/enterprise_xi40/wdeploy

We also require Web application server administrative account password, lets say its T3ch#312 then execute below command

./wdeploy.sh sapappsvr73 -Das_admin_password=T3ch#312 deployonlyall

This will deploy all the components for NetWeaver AS Java.

But if your system is NW7.3 then it will not succeed for all components. You need to copy the .sca file present at location

sap_bobj/enterprise_xi40/wdeploy/workdir/sapappsvr73/application/

and copy them to inbox of Trans directory /usr/sap/trans/EPS/in/

Set your display and start JSPM, select this option

and proceed next

This way you can deploy your remaining components.

Now you are ready to go with these two links.

http://<hostname>:5<nn>00/BOE/CMC

http://<hostname>:5<nn>00/BOE/BI

After login to CMC you can get screen like below which will open door for you to configure.

From this screen click on "OLAP Connection" and create new connection to any SAP BW system.

By clicking on Authenticatin you can select the type of authentication is needed

By selecting SAP you can also import users and roles from SAP system as well.

This was the brief overview for BObj BW 4.0. Hope it will give some idea to those who have never worked with BObj earlier.

My other Blogs, if you have time...

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-I

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-II

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

Multiple/Bulk transports with tp script for Unix (AIX, Solaris, HP-UX, Linux)

Holistic Basis View: BusinessObjects BI 4.0 SP 2 Installation & Configuration

How to Rename the Oracle Listener & Change Listener port for SAP

OSS1 & RFC connections SAPOSS, SAPNET_RFC, SDCC_OSS

Interrelation: SAP work process, OPS$ mechanism, oracle client & oracle shadow process

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-2

List of Newly added/converted Dynamic parameter in NetWeaver 7.3

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-II

Posted by Ishteyaque Ahmad May 22, 2012

This is the continuation of blog What's new in SAP NetWeaver 7.3 - A Basis perspective Part-I

13. SAP JVM

In our earlier installation of SAP we need to install jdk or sapjvm before we start with sapinst. But with NW7.3 its not needed any more. SAPInst will install required sapjvm6 on its own, though you can provide the path of latest version of sapjvm6 downloaded from service market place.

Benefits of sapjvm :The SAP JVM provides comprehensive statistics about threads, memory consumptions, garbage collections and I/O activities. This information is visualized in the monitoring and management tools provided with the SAP NetWeaver Application Server Java. For solving issues with SAP JVM, several traces may be enabled on demand. They provide additional information and insight into integral VM parts like the class loading system, the garbage collection algorithms and I/O.

Patching the SAP JVM on an SAP NetWeaver system is only supported using the Java Support Package Manager (JSPM) but there is issue with patching SAPJVM6 through JSPM for distributed system JSPM tries to start PAS and DB for SAPJVM deployment, but its not able to do so because they are on different servers and it gives error.

In that case we can do manuall patching like below first modify Instance profile parameters for JVM 6

_CPARG0 = list:$(DIR_CT_SAPJVM)/sapjvm_6.lst

_CPARG1 = source:$(DIR_CT_SAPJVM)

SAPJVM_VERSION = 6.1.032

DIR_SAPJVM = $(DIR_EXECUTABLE)$(DIR_SEP)sapjvm_6

jstartup/vm/home = $(DIR_SAPJVM)

Then uncar sapjvm6 and keep it at location of jvm directory, there will be variation in directory name as per your OS. If you are not using PI or Java then this directory structure may not present and upgrade is not needed in that case.

14. SUM : Software Update Manager
The Software Update Manager is a multi-purpose tool, which supports various procedures, such as installing enhancement packages or applying Support Package Stacks

SAPehpi 7.10 is replaced by Software Update Manager:
The SAP Enhancement Package Installer (SAPehpi), which was used until now to install Enhancement Package 1 for SAP NetWeaver PI / MOBILE / ABAP 7.1, is replaced by the Software Update Manager (SUM).

Use Software Update Manager 1.0 SP02 for the following processes:

Upgrading to SAP NetWeaver 7.3
Applying Support Packages Stacks
Installing enhancement packages

Install SUM
SAPCAR -xvf /<directory>/SUM10SP02_9-20006543.SAR -R /usr/sap/<SAPSID>

Start SUM
With sid<adm> on Primary Application Server
> /usr/sap/<SID>/SUM/sdt/exe/DSUGui

Please take a glimpse of this tool it will remind you of SAP version upgrade and Ehp ugrade tool !

For detail please check SAP Note 1557404 - Central Note - Software Update Manager

15. CUA and IDM

SAP NetWeaver 7.3 AS Java fully supports the latest security standards, such as the SAML 2.0 protocol.

In SAP NetWeaver 7.3, CUA (Central User Administration) is now completely replaced by SAP NetWeaver Identity Management. But this does not mean that NW7.3 will not support CUA, you can still use it like previous version, in fact I am also using CUA with my NW7.3 so far its not complaining

Below is typical IdM landscape for your reference.

16. Dynamic Profile Parameters

To make it more dynamic and reduce downtime, from NetWeaver 7.3 some of the well-known system parameters have been “dynamized” — the parameters do not require a system restart after changes are made.

You can get a list of those parameters at this link

List of Newly added/converted Dynamic parameter in NetWeaver 7.3

17. Dynamic work processes

Probably this feature has been introduced from NetWeaver 7.0 Ehp 1, but still this is not frequently used and NetWeaver 7.3 favours/promotes majorly the concept of dynamic behaviour so I wanted to make it a separate point. Here we can increase total number of work processed without restarting SAP system, its different than what we do through RZ04. There no point me discussing it here when SAP has itself described it beautifully, please go throught the link

http://help.sap.com/saphelp_nwpi71/helpdata/en/46/c24a5fb8db0e5be10000000a1553f7/content.htm

18. ABAP Soft Shutdown

Like different option present in case of Oracle Database, now from NW7.02 to NW7.3 has got the additional option of Soft Shutdown of ABAP. There are various option possible with help of these parameters.

rdisp/shutdown/disable_gui_login - This parameter will suppress GUI logons during the shutdown. This applies irrespective of user roles or authorizations
rdisp/shutdown/gui_auto_logout - Defines the period for which dialog users can be inactive during the kernel shutdown, before they are automatically logged off. If greater value than 0 will be used, the maximum wait time is calculated from the minimum of the parameters rdisp/gui_auto_logout and rdisp/shutdown/gui_auto_logout.
rdisp/shutdown/idle_wp_timeout - How long the kernel shutdown waits for all work processes to be in the status "waiting".
rdisp/shutdown/message_frequency - How frequently dialog users are requested to log off during the server shutdown.
rdisp/shutdown/j2ee_timeout - How long the kernel shutdown waits for the AS Java (JEE Engine) to shutdown.
rdisp/shutdown/load_balance_wait_time - How long the kernel shutdown waits for the server to be deleted from the load balance information. During this time, all requests can continue to be processed.
rdisp/shutdown/abap_trigger_timeout - Defines how long the kernel shutdown waits for the shutdown trigger to be read by the Auto ABAP.

The Soft Shutdown option is available from SAP transaction SM51 and with help of SAP MMC

SAP MMC : From Web Browser -> http://<hostname>:5nn13

Right click on instance which needs to be shutdown and Click on Shutdown or restart

19. SSO2 Wizard is more powerful

Now from NetWeaver 7.3 there is no need to use STRUSTSSO2 and NWA certificate link unless you wish to use them to import export certificates.

Please go through this blog for details

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

20. NetWeaver 7.3 on Cloud

With release of NetWeaver 7.3 SAP is now more focusing on future cloud integration, mobility and in-memory computing tasks.

As if now, these NW7.3 hubs are available on Cloud.

SAP Enterprise Portal 7.3
SAP BW NetWeaver 7.3
SAP PI NetWeaver 7.3
HANA

For reference please visit below links

http://www.sap.com/corporate-en/press.epx?pressid=15178

http://www.sapcloudcomputing.com/technology/architecture.html

http://www.wftcloud.com/

With these 20 points I would like to wind up this blog, but I will appriciate if readers suggest more points which they know but we should stick to the Basis perspective

Hope this will be of help to some of us.

----------------Adding this point as suggested by Hemanth Kumar Jul 10, 2012----------------

21. From NetWeaver7.1 sap introduced new tool in place of JCMON. This tool is JSMON

This can be used just like jcmon.

jsmon pf=<instance profile name>

you can type help and get multiple options that can be used, like below screenshot you can type instance, process, display and see the result.

My other Blogs, if you have time...

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

Escaping tough moments of SPAM or SAINT

Multiple/Bulk transports with tp script for Unix (AIX, Solaris, HP-UX, Linux)

Holistic Basis View: BusinessObjects BI 4.0 SP 2 Installation & Configuration

How to Rename the Oracle Listener & Change Listener port for SAP

OSS1 & RFC connections SAPOSS, SAPNET_RFC, SDCC_OSS

Interrelation: SAP work process, OPS$ mechanism, oracle client & oracle shadow process

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-2

Holistic Basis View: BusinessObjects BI 4.0 SP 2 Installation & Configuration

List of Newly added/converted Dynamic parameter in NetWeaver 7.3

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-I

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-II

List of Newly added/converted Dynamic parameter in NetWeaver 7.3

Posted by Ishteyaque Ahmad May 22, 2012

This list is not published by SAP, I have pulled out this list from SAP system and did comparision with various versions, so this list should not be taken as official list but as a rough reference.

Unchanged Dynamic Profile	Newly added/converted Dynamic parameter	Old/Earlier Dynamic parameter no more Dynamic
abap/atra_split_trace_file	abap/aciinternal	abap/enable_ro_check
abap/deferred_generation	abap/apg_settings	abap/oo_warn
abap/list/listparser	abap/compile_mult_pass	vmcj/debug_proxy/cfg/defaultPort
abap/list/printQuickInfos	abap/comp_diagnostic	vmcj/debug_proxy/cfg/waitTimeout
abap/objmgr/nodeletemode	abap/hotspot_trace	sapgui/user_scripting_disable_recording
abap/string_sharing	abap/package_check	gw/auto_disconnect
abap/swap_reserve	abap/package_check_exceptions	gw/cpic_security
abap/table_sharing	abap/parallelism	gw/gwwp_connect_timeout
abap/warn2error_release	abap/rabax_no_debug	gw/gwwp_long_polling_time
abap/activate_precompiled_header	abap/maximal_defenv_size	gw/gwwp_restart
auth/authorization_trace	dbs/dba/ccms_security_level	gw/gwwp_short_polling_time
auth/new_buffering	dbs/syb/par_stmt_prepare	gw/ims_max_send_length
bdc/bdel_auth_check	dbs/syb/sql_trace	gw/ims_signon
bgrfc/context_check/auth_check	DIR_CT_SAPJVM	gw/ims_signon_cmd
bgrfc/disable_integrity_check	eg2/max_extend_size_MB	gw/keep_process
bgrfc/extern/auth_check	EM/TOTAL_SIZE_MB	gw/max_conn_per_wp
bgrfc/loadbalancing/auth_check	enque/delay_max	gw/max_shm_req_per_conn
bgrfc/supportability/auth_check	enque/deque_wait_answer	gw/max_short_poll_no
icf/accept_client_profile_level	FN_EXTRACT	gw/nibuf_retry
icf/accept_remote_profile_level	gw/accept_timeout	gw/non_conversational
csi/enable	gw/acl_mode	gw/receive_immediate
dbs/db2/cli_trace	gw/autoreload	gw/tcp_security
dbs/db2/icli_client_trace	gw/frag_timeout	icm/HTTPS/verify_client
dbs/db2/sql_trace	gw/logging	vmcj/debug_proxy/cfg/listenport
dbs/db4/dbsl_alternate_package	gw/ni_dns_trc_limit	vmcj/debug_proxy/cfg/strat_jars
dbs/db4/dbsl_trace	gw/req_stack_size	mdm/network_timeout
dbs/db6/ccms_maintenance	gw/start_in_homedir	rdisp/bufreftime
dbs/db6/dbsl_cli_trace	http/security_session_timeout	rdisp/context_pool_size
dbs/db6/dbsl_cstrace	icf/set_HTTPonly_flag_on_cookies	rdisp/plugin_pool_timeout
dbs/db6/dbsl_trace	icm/failover_timeout	rdisp/plugin_server_pooling
dbs/db6/dbsl_trace_iocount	icm/HTTP/max_request_size_KB	rdisp/rfc_pool_size
dbs/db6/dbsl_trace_string	icm/HTTP/request_timer	rdisp/rfc_pool_timeout
dbs/db6/dbsl_trace_str_len	icm/IIOP/max_request_size_KB	rdisp/rfc_server_pooling
dbs/db6/dbsl_trace_time	icm/P4/max_request_size_KB	SRZL_WPNO_BTC_A
dbs/mss/dbsl_profile	icm/trace_secured_data	stat/correct_processing_time
dbs/mss/par_stmt_prepare	icm/wp_roll_timeout	vmcj/inline_lock_loops
dbs/mss/stats_on	is/hostbuffer_timeout_invalid_entry	vmcj/rollout_lock_loops
dbs/mss/update_with_updlock	is/hostbuffer_timeout_valid_entry
DIR_MEMORY_INSPECTOR	itsp/Security/allow_designs_from
DIR_PUT	login/certificate_mapping_rulebased
rdisp/accept_remote_trace_level	login/password_hash_algorithm
rdisp/vb_delete_after_execution	ms/extbnd_port
login/password_compliance_to_current_policy	ms/http_proctime
em/stat_log_size_MB	ms/sapevt_lb
em/stat_log_timeout	rbam/active
enque/async_req_max	rbam/trace_level
enque/backup_disabled	rdisp/acl_file
enque/con_retries	rdisp/addump_period
enque/con_timeout	rdisp/allow_block_softcancel
enque/delay_jitter	rdisp/avoidTraceInSigHandler
enque/delay_log_level	rdisp/calculateLoadAverage
enque/delay_log_time	rdisp/commTableCheck
enque/delay_max_refine	rdisp/configurable_wp_no
enque/log_file	rdisp/convert_old_epp_recs
enque/snapshot_timeout	rdisp/dev_loop
enque/top_list_length	rdisp/dynamic_wp_check
enque/use_pfclock2	rdisp/ext_timer_stop_delay
exe/j2ee	rdisp/fileTableCheck
icf/accept_client_recorder_level	rdisp/maxAppcBlocksInQueue
icf/accept_remote_recorder_level	rdisp/maxWpBlocksInQueue
gw/accept_remote_trace_level	rdisp/max_cs_delays
gw/close_routes	rdisp/max_dynamic_wp_alive_time
gw/compatibility	rdisp/max_vm_debug_attach_time
gw/conn_disconnect	rdisp/max_vm_priv_no
gw/conn_pending	rdisp/max_vm_priv_time
gw/cpic_timeout	rdisp/max_vm_sgc_lazy_time
gw/deallocate_timeout	rdisp/queue_size_check_value
gw/export_trace_level	rdisp/sessionTableCheck
gw/external_trace_level	rdisp/shutdown/abap_trigger_timeout
gw/gw_disconnect	rdisp/shutdown/disable_gui_login
gw/internal_timeout	rdisp/shutdown/gui_auto_logout
gw/keepalive	rdisp/shutdown/idle_wp_timeout
gw/local_addr	rdisp/shutdown/j2ee_timeout
gw/max_overflow_size	rdisp/shutdown/load_balance_wait_time
gw/max_overflow_usage	rdisp/shutdown/message_frequency
gw/max_sleep	rdisp/tableCheck
gw/monitor	rdisp/tableCheckMode
gw/nibuf_max	rdisp/traffic_control
gw/nifragtest	rdisp/use_sqlbreak
gw/nitrace	rdisp/vb_dequeue_after_commit_error
gw/reg_keepalive	rdisp/vmc_timeout_prio
gw/reg_lb_default	rsdb/trace_modules
gw/reg_lb_ip	sapgui/user_scripting_disable_recording
gw/reg_lb_level	SAPJVM_VERSION
gw/reg_timeout	slic/activate_server
gw/rem_start	slic/high_available
gw/resolve_timeout	stat/externalize/enabled
gw/so_keepalive	stat/externalize/regdir
gw/stat	vmcj/cloning
gw/timeout	vmcj/debug_proxy/cfg/allowedPorts
gw/use_udp	vmcj/debug_proxy/cfg/defaultPort
icf/option_list	vmcj/debug_proxy/cfg/listenport
icf/shared_memory_cache_off	vmcj/debug_proxy/cfg/strategy_jars
icf/user_recheck	vmcj/debug_proxy/cfg/waitTimeout
icm/accept_remote_trace_level	vmcj/dynamic_options
icm/ccms_monitoring	vmcj/guard_page_num
icm/ccms_refresh_rate	vmcj/keepAutoJavaVm
icm/conn_timeout	vmcj/max_error_count
icm/HTTP/context_quota	vmcj/max_sgc_exceed_count
icm/HTTPS/context_quota	vmcj/max_vm_heap_MB
icm/log_level	vmcj/option/jit/sharedCodeCacheSize
icm/SMTP/context_quota	vmcj/option/maxJavaHeap
is/HTTP/default_root_hdl	vmcj/option/percentageCopyOnlySC
is/HTTP/show_detailed_errors	vmcj/option/percentageSharedClasses
is/HTTP/show_server_header	vmcj/option/ps
is/HTTP/virt_host_0	vmcj/option/ss
is/HTTP/virt_host_1	vmcj/option/traceThreadId
is/HTTP/virt_host_2	vmcj/option/traceVmId
is/HTTP/virt_host_3	vmcj/property/APP.REPOSITORIES
is/HTTP/virt_host_4	vmcj/property/java.io.tmpdir
is/HTTP/virt_host_5	vmcj/restrictedPackage_0
is/HTTP/virt_host_6	vmcj/restrictedPackage_1
is/HTTP/virt_host_7	vmcj/restrictedPackage_2
is/HTTP/virt_host_8	vmcj/restrictedPackage_3
is/HTTP/virt_host_9	vmcj/restrictedPackage_4
is/SMTP/virt_host_0	vmcj/restrictedPackage_5
is/SMTP/virt_host_1	vmcj/restrictedPackage_6
is/SMTP/virt_host_2	vmcj/restrictedPackage_7
is/SMTP/virt_host_3	vmcj/restrictedPackage_8
is/SMTP/virt_host_4	vmcj/restrictedPackage_9
is/SMTP/virt_host_5	vmcj/write_core
is/SMTP/virt_host_6	wdisp/HTTP/context_timeout
is/SMTP/virt_host_7	wdisp/HTTPS/context_timeout
is/SMTP/virt_host_8
is/SMTP/virt_host_9
itsp/cachecontrol/maxage
itsp/devmode/contextdump
itsp/ignorefromurl
itsp/max_eg_mem_percent
itsp/memory_check
itsp/startokcode
itsp/Traces/SAPagi/TraceLevel
itsp/Traces/SAPalvgrid/TraceLevel
itsp/Traces/SAPdiag/TraceLevel
itsp/Traces/SAPdp/TraceLevel
itsp/Traces/SAPxgdk/TraceLevel
vmcj/debug_proxy/cfg/allowedPorts
javascript/FrameStack
javascript/Options
javascript/RuntimeHeap
javascript/TraceLevel
login/accept_sso2_ticket
login/create_sso2_ticket
login/password_change_for_SSO
login/password_charset
login/ticket_only_by_https
login/ticket_only_to_host
login/update_logon_timestamp
ms/admin_port
ms/audit
ms/comment
ms/conn_timeout
ms/domain_max_delay
ms/domain_max_try
ms/http_bufferln
ms/http_domain
ms/http_enable_handler
ms/http_logging
ms/http_lookup
ms/http_timeout
ms/http_was_required
ms/icf_info_server
ms/keepalive
ms/max_sleep
ms/max_vhost
ms/monitor
ms/nitrace
ms/redirect_version
ms/timeout
nobuf/max_attempts
nobuf/server
rdisp/no_rfc_commit_in_update_task
rdisp/async_dialog_timeout
rdisp/autoabaptime
rdisp/autoabapuser
rdisp/autojavatime
rdisp/autothtime
rdisp/auto_vb_stop
rdisp/btctime
rdisp/call_system
rdisp/debug_jvm_startup
rdisp/delayed_call_interval
rdisp/gui_auto_logout
rdisp/http_check
rdisp/http_min_wait_dia_wp
rdisp/j2ee_error
rdisp/j2ee_libpath
rdisp/j2ee_profile
rdisp/j2ee_start
rdisp/j2ee_start_control
rdisp/j2ee_start_lazy
rdisp/j2ee_timeout
rdisp/jvm_pool_timeout
rdisp/keepalive
rdisp/keepalive_old
rdisp/keepalive_timeout
rdisp/max_alt_modes
rdisp/max_cmdrun_time
rdisp/max_debug_lazy_time
rdisp/max_hold_time
rdisp/max_jvm
rdisp/max_priv_time
rdisp/max_sleep
rdisp/max_snc_hold_time
rdisp/max_vm_forced_sgc_time
rdisp/max_wprun_time
rdisp/min_jvm
rdisp/ms_keepalive
rdisp/ms_keepalive_timeout
rdisp/noptime
rdisp/no_core_info
rdisp/no_statistic
rdisp/plugin_auto_logout
rdisp/reinitialize_code_page
rdisp/restartable_wp
rdisp/reverse_name_lookup
rdisp/rfc_check
rdisp/rfc_max_comm_entries
rdisp/rfc_max_login
rdisp/rfc_max_own_login
rdisp/rfc_max_own_used_wp
rdisp/rfc_max_queue
rdisp/rfc_max_wait_time
rdisp/rfc_min_wait_dia_wp
rdisp/rfc_use_quotas
rdisp/rm_max_tbl_size
rdisp/sna_gateway
rdisp/sna_gw_service
rdisp/softcancel_sequence
rdisp/softcancel_timeout
rdisp/spooltime
rdisp/start_icman
rdisp/test_roll
rdisp/time_intervals
rdisp/TRACE
rdisp/TRACE_HIDE_SEC_DATA
rdisp/TRACE_LOGGING
rdisp/TRACE_PATTERN_0
rdisp/TRACE_PATTERN_1
rdisp/TRACE_PATTERN_2
rdisp/TRACE_RESOLUTION
rdisp/TRACE_SEARCH_LIST
rdisp/update_max_attempt_no
rdisp/use_rfc_dest_lookup
rdisp/vbmail
rdisp/vb_auto_sync
rdisp/vb_lock_mode
rdisp/vb_mail_user_list
rdisp/vb_stop_active
rdisp/vb_v2_auto_sync
rdisp/verbose_level
rdisp/vm_alarm_time
rdisp/wait_after_deadlock
rdisp/wpdbug_max_no
rdisp/wppriv_max_no
rdisp/wp_abap_restart
rdisp/wp_auto_restart
rdisp/wp_restart_interval
rfc/cp_convert/conversion_char
rfc/cp_convert/ignore_error
rfc/ext_debugging
rfc/option_list
rfc/prefer_rfcdes
rfc/reduce_tracelevel
rfc/set_standard_destination
rfc/signon_error_log
rscp/mbc_copy
rsdb/max_blocking_factor
rsdb/max_in_blocking_factor
rsdb/min_blocking_factor
rsdb/min_in_blocking_factor
rsdb/prefer_fix_blocking
rsdb/prefer_in_itab_opt
rsdb/prefer_join
rsdb/prefer_union_all
rsdb/rclu/opt_level
rsec/securestorage/keyfile
rstr/accept_remote_trace
rstr/buffer_size_kB
rstr/max_filesize_MB
rstr/max_lock_try
rstr/stacksize
dbs/db6/dbsl_trace_deadlock_time
sapgui/theme
sapgui/user_scripting
sapgui/user_scripting_force_notification
sapgui/user_scripting_per_user
sds/comment
sec/dsakeylengthdefault
sec/rsakeylengthdefault
itsp/Traces/SAPplugin/TraceLevel
login/password_downwards_compatibility
stat/checks
itsp/Traces/SAPautom/TraceLevel
itsp/Traces/SAPjulep/TraceLevel
sapgui/user_scripting_set_readonly
vmcj/asyncCompilation
vmcj/debug_proxy/cfg/fileName
vmcj/debug_proxy/cfg/generate
vmcj/debug_proxy/cfg/loglevel
vmcj/debug_proxy/cfg/msHost
vmcj/debug_proxy/cfg/msPort
vmcj/debug_proxy/param_0
vmcj/debug_proxy/param_1
vmcj/debug_proxy/param_2
vmcj/debug_proxy/param_3
vmcj/debug_proxy/param_4
vmcj/debug_proxy/param_5
vmcj/debug_proxy/param_6
vmcj/debug_proxy/param_7
vmcj/debug_proxy/param_8
vmcj/debug_proxy/param_9
vmcj/debug_proxy/port
vmcj/jni_strategy
vmcj/max_inline_sleeps
vmcj/nested_lock_loops
vmcj/option/debugPortRange
vmcj/option/gc/sharedWaterMark
vmcj/prof/directory
vmcj/prof/maxAge
vmcj/sgc_options
vmcj/TRACE_1
vmcj/TRACE_2
vmcj/TRACE_3
vmcj/vm_auto_restart
vmcj/vm_shared_lock_statistics
vmcj/waitForVmTime
zdate/DSTswitch_contloctime
ztta/cua_area
ztta/diag_area
ztta/dynpro_area

My other Blogs, if you have time...

How to Rename the Oracle Listener & Change Listener port for SAP

Multiple/Bulk transports with tp script for Unix (AIX, Solaris, HP-UX, Linux)

OSS1 & RFC connections SAPOSS, SAPNET_RFC, SDCC_OSS

Interrelation: SAP work process, OPS$ mechanism, oracle client & oracle shadow process

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-2

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-I

Posted by Ishteyaque Ahmad May 22, 2012

There are various materials present about features of SAP NetWeaver 7.3 but not all of them are directly useful for Basis people like us. So I thought to collect some of differences/features which I noticed.

I know some folks will say that not all features are introduced in 7.3 some of them were introduced in 7.1 and 7.2, but I am a greedy man and I wanted to increase number of features in this blog so I included them as well. Beside it will be helpful to those who haven't got chance to work with 7.1 or 7.2 and directly started working with 7.3.

So lets begin...

1. SAP NetWeaver 7.3 Goes Green

With NW7.3 you can save more energy from architectural perspective, you can get details of it here, I find it interesting.

http://scn.sap.com/community/sustainability/green-it/blog/2011/06/06/sap-netweaver-73-goes-green

2. SAP NetWeaver 7.3 – Lean Avatar

In the process integration, a Java-only, lightweight advanced adapter engine is now available for NetWeaver 7.3, eliminating the need to run SAP NetWeaver Process Integration (SAP NetWeaver PI) as a dual stack.
From SAP NetWeaver 7.30, customers can reduce their hardware needs as a result of common deployment options for all Java usage types, including enterprise portals, SAP NetWeaver BW, and SAP NetWeaver Composition Environment (SAP NetWeaver CE), with one unified Java application server.
NetWeaver Portal 7.3 uses half as much memory on average to execute navigations.
NetWeaver Portal 7.3 server node starts up much faster than 7.01, with improvement of 33% in average.

3. Instances Naming convention

As of SAP NetWeaver 7.1, the concept and naming of SAP system instances has changed. The terms “central instance” and “dialog instance” are no longer used. Instead, the SAP system consists of the following instances:

Application server instances

Application server instances can be installed as “primary application server instance” (PAS) or “additional application server instances” (AAS).

Central services instance
Database instance

4. The Central Services Instance ABAP - ASCS

The central services instance for ABAP (ASCS instance) is now installed with every SAP ABAP system distribution option:

❶ Standard System ❷ Distributed System ❸High-Availability System

The enqueue replication server instance (ERS instance) can now be installed together with the central services instance for every installation :

Standard System (optional)
Distributed System (optional)
High-Availability System (mandatory)

At the time of SCS installation if we can select the above option it will install ERS instance as well.

Though I am such a naive person who is failed to understand the purpose of having ERS instance on same host where we are having Enqueue server.

5. The Central Services Instance ABAP - ASCS

With new Installation Master for ABAP+Java, SAPInst does not provide option for separate ASCS and SCS Instance. Though it can be separated manually after installation on different host.

6. Split Off ASCS Instance

SAPInst now has an option to "Split Off ASCS Instance"

With the option Split Off ASCS Instance from Existing Primary Application Server Instance, you can split off an central services instance for ABAP (ASCS instance) from the primary application server instance of an existing ABAP system or ABAP+Java (dual-stack) system.

7. Solution Manager Key

As of SAP NetWeaver 7.3, Solution-Manager-Key at the time of Installation is not asked/required by SAPInst.

Even in previous installation people found out the way to generate the Solution Manager Key out of SolMan System.

http://kohanov.com/tmp/sap_keys.vbs

8. Start Profile Merged

As of SAP NetWeaver 7.3, Start Profile has been removed as separate file.

In earlier versions of NetWeaver there were 1 Default profile per SAP system, 1 Start profile per Instance and 1 Instance profile per instance.

Now the Start profile contents are merged with Instance profile. With help of new Instance profile SAP processes are started and at the same time instance specific parameters are read.

This removed total number of profile files. 1 Default profile per SAP System, 1 instance profile per instance.

Now Profile Directory will look neater !!

9. JSPM (Java Support Package Manager) Initial credential requirement changed

While starting JSPM – SDM password is not being prompted, Instead you need to provide Java Admin User ID and password.

While deploying and upgrading components it needs restart of just Java and sometime complete SAP restart, for which Admin User ID at OS level and its password is asked.

SDM is replaced with JSPM and directory SDM is altogether removed.

Un-deployment of SCA’s/EAR files are not possible using JSPM. You have to use NWDI for this purpose.
No support for PAR files. All portal applications are now EAR (Enterprise Archive) based, PAR migration tool for converting PAR files to EAR files

10. JCMON changed menu

After NetWeaver 7.01 JCMON menu 20: Local Administration Menu is non functional.

Select opton Solid Rock .... name is funny I mean Rocks are solid anyway

and you will able to see which state of different components/nodes. Unlike previous version I didn't find refresh option here, so go back and come to this menu again for recent view.

11. Visual Admin Vs NWA

As of SAP NetWeaver 7.1, Visual Admin has been replaced with NWA

12. Support Pack Stack

Earlier in NetWeaver 7.0, For a Support Pack Stack the release level of BW component was generally 2 release ahead of the ABAP and Basis component.

Now all components are released on same level.

Please continue with second part of this blog.

What's new in SAP NetWeaver 7.3 - A Basis perspective Part-II

My other Blogs, if you have time...

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

Escaping tough moments of SPAM or SAINT

SAP Software Provisioning Manager : with screenshots

Multiple/Bulk transports with tp script for Unix (AIX, Solaris, HP-UX, Linux)

Script for deleting files within a directory structure with different retention days

Holistic Basis View: BusinessObjects BI 4.0 SP 2 Installation & Configuration

How to Rename the Oracle Listener & Change Listener port for SAP

OSS1 & RFC connections SAPOSS, SAPNET_RFC, SDCC_OSS

Start/Stop SAP along with your Unix Server Start/Stop

Interrelation: SAP work process, OPS$ mechanism, oracle client & oracle shadow process

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-2

List of Newly added/converted Dynamic parameter in NetWeaver 7.3

Sunset for ops$ mechanism: No more supported by Oracle & Not Used by SAP

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

Posted by Ishteyaque Ahmad May 14, 2012

It is time to enjoy for those who have NetWeaver 7.3 Java in their landscape or somewhere else provide from that Java system you can jump to any of your systems in landscape and firewall will not stop you from login.

If answer is yes then you can avoid use of STRUSTSSO2 and Java nwa license link to import-export certificates.

From just one NW7.3 Java system you can exchange certificate between between any two

Java <--> Java

ABAP <--> Java

ABAP <--> ABAP

without downloading and uploading of certificate files and with just few mouse clicks, what else you need in life?

SSO2 Wizard was introduced for AS Java 640: SP21 & for AS Java 700: SP14 that can be accessed through URL http://<hostname>:5nn00/sso2

If you are having older SP levels than the mentioned above then you can deploy it from SAP Note 1083421 - SSO2 Wizard

After login, screen it will look like below

check the information marked in green

It will show the SID, client of Java, which is needed in order to work with SSO certificates.

You can notice that there are 3 certificates applied, you can see their SID and client as well, in the example the system with client number 007 is Java and rest two systems are ABAP.

If you want to add more systems you have two methods:

By Querying Trusted System
By Uploading Certificate Manually (old method needed file download and upload)

We will checkout easy method : By Querying Trusted System

It will prompt you for searching system from SLD, you can select it from SLD list else you can cancel it and come to below screen.

select the system type, for example I am selecting JAVA

Fill the hostname or IP, Port number like 5NN00 where NN is instance number. Click Next

Wizard will automatically pull the certificate along with the information like Client number when you will click on Finish, the certificate from this new system will be applied to SID shown on the top, like the arrow mark.

Lets see in case of ABAP

You can use any user ID with proper authorization.

The process is just the same in case of ABAP system.

Here we have seen that with help of Wizard, how life became easy, but wait this is not all.................

We have seen that with help of this wizard we can apply certificate to java system easily, but when we want to apply certificates into some another Java system or ABAP system then?

Here our new friend NetWeaver 7.3 SSO2 Wizard will help, lets see whats extra in there.

Notice the new button "Connect to Remote System" this button was not there in older versions, you can checkout the screenshot given in starting of this blog.

When we click on the button, it will give two options from drop down.

Lets say I want to jump to any Java system in which I want to apply SSO certificates, no matter what version of Java that would be, fill in required values

Click OK and you will be able to jump to this new system, notice the changed SID in below screenshot (red arrow)

Now here you can follow the same method described above and import certificates from any ABAP or Java system as per your requirement.

Lets see, if we can jump to any ABAP system

Click OK

The green arrow shows in which system we are and with help of red eclipse we can import ABAP or Java system certificates as many we want.

In Nutshell, the new button "Connect to Remote System" giving you flexibility enough so that you can be Lazy

Though its not centralize administration but somehow you can work with all your systems in your landscape, so for generating sensation I am calling it centralized administration of SSO.

Hope this will be of help to some of us.

My other Blogs, if you have time...

How to Rename the Oracle Listener & Change Listener port for SAP

Multiple/Bulk transports with tp script for Unix (AIX, Solaris, HP-UX, Linux)

OSS1 & RFC connections SAPOSS, SAPNET_RFC, SDCC_OSS

Interrelation: SAP work process, OPS$ mechanism, oracle client & oracle shadow process

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-2

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

OSS1 & RFC connections SAPOSS, SAPNET_RFC, SDCC_OSS

Posted by Ishteyaque Ahmad Apr 27, 2012

Many times we come across when our SM59 RFC connection SAPOSS or other connections related to SAPNet is not working, most of the time due to wrong password, which you we can easily correct with the correct logon data which is as follows(SAP Note 182308):
Language    EN
Client      001
User        OSS_RFC
Password    CPIC

But this is not which I wanted to discuss here. Here we will check the firewall connection and how to create these RFC connections automatically.

Before we proceed, maintaining correct hostname(Use FQDN) and its correct IP that can be reached from outside of you customer network is very important.

So double checking it is best idea.

Scenario 1

In above screen of OSS1, we have SAProuter 1 and SAProuter 2 entry filled, though filling the entry for SAProuter 1 and SAProuter 2 is not mandatory in order to work your OSS connection in SM59.... BUT from your server firewall and SAPNet firewall connection should be allowed.

Lets move to this scenario, where both SAProuter 1 and SAProuter 2 entry is filled with your customer hosts where saprouter is configured.

For discussion sake lets assume the server name is "C" where you are executing OSS1 tcode, and two other servers are host A and host B as mentioned in figure.

The flow will be C -> A -> B -> SAPNet

1. Login to server C and check the port

telnet <A IP/hostname> 3299

You should get response like below

2. Again login to host A and check port

telnet <B IP/hostname> 3299

Now, we will check in reverse direction for incoming flow

B -> A -> C

1. Login to host B and check port for A

telnet <A IP/hostname> 3299

2. Login to host A and check port for C here you have to check for your application instance number, if it is lets say 40 then

telnet <C IP/hostname> 3240

If any of the above telnet is not working then get in touch with your client network/firewall team and request them to open the port.

In this scenario, we noticed that SAProuter 2 is router which is responsible for first entry point from outside your client network, which means the firewall at host B should be open for SAPNet to enter and at the same time if it is not done earlier then you have to be in touch with SAPNet network team and request them with help of OSS message to allow entry for your host A

Scenario 2

When we fill SAProuter 1 only not the SAProuter 2

This means that in client network host A will be entry/exit point and your application servers will be communicated with SAPNet like this

C -> A -> SAPNet

You have to check your firewall accordingly.

Note 35010 - Service connections: Composite note (overview)

If all these firewall is working fine, the delete all RFC connection related toSAPNet and recreate them as follows (SAP Note 812386)

1. Transaction OSS1 ->Parameters -> Technical settings -> Change mode -> Save. The SAPOSS destination can only be updated by saving.

2. Create the RFC destinations again:

Use the following path to create SAPNET_RTCC: SE38 -> RTCCTOOL -> list -> Refresh from SAPNet

Use the following path to create SAPNET_RFC: SDCC -> Maintenance -> Refresh -> Session overview

SDCC_OSS is created initially when you activate SDCCN. If you then want to create a new copy of SAPOSS, use the following path:

SDCCN -> Goto -> Settings -> Task specific -> RFC destinations -> Change mode -> 'Create destination to SAPNet R/3 Frontend'

Checkout this wiki for more insight about saprouter at SAPNet.

http://wiki.sdn.sap.com/wiki/display/Basis/Configure+OSS1+Connection

Hope this will be of help to some of us.

My other Blogs, if you have time...

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

How to Rename the Oracle Listener & Change Listener port for SAP

Multiple/Bulk transports with tp script for Unix (AIX, Solaris, HP-UX, Linux)

OSS1 & RFC connections SAPOSS, SAPNET_RFC, SDCC_OSS

Interrelation: SAP work process, OPS$ mechanism, oracle client & oracle shadow process

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-2

Posted by Ishteyaque Ahmad Apr 24, 2012

In my previous blog Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1 I discussed the installation part.

Now I would like to show the post step configuration.

Unlike previous versions, in NW7.3 we have Configuration Wizard which takes care of most of the configurational activity by itself, we just need to provide required information.

To start the Wizard we need to login to NWD with Administrator ID http://<hostname>5<nn>00/nwa

goto Configuration tab and click on Configuration Wizard.

Now on the above screen click on "Functional Unit Configuration UI"

Then you need to select Advanced Adapter Engine (AF)

By selecting this component, it will automatically select related components as you can see in above screenshot.

Provide the passwords.

Select the option "Use an existing remote SLD" and provide related User IDs and password from your actual SLD system, which will be the same SLD where all your PI 7.3 components are registered already.

In case if you get error with User ID and password, you can use pisuper for SLD Data supplier User

Now you can login to your SLD system and check the PI category and there you will find entry for your Adapter Engine. In case if you are not able to view the entry here, you should go to your adapter server URL http://<AE_hostname>:5<nn>00/exchangeProfile

and check for hostname for SLD and there should be FQDN for SLD hostname

in AS Java Category you will find entry for the Advance Adapter SID

Now goto your PI server http://<PI_hostname>:5<nn>00/rwb/index.jsp

Click on "SLD Registration" in the Non-Central Components you should see the entry for newly installed Decentral Adapter Engine. If the entry is not present then you need to check for the Domain name of the Decentral Adapter, Domain name should be same as rest of the systems in PI system.

Hope this will be of help to some of us.

and this is completion of my previous blog.

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

My other Blogs, if you have time...

Bye bye STRUSTSSO2: New Central Certificate Administration NW7.3

How to Rename the Oracle Listener & Change Listener port for SAP

Multiple/Bulk transports with tp script for Unix (AIX, Solaris, HP-UX, Linux)

OSS1 & RFC connections SAPOSS, SAPNET_RFC, SDCC_OSS

Interrelation: SAP work process, OPS$ mechanism, oracle client & oracle shadow process

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-2

Install and configure NetWeaver PI 7.3 Decentralize Adapter part-1

Posted by Ishteyaque Ahmad Apr 24, 2012

I would like to share the purpose of Decentral Adapter for PI 7.3 and how to install and configure it from NetWeaver Administrator perspective.

What is the meaning of term “Decentral Adapter Engine”?

When a PI adapter is being installed outside PI system it is called Decentral Adapter …because the adapter engine which gets installed along with PI installation is known as Central Adapter Engine. Often it is also referred as Advance Adapter Engine. In a nutshell, unless the term “Extended” is not used it should not be considered as AEX (Advance Adapter Engine Extended).

Please refer to the installation master options for PI 7.3 Adapters

The setup of Decentral Adapter is more like a standalone SAP system, which means you have to install it as a separate SID, For NW7.3 PI it will contain SCS, PAS & DB instance of its own. Some people wrongly assume that it will have same SID as PI system and there is no need to have DB instance for it, which is wrong perception.

When Decentral Adapter Engine can be used:

There is Firewall between Integration server and Business system which cannot be opened for either security or corporate policy of Client(Customer).
Some protocols of Sender/Receiver system are not allowed e.g. ftp not allowed between two servers.
When we use Decentral Adapter Engine, because it is on different server and not utilizing resources of actual PI system, it shares load and boosts the overall performance.
If you wants to use some drivers which are not available for the OS on which your PI is running.

Installation of Decentral Adapter Engine (in this example Distributed option is selected)