multiple role task
Post on 05-Apr-2018
213 Views
Preview:
TRANSCRIPT
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 1/18
System Administration Made Easy 9 –1
&KDSWHU 0XOWL5ROH7DVNV
&RQWHQWV
Starting the R/3 System..........................................................................................9 –2
Stopping the R/3 System........................................................................................9–5
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 2/18
Chapter 9: Multi-Role Tasks
Starting the R/3 System
Release 4.6A/B 9 –2
6WDUWLQJWKH56\VWHP
To start the R/ 3 System in a produ ctive environmen t:
1. Start the operating system (if requ ired).
2. Check the operating system logs to verify a good start.
3. Start the da tabase.
This step is optional because starting th e R/ 3 System also starts the da tabase.
How ever, manu ally starting the database allows you to review the database log before
starting the R/ 3 System.
< NT/ SQL: If not autom atically started, use the SQL Server Service Manager to start
the database.
< NT/ Oracle: If not autom atically started, use SAPDBA to start the database.
< UNIX: At the comman d prom pt, enter startsap db.
4. Check the database logs to verify a good start.
5. Start R/ 3 on the central instance.
< NT: Use the SA P M anagement Console.
< UNIX: At the comm and p romp t, enter startsap r3.
To start the R/ 3 System, at the r estart, wait for 60 second s before you chan ge the server’s
clock. This step m akes it easier to read the system log. For example, the last stop en try is
19:26:xx and the first star t ent ry is 19:27:xx, where time is reported as hh:mm :ss.
6. Check the R/3 System log (SM21) to verify a good start.
Problems at this point may requ ire you to cycle (stop and start) the system.
7. Start R/ 3 on the app lication instances.
The app lication servers w ould be started an y time after step 2.
8. Check the R/3 System log.
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 3/18
Chapter 9: Multi-Role Tasks
Starting the R/3 System
System Administration Made Easy9 –3
6WDUW5³17
1. On the NT desktop , double-click
SA P R3 M anagement Console.
2. Click on the nod es (+) to dr ill down
to the <servers>.
Start the Central Instance (on the
database server).
3. Right click on the <database server>
(for example, pa100767), and
choose Start .
4. The following two items ind icate
that the database instance has
started and that R/ 3 has completed
the start p rocess:
a. The status indicators for the
database server change color to
green.
b. The Status for both processesindicates Running.
Wait a few m inutes because startup
activity is still occurrin g on th e
server.
Tools such as QuickSlice an d Perfmon allow you to m onitor the activity of the server and
know wh en it is OK to logon to the system.
4a4b
3
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 4/18
Chapter 9: Multi-Role Tasks
Starting the R/3 System
Release 4.6A/B 9 –4
The steps below are applicable only if
you have an application server:
Start th e d ialog instance (on the
app lication server).
1. Click on the nodes (+) to drill dow n
to the <app lication server> (for
example, pal002840), and choose
Start .
2. The following two items ind icate
that the da tabase instance has
started and that R/ 3 has completed
the start p rocess:
a. The status indicators for theapp lication server chan ge color
to green.
b. The Status for the p rocess
indicates Running.
3. Wait a few minu tes because startup
activity is still occurr ing on the
server.
1
2a 2b
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 5/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
System Administration Made Easy9 –5
6WRSSLQJWKH56\VWHP
< When you stop R/ 3, coordinate and p lan this stoppage with all users or their
representatives.
< Stopp ing a system at “your convenience” is unp rofessional and u sually causes
considerable operational issues with u sers who n eed (and expect) the system to be up
and runn ing.
6WRS5&KHFNOLVW
Task Date Initial
The follow ing tasks must be completed w ell before the R/3
System is stopped:
Coordinate the shu tdow n w ith all affected p arties, such as:
< Finance
< Shipping
< Sales
< Other
Reschedu le/ cancel jobs that wou ld be running or starting
du ring the schedu led shutd own (SM37).
Create a system m essage announ cing the p lanned shutd own
(SM02).
The follow ing tasks must be completed before the R/3
System is stopped:
Check that there are no active users on th e system (SM04 an d
AL08).
Check that there are no active background jobs runn ing
(SM37 ).
Check for active processes (SM50 an d SM51).
Check for active external inter faces.
To stop the R/3 System:
Stop the application server instance(s).
Stop the central instance.
Stop the d atabase (optional).
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 6/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
Release 4.6A/B 9 –6
7DVNVWR%H&RPSOHWHG%HIRUH6WRSSLQJWKH6\VWHP
< Coordinate the shu tdow n w ith all effected p arties.
If an organ ization has p lanned to d o something and expects the system to beoperational, they m ay or may not be able to reschedu le. You m ay have to reschedu le
your shutd own around them and shutdow ns are usually negotiated activities.
([DPSOH
An IT person in a company rebooted a server in the midd le of the day withou t telling
anyone. He had a da te that evening and did n ot wan t to stay late. The CFO said,
“Yeah, he’ll have a d ate w ith the u nemp loyment line.”
Before stopp ing the system, there are several checks that n eed to be m ad e. The p urp ose
is to determ ine that there is no activity on the system wh en the system is stopped .
Certain activities (such as a large p osting job), if interrup ted, could have sometransactions posted and some not yet p osted. Recovery could then become an issue.
If you are th e cause of the emergen cy, be prep ared to take the consequences.
An examp le of an emergen cy is not mon itoring th e file system, having it fill up , wh ich
results in stopping R/ 3.
< Reschedu le or cancel jobs that w ill be runn ing or starting d uring th e scheduled
shutdown.
Check SM37 for these jobs and cancel or reschedule them to ru n after the shutd own .
Watch for rep eating jobs, such as d aily or weekly jobs.
These jobs are n ot created u ntil the job for the p rior period (day, week, etc.) has run .
In other w ords, a d aily job cannot exist several days in ad vance.
< Create a system m essage announcing the planned shutd own.
< Emergency or p riority shu tdow ns (for example, file system full, log full, equipm ent
failure, etc.) are a d ifferent m atter.
In these instances, you need to shutd own im med iately and u sers need to accommod ate
you . There m ay be little—if any—negotiating.
6\VWHP0HVVDJH60
:KDW
A system message is a popu p th at users see when they first log on to the R/ 3 System. This
window app ears after a new message has been created or w hen u sers move between
screens.
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 7/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
System Administration Made Easy9 –7
*XLGHG7RXU
In the Command field, enter transaction SM02 and choose Enter
(or from th e SA P standard menu, choose Tools → Administration → Administration →
SM02-System messages).
Choose Create.
In System message text , enter your
message.
If you are only shutting dow n one
server, you m ay also enter text in
th e Server field. To enter this text,
choose and select the instance
on which the message shou ld
appear.
In Expiry on, enter the message’s
expiration da te and time.
Choose .
When referencing the time for the shu tdow n, always enter th e specific time, time zon e, and
date (for example, 0230 PDST-Mon–Jun 8,1998). Enter ing vague inform ation, su ch as “ in 15
minu tes” creates possible confusion as to when an d w here an event h as been sched uled.
Some examp les of confusion th at m ay arise includ e:
< 15 minu tes (from wh en?)
< 0230 (where? Corp orate offices or where th e user is?)
< 6:00 (a.m. or p .m.?)< Mond ay (of wh ich week?)
6
5
3
2
4
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 8/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
Release 4.6A/B 9 –8
The message in the statu s bar
indicates that your m essage has
been saved.
This screen shows th e message as
the user w ould see it.
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 9/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
System Administration Made Easy9 –9
&KHFNWKDW1R$FWLYH8VHUV$UHRQWKH6\VWHP$/60
*XLGHG7RXU
For a system without app lication servers:
1. In the Command field, enter SM04 and choose Enter
(or from th e SA P standard menu, choose Tools → Administration → Monitor → System monitoring →
SM 04-User overview).
2. Contact the users and have them
log off.
3. If users cannot be contacted , delete
their session as described in
chapter 12, Deleting a User’s
Session.
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 10/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
Release 4.6A/B 9 –10
For systems with app lication servers:
1. In the Command field , enter AL08 and choose Enter
(or from th e SAP standard menu, choose Tools → CCMS → Control/Monitoring→ Performance menu →
Exceptions/users→ Active users → AL08-Users global).
2. Scroll down the tran saction screento see all the server s in the system
and the users on those servers. 3. Contact the users to have them log
off. 4. If the user s cannot be contacted ,
delete their session a s d escribed in
chapter 12, Deleting a User’s
Session.
You cannot d elete a u ser from
transaction AL08. You mu st loginto the individu al instance and
use tr ansaction SM04 to delete the
user session.
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 11/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
System Administration Made Easy9 –11
&KHFNIRU%DWFK-REV5XQQLQJRU6FKHGXOHG60
Check for any batch jobs that are running or are scheduled to run du ring the shutdown .
*XLGHG7RXU
1. In the Command field, enter SM37 and choose Enter
(or from th e SA P standard menu, choose Tools → CCMS Jobs → SM37-Maintenace).
2. Enter * in User name. 3. Under Job status, select the
following: < Planned
< Released
< Ready
< Active
4. Chang e the Fr (from) da te back a
year. 5. Chang e the To date to a date
beyond the shutd own p eriod. 6. In or after event , choose and
select *. 7. Choose Execute.
5
2
4
3
7
6
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 12/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
Release 4.6A/B 9 –12
8. Choose a job to review
(for example, GARY-TEST).
9. From the menu bar, choose Job→
Change.
Change the display to show the planned start date and time.
From the m enu bar, on the screen above, choose Settings → Display variant → Current .
On th e field selection screen, mov e the planned start date an d planned start t ime from the
hidden fields on the right, to the displayed fields on the left.
10. Choose Start condition.
9
8
10
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 13/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
System Administration Made Easy9 –13
11. Ch ange the Scheduled start da te, to
a date after the shutdow n.
12. Choose Save.
13. Verify the new start d ate.
14. Choose Save.
11
12
14
13
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 14/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
Release 4.6A/B 9 –14
15. A m essage ind icates tha t the job
was saved.
16. Repeat th e steps for each of the
other jobs that need to be moved .
17. As a final step, repeat the initial job selection to verify that there
are no jobs sched uled d uring the
system shutdown .
15
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 15/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
System Administration Made Easy9 –15
&KHFNIRU$FWLYH3URFHVVHVRQ$OO6\VWHPV60
*XLGHG7RXU
1. In the Command field, enter transaction SM51 and choose Enter
(or from th e SA P standard menu, choose Tools → Administration → Monitor → System monitoring →
SM51-Servers).
This screen lists all instances in the
system.
2. Select an instan ce.
3. Choose .
4. The screen that app ears is the
transaction SM50 screen for th at
server.
5. Review for activities.
6. Choose Back and return to the SAP
servers transaction (SM51).
7. Repeat steps 2 to 5 for eachinstance.
&KHFNIRU([WHUQDO,QWHUIDFHV
External interfaces are interfaces wh ere da ta is being m oved to or from th e R/ 3 System.Checking for active interfaces dep end s on th e specific interface and how it has been
designed, built, and implemented . The developer or consultant can help you d etermine if
the interface is active.
2
5
6
3
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 16/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
Release 4.6A/B 9 –16
6WRSSLQJ5
< When you bring dow n or stop R/ 3, coordinate and plan this event with all the R/ 3 users
or their rep resentatives.
< Stopp ing a system at “your convenience” is unp rofessional and usu ally causesconsiderable operational issues with users who need (and expect) the system to be u p
and run ning.
Stop R/ 3 only after all checks have been m ad e and you are certain that there is no activity
on the system.
To stop the R/ 3 System:
1. If there are app lication servers in the system, stop the instance on the ap plication
server(s).
2. Stop the instance on the database server.
< NT/ SQL: Use the SA P M anagement Console.
< UNIX: At the comman d prom pt, enter stopsap
This script m ay also stop the da tabase; check you r specific
installation.
3. If needed , stop the database.
The database mu st be stopp ed separately. Unlike the start process, stopp ing the system
does not also stop the d atabase.
< NT/ SQL: Use SQL Server Service Manager to stop the database.
< NT/ Oracle: Use SAPDBA to stop the database.
< UNIX: Use either SAPDBA or the stopsap script to stop th e database.
4. If needed , stop the operating system.
67235³17
1. On the NT desktop,
double-click SAP R3
Management Console.
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 17/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
System Administration Made Easy9 –17
2. Drill dow n to the:
a. <SID> (for examp le, SA S).
b. <servers> (for examp le, pa100767
an d pal002840).
The follow ing steps are applicable
only if you have application servers.
Stop the R/ 3 dialog instance (on the
app lication server).
1. Click on the nod es (+) to d rill down
to the <application server> (for
example, pal002840).
2. Right click on the <ap plication
server> and choose Stop.
3. Choose Yes.
4. When R/ 3 stops:
a. The status indicators change
color to gray.
b. The Status indicates Stopped .
3
2a2b
2b
1
4a
4b
7/31/2019 Multiple Role Task
http://slidepdf.com/reader/full/multiple-role-task 18/18
Chapter 9: Multi-Role Tasks
Stopping the R/3 System
Release 4 6A/B
Stop the R/ 3 central instance (on the
da tabase server).
1. Click on the nodes (+) to drill dow n
to the <d atabase server> (for
example, pa100767 ).
2. Right click on the <database server>
and choose Stop.
3. Choose Yes.
4. When R/ 3 stops:
a. The status indicators change
color to gray.
b. The Status indicates Stopped .
3
4a
1
4b
top related