Visual Admin Tool

In this artical, I am going to cover the following.

* What is visual admin tool ?

* Significance of visual admin tool

* Path to access the visual admin tool

* Running the visual admin tool.

Note:-Visual admin tool is replaced with the NWA tool from Netweaver7.1 or higher versions

                                                                                                                                                                   
What is Visual Admin tool?

Visual admin tool is the graphical user interface(GUI) based tool.

Visual admin is built on java platform.

Visual admin tool is used to maintain the cluster.

It is template of component running on java engine.

It requires jre installed on the platform, where you are running visual admin tool from.

                                                                                                                                                                   
Significance of visual admin tool

It is used to maintain the UME(User Maintainance Engine) settings.

It is used for maintaining the cluster.

Visual admin is an online tool. It means database should be up and running during the access of visual admin tool

It works like RZ11.(Whenever you make changes it does not require instance restart.)

You can login to multiple server,But one server at a time.

It is used to fetch the details of the services running on SAP server.

You can remotely login to any server.

It runs on P4 port.

This tool is password protected.

It is used to install the license.

It is used to create Jco - Rfc connection

                                                                                                                                                                   
Path to visual admin tool

Below is the path to access the visual admin tool.

usr/sap/<sid>/<INSTANCE<nr> >/j2ee/admin/go.bat  ->for windows

usr/sap/<sid>/<INSTANCE<nr> >/j2ee/admin/go.sh  ->for unix

                                                                                                                                                                 
Running the Visual admin tool.

Goto above specified path. And excute the go.bat file or go.sh file.

                                                                                                                                                                  

Assigning logical System to Client

1) Login in golden client like 000 with user like ddic.

2)Execute transaction code SCC4 or SALE

3)Click on change icon

5)Double click on client for which you want to assign the logical system.

6) Provide the logical system name from drop down list.Or you can manually type. and save it

Client Creation

                                                                         Creating A Client

1) A client is a business independent unit.

2) It provides the different different environment within the same SAP SID.

3) It is considered to be the data separator in the SAP environment.

4) A client is represented by three digit number in SAP.

5) A client is stored in table T000.

6)Whenever a client is created an entry is made in T000. And it does not contain any data as soon as it is created.

7) Initially whenever we create a client it is created with the default user 'sap*' and password 'pass'.


                                                                              Procedure


A) Execute the transaction code SCC4

B) Click on Change Icon                                                                                                                           

                                                                               

C)The Following message will appear.Click on OK                                                                                     

D)Click on New Entries                                                                                                                            

E) Provide 3 digit client number for 'client' textbox. Input City,Logical System, Std currency, Client Role etc.

F) Scroll down the screen and provide the following options as it is, If your system is playing the      development role in the landscape.

G)Click On save, When you save the following prompt will appear click on ok.                                    

Client 150 will get created.

Logical Client Creation

                                                  LOGICAL SYSTEM CREATION

1)Logical system help to uniquely identifying the system in the landscape

2)Logical system names are stored in table TBDLS

3)Once logical system are created and assigned, These can not be deleted.

4)You can change the logical system name but you can't delete, if they are assigned to any client.

5)Table TBDLS is the cross client and therefore these names are visible to throughout the landscape.

6)The syntax to create the logical system name is :- <sap system Id>CLNT<CLIENT NO.>

    E.g.-: DEVCLNT150 (DEV= sap system ID,CLNT=from naming convention,150=Client no.)


Procedure

A) Login in client 000 user like ddic

B)Execute transaction code SALE or BD54                                                                                               

C)Navigate as Basic Settings-> Logical System->Define Logical System                                                      

D) The Following message will appear. Click on Ok(Ritht symbol)                                                               

E) Click on New Entries. If this option does not occur than click on change button to get this option              

F)Specify the Logical System name in Log. System column. And description in Name column                       

G)Click On save.                                                                                                                                      

Creating Operation Modes

                                                                 OPERATION MODES

1) Operation Modes are used for proper utilization of resources.

2)Operation modes are used to convert the DIALOG(dia) workprocesses into BACKGROUND(bgd) or vice versa.

3) Operation modes are used to define the resources for the instance.

4)Operation modes are used to switch the bgd to dia or vice versa without restarting the INSTANCE.

5)Operation modes are triggered automatically on specified time.The effect can be seen in sm21/sm50/sm66.


                                                 CREATING THE OPERATION MODE

1) Execute the transaction code RZ04 the following screen will apear.

2)Click On create ICON the following screen will apear                                                                             

3)Specify the operation mode name and save it.                                                                                       

4)If you want to create another mode,Again press the create button and repeat step 3                               

5) After saving the information, Below screen will apear                                                                        

6) Go to settings->Based on current instance->new instance->genrate.                                                      

7)Specify Application server name(on which you want operation mode to get triggered) for the dropdown textbox Of Appl Eg.-MYCOMP_DEV_00. server.And specify the dialog and background workprocesses that you require for the particular time.                                                                                                                                    

8)Click on save button.Now one prompt will apear which ask you to maintain the other operation                  modes,Click on yes  . And maintain the resources for the other operation mode, As I did in below screen  shot.                                                                                                                                                       

9)Click on save and this time click on no for the prompt.                                                                               10)Execute the Transaction code sm63 to define the time for the operation modes(defined earlier).                  Below screen will appear click on change button.                                                                                                                        

11)Choose the time range for which you want operation mode to get triggered. And click on Assign button.    

12)Define the operation modes for the time and save it.                                                                                 

Facts about sap* and ddic

                                                     sap* and ddic  facts


-> sap*  and ddic users are super users which are created by default when we install the sap application.
-> In fact to install ddic user's privileges are used.
->So ddic(data dictionary) user is created first with the default password 19920706 for client 000 and 111 only. But at the end of the installation phase the default password for ddic is overwritten with the master password provided at initial phase of installation.

->Default password for sap* is 06071992. It is also overwritten with the master password.
->It is applicable for default clients 000,001,066.
->sap* user reside at kernel level, means it is in the kernel code.
->Whenever we start sap application, Kernel code is executed and check whether sap* exist or not. If it does not exist than the kernel code again creates sap* user with the password pass.
->For the security reason this user is disabled to log in.
->To enable the login for sap* user set the parameter login/no_automatic_user_sap*=0 and restart sap application
->Even than if you are not able to login with sap* user than delete it from os level.
->To delete sap* user execute the sql command delete from SAPSR3.usr02 where bname='sap*' and mandt='<client no.>'; for mssql server replace SAPSR3 with <dbsid>.
->Later set the parameter login/no_automatic_user_sap*=1 or some higher value.To prevent from any accidental case.
->Or you can lock the user sap*.
->lock ddic user, It is used for some upgrade/update and installation tasks in background. Unlock ddic user only when it is required
->You are advised not to use ddic user.
->You can create user like ddic by making a copy of ddic.
->To copy execute su01 and press copy icon than provide ddic in copy from option.

->Beside this we also have a earlywatch user in 066 client with the password support. So you should also lock the earlywatch user.Unlock it when you open the connection to SAP.

Kernel Upgrade

KERNEL UPGRADE
Kernel upgrade is the process of replacing the old executable with new executable. 
SAP Kernel Resides in /sapmnt/<SID>/exe (or) /usr/sap/<SID>/SYS/exe/run for 32/64bit Machines.
The need to upgrade the kernel may arise in the following circumstances.

1. Applying of support packages sometimes demand the updated kernel
2. During an SAP OS/DB upgrade (or) patching
3. To fix the bug as per the notes
4.As part of the early watch report SAP recommends. 
we can check the Kernel Version by executing “disp+work” on
<sid>adm user

PROCESS:
1. Stop SAP System, Stop Services (SAPOSCOL, SAP<SID>_00, All
Oracle Services)
Page

2. Backup The Kernel Directory for Rollback in any inconsistencies with the new kernel.                 

3. Check the present kernel Patch level by executing disp+work (or)  login to the system and navigate to system-->status

4. Download the Latest Kernel from SAP Service Market Place (SMP) specific to Release, OS, DB,

Hardware and Unicode/Non-Unicode

Execute the URL www.service.sap.com/patches to download the latest

kernel and specify the S-USERID and Password

Navigate to software Downloads-->support packages and

patches-->My Company Application Components-->Click on

Complimentary Software

Now select the kernel based on 32/64bit and Unicode/Non-Unicode

Select the “Linux on IA32 32bit”

Select the Database Independent and download the kernel files

“SAPEXE_310-20000967.SAR” file and click on add to Download Basket

Click on Oracle to download the database dependent file

Select the Database Dependent and download the kernel files

“SAPEXEDB_310-20000968.SAR” file and click on add to Download

Basket

Download all the files that is mentioned in the above.

After Successfully Downloading the kernel files Uncar the kernel files

as follows

5. Uncar the Executables into kernel with New kernel Directory

Like that uncar all the executables by suing command SAPCAR –xvf <filename.SAR>

6. Copy the executables into existing kernel (because only few of

them are updated) i.e., overwrite the existing kernel executables.

7. Run the below script with the ‘root’ user to get the privileges for

br*tools (./saproot.sh)

8. Restart the services and SAP system i.e., start all the services that

is mentioned in step1.

9. Check the kernel version by executing command ‘disp+work’ in

<sid>adm user/login in to system and check in systemstatus

Execute the command “dpmon” to check whether the system is up &

running (or) not

Kernel Is Updated Successfully