Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam. blogger theme by BTemplates4u.com.
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam. blogger theme by BTemplates4u.com.
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam. blogger theme by BTemplates4u.com.
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam. blogger theme by BTemplates4u.com.
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam. blogger theme by BTemplates4u.com.
| Function | Menu Path | Transaction |
| Call operating system monitor for the local server | ® Local ® Activity | OS06 |
| Call operating system monitor for another server | ® Remote ® Activity, then select the desired server on the SAPOSCOL Destination screen | OS07, then select the desired server on the SAPOSCOL Destination screen |
In both cases, the system displays performance indicators for the operating system of the desired server.
Check the authorisations for the relevant destination in SM59:
You will see something like the following:
The SAPOSS destination still fails even though the password is correct. This has occurred previously as a result of a replication issue. The problem should resolve itself after a few days without making any changes in the system. In some cases it has taken up to 7 days.
Source: http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=233410011
The following describes how to install SAProuter. On UNIX, SAProuter is installed as a daemon. On Windows it is installed as a service.
You will find the latest SAProuter on the SAP Service Marketplace under Download SAP Software ®
In the hierarchy choose SAP NETWEAVER ® SAP NETWEAVER 04 ® Binary Patches ® SAP KERNEL
Here you will find the saprouter packet.
How you install the SAProuter depends on the operating system you are using. Choose the appropriate method:
Source: http://help.sap.com/saphelp_nw04/helpdata/en/4f/992d91446d11d189700000e8322d00/content.htm
This is often useful if, for example, there is a support connection from SAP to your SAP system that SAP staff use to access your system in the case of problems. SAProuter controls and monitors these connections.
Note that installing SAProuter without the use of a firewall does not protect your network against access from external networks. You must ensure that all incoming connections go through the SAProuter “hole”.
Source:
http://help.sap.com/saphelp_nw04/helpdata/en/4f/992ce8446d11d189700000e8322d00/frameset.htm
The first version of SAP's flagship enterprise software was a financial Accounting system named R/1 called as YSR. This was replaced by R/2 at the end of the 1970s. SAP R/2 was in a mainframe based business application software suite that was very successful in the 1980s and early 1990s. It was particularly popular with large multinational European companies who required soft-real-time business applications, with multi-currency and multi-language capabilities built in. With the advent of distributed client–server computing SAP AG brought out a client–server version of the software called SAP R/3 (The "R" was for "Real-time data processing" and 3 was for 3-tier). This new architecture is compatible with multiple platforms and operating systems, such as Microsoft Windows or UNIX. This opened up SAP to a whole new customer base
SAP R/3 was officially launched on 6 July 1992. It was renamed SAP ERP and later again renamed ECC (ERP Central Component). SAP came to dominate the large business applications market over the next 10 years. SAP ECC 5.0 ERP is the successor of SAP R/3 4.70. The newest version of the suite is SAP ERP 6.0 – the path to SAP Business Suite 7.
You use this component to process internal support messages, and forward them to SAP Support, if necessary.
Your project team members can create messages, which you can manage centrally in the Service Desk, in all project phases, e.g. in the Blueprint and during the test phase. Your internal customers, i.e. end or key users, can also create support messages from any SAP system. You process these support messages centrally in the Solution Manager Service Desk.
· Direct creation of support messages from any transaction
· Automatic capture of important data about the system in which the support message was created, e.g. installation number, installed software components, operating system, transaction, screen number.
· Automatic assignment of the support message to a support level
· Central message processing in the SAP Solution Manager:
¡ Display customer data, problem description, priority, attached documents, Service Level Agreements (SLA)
¡ Assign processor
¡ Send messages to the creator and other processors
¡ Forward message to other processors or support units
¡ Create documents and URLs
¡ Attach documents
¡ Status assignment and monitoring
¡ Create a worklist with selection conditions
· Search for SAP notes in the SAP Service Marketplace
· Import SAP notes with the SAP Notes Assistant
¡ Automatic corrections in ABAP source code
¡ Adjust changes to already imported Support Packages
¡ Display all SAP notes which were imported into a system with the SAP Notes Assistant
You can search for problem solutions in your internal solution database. The solution database is delivered without symptoms and solutions. You construct the internal solution database with the functions Edit Symptoms and Solutions (IS01) and Update Solution Database Index (IS02). For further information about creating your own solution database, see under http://help.sap.com/ ® SAP Customer Relationship Mgmt. ® SAP CRM 3.1 ® Search for „Customer Service (CS), Solution Database“ ® Solution Database in the Search menu.
The Support Desk is your interface to the SAP Service & Support. You can forward messages to SAP and receive problem solutions, in the Service Desk.
Source: http://help.sap.com/saphelp_sm32/helpdata/en/33/c7f5414e2fc517e10000000a155106/content.htm
This function leads you through one of the following selectable configurations:
Initial Configuration
You create a user for the administration of the SAP Solution Manager. The system performs one-off technical configuration steps, e.g. log the SAP Solution Manager on to the system management.
Basic Configuration
You configure the most important SAP Solution Manager functions, applications and work centers, for example:
Communication with SAP
Service Desk
EarlyWatch Alert.
Maintenance Optimizer
Service Delivery
Diagnostics
The system logs the current configuration status in each basic configuration step. You can also see this in the configuration transaction (SOLAR02).
Do not perform basic configuration with the users DDIC and SAP*.
You can technically perform basic configuration before initial configuration, but you must ensure that the results of the initial configuration are available. The system may not be able to perform the following configuration without initialization.
Configuration of Managed Systems
Create connections to managed systems, and configure them, for example for diagnostics.
You can call the guided procedure to configure managed systems for a selected system, from the System Administration work center.
The same prerequisites apply as for the basic configuration.
For more information, see SAP Solution Manager Basic Configuration.
You have activated the use of Web Dynpro services.
The system leads you through the configuration with a Guided Procedure.
Each step contains a context-sensitive, expandable help text with detailed information to help you perform the step.
The system proposes default values, which you can accept or change.
To edit the guided procedure, you only need to go to change mode once. The system stays in this mode for all other steps. The guided procedure is locked for other users during editing.
When you have entered data, you can save it with Save and Continue.
You cannot Save in every step. When you choose Continue, the system implicitly saves the part of the data which it uses later for automatic configuration.
This process configures the SAP Solution Manager, either after installation or after importing support packages. The system leads you through this process, which comprises the following areas:
Initial Configuration
When you have entered logon and authorization data for the SAP Solution Manager ABAP and Java instance administrators, connect the System Landscape Directory (SLD) to the SAP Solution Manager, with this configuration.
Basic Configuration
Basic configuration. Configure the basic functions of the SAP Solution Manager.
Configuration of Managed Systems
Connect managed systems to the SAP Solution Manager, and configure them for basic SAP Solution Manager functions.
You have installed the SAP Solution Manager and satisfied the following configuration prerequisites:
The license key is installed.
The profile parameter /ICM_HOST_NAME_FULL or SAPLOCALHOSTFULL is set.
The Transport Management System (TMS) is configured.
The connection to the SAP backend system exists and works.
The SAP Solution Manager Java instance is up-to-date.
You have started the load generator (transaction SGEN), for the following components, before configuration, to increase the performance of your systems in configuration:
ST
SAP_BASIS
SAP_ABA
Start the transaction SOLMAN_SETUP, to perform the assisted basic configuration of the SAP Solution Manager.
The first time you start your system, you go automatically to a Service Activation dialog window. You confirm the activation of Web-Dynpro Services.
The system then shows which configurations are possible, in the SAP Solution Manager: Overview screen. The system tells you which open activities you must perform for a configuration which you have selected.
You always perform the initial configuration for new installations. Choose the Initial Configuration view.
In an update of the support package stack for your system, you can, for example, go to the process with the Basic Configuration, or only perform part of the initial configuration, for example only to connect SLD.
The system starts a guided procedure, and leads you through the configuration steps. When configuring managed systems, you first go to a system selection screen, before the guided procedure starts. For more information, see SAP Solution Manager Basic Configuration Assistant.
You can also perform the basic configuration of the SAP Solution Manager without guided procedures. You must then perform the required SAP Solution Manager customizing activities individually, manually. For more information, see 
The best solution to know about these init levels is to understand the " man init " command output on Unix.
There's a file called /etc/fstab in your Linux system. Learn what its contents mean and how it's used in conjunction with the mount command. When you learn to understand the fstab file, you'll be able to edit its contents yourself, too.
In this tuXfile I assume you already know how to mount filesystems and partitions with the mount command. If you don't, I suggest reading the Mounting tuXfile before reading this one.
fstab is a configuration file that contains information of all the partitions and storage devices in your computer. The file is located under /etc, so the full path to this file is /etc/fstab.
/etc/fstab contains information of where your partitions and storage devices should be mounted and how. If you can't access your Windows partition from Linux, aren't able to mount your CD or write to your floppy as a normal user, or have problems with your CD-RW, you probably have a misconfigured /etc/fstab file. So, you can usually fix your mounting problems by editing your fstab file.
/etc/fstab is just a plain text file, so you can open and edit it with any text editor you're familiar with. However, note that you must have the root privileges before editing fstab. So, in order to edit the file, you must either log in as root or use the su command to become root.
Of course everybody has a bit different /etc/fstab file because the partitions, devices and their properties are different on different systems. But the basic structure of fstab is always the same. Here's an example of the contents of /etc/fstab:
| /dev/hda2 | / | ext2 | defaults | 1 1 |
| /dev/hdb1 | /home | ext2 | defaults | 1 2 |
| /dev/cdrom | /media/cdrom | auto | ro,noauto,user,exec | 0 0 |
| /dev/fd0 | /media/floppy | auto | rw,noauto,user,sync | 0 0 |
| proc | /proc | proc | defaults | 0 0 |
| /dev/hda1 | swap | swap | pri=42 | 0 0 |
What does all this gibberish mean? As you see, every line (or row) contains the information of one device or partition. The first column contains the device name, the second one its mount point, third its filesystem type, fourth the mount options, fifth (a number) dump options, and sixth (another number) filesystem check options. Let's take a closer look at this stuff.
The first and second columns should be pretty straightforward. They tell the mount command exactly the same things that you tell mount when you mount stuff manually: what is the device or partition, and what is the mount point. The mount point specified for a device in /etc/fstab is its default mount point. That is the directory where the device will be mounted if you don't specify any other mount point when mounting the device.
Like you already learned from the Mounting tuXfile, most Linux distros create special directories for mount points. Most distros create them under /mnt, but some (at least SuSE) under /media. As you probably noticed when looking at the example fstab, I use SuSE's mount points as an example.
What does all this mean? If I type the following command:
$ mount /dev/fd0
... my floppy will be mounted in /media/floppy, because that's the default mount point specified in /etc/fstab. If there is no entry for /dev/fd0 in my fstab when I issue the command above, mount gets very confused because it doesn't know where to mount the floppy.
You can freely change the default mount points listed in /etc/fstab if you're not satisfied with the defaults your distro has given you. Just make sure the mount point is a directory that already exists on your system. If it doesn't, simply create it.
Some partitions and devices are also automatically mounted when your Linux system boots up. For example, have a look at the example fstab above. There are lines that look like this:
/dev/hda2 / ext2 defaults 1 1
/dev/hdb1 /home ext2 defaults 1 2
As you've learned, these lines mean that /dev/hda2 will be mounted to / and /dev/hdb1 to /home. This is done automatically when your Linux system boots up... if it wouldn't, you'd have a hard time using your cool Linux system because all the programs you use are in / and you wouldn't be able to run them if / wasn't mounted! But how does the system know where you want to mount /dev/hda2 and /dev/hdb1? By looking at the /etc/fstab file of course.
The third column in /etc/fstab specifies the filesystem type of the device or partition. Many different filesystems are supported but we'll take a look at the most common ones only.
ext2 and ext3 Very likely your Linux partitions are Ext3. Ext2 used to be the standard filesystem for Linux, but these days, Ext3 and ReiserFS are usually the default filesystems for almost every new Linux distro. Ext3 is a newer filesystem type that differs from Ext2 in that it's journaled, meaning that if you turn the computer off without properly shutting down, you shouldn't lose any data and your system shouldn't spend ages doing filesystem checks the next time you boot up.
reiserfs Your Linux partitions may very well be formatted as ReiserFS. Like Ext3, ReiserFS is a journaled filesystem, but it's much more advanced than Ext3. Many Linux distros (including SuSE) have started using ReiserFS as their default filesystem for Linux partitions.
swap The filesystem name is self-explanatory. The filesystem type "swap" is used in your swap partitions.
vfat and ntfs Your USB stick is most likely formatted as Vfat (more widely known as FAT32). Your Windows partitions are probably either Vfat or NTFS. The 9x series (95, 98, ME) all use Vfat, and the NT series (NT, 2000, XP, Vista, 7) use NTFS but they may be formatted as Vfat, too.
auto No, this isn't a filesystem type :-) The option "auto" simply means that the filesystem type is detected automatically. If you take a look at the example fstab above, you'll see that the floppy and CD-ROM both have "auto" as their filesystem type. Why? Their filesystem type may vary. One floppy might be formatted for Windows and the other for Linux's Ext2. That's why it's wise to let the system automatically detect the filesystem type of media such as floppies and cdroms.
The fourth column in fstab lists all the mount options for the device or partition. This is also the most confusing column in the fstab file, but knowing what some of the most common options mean, saves you from a big headache. Yes, there are many options available, but I'll take a look at the most widely used ones only. For more information, check out the man page of mount.
auto and noauto With the auto option, the device will be mounted automatically (at bootup, just like I told you a bit earlier, or when you issue the mount -a command). auto is the default option. If you don't want the device to be mounted automatically, use the noauto option in /etc/fstab. With noauto, the device can be mounted only explicitly.
user and nouser These are very useful options. The user option allows normal users to mount the device, whereas nouser lets only the root to mount the device. nouser is the default, which is a major cause of headache for new Linux users. If you're not able to mount your cdrom, floppy, Windows partition, or something else as a normal user, add the user option into /etc/fstab.
exec and noexec exec lets you execute binaries that are on that partition, whereas noexec doesn't let you do that. noexec might be useful for a partition that contains binaries you don't want to execute on your system, or that can't even be executed on your system. This might be the case of a Windows partition.
exec is the default option, which is a good thing. Imagine what would happen if you accidentally used the noexec option with your Linux root partition...
ro Mount the filesystem read-only.
rw Mount the filesystem read-write. Again, using this option might cure the headache of many new Linux users who are tearing their hair off because they can't write to their floppies, Windows partitions, or something else.
sync and async How the input and output to the filesystem should be done. sync means it's done synchronously. If you look at the example fstab, you'll notice that this is the option used with the floppy. In plain English, this means that when you, for example, copy a file to the floppy, the changes are physically written to the floppy at the same time you issue the copy command.
However, if you have the async option in /etc/fstab, input and output is done asynchronously. Now when you copy a file to the floppy, the changes may be physically written to it long time after issuing the command. This isn't bad, and may sometimes be favorable, but can cause some nasty accidents: if you just remove the floppy without unmounting it first, the copied file may not physically exist on the floppy yet!
async is the default. However, it may be wise to use sync with the floppy, especially if you're used to the way it's done in Windows and have a tendency to remove floppies before unmounting them first.
defaults Uses the default options that are rw, suid, dev, exec, auto, nouser, and async.
Dump and, uh, what options? Well, dump is a backup utility and fsck is a filesystem check utility. I won't discuss them in great length here, but I'll mention them, because otherwise you'd spend the rest of the day wondering what on God's green Earth do these things mean.
The 5th column in /etc/fstab is the dump option. Dump checks it and uses the number to decide if a filesystem should be backed up. If it's zero, dump will ignore that filesystem. If you take a look at the example fstab, you'll notice that the 5th column is zero in most cases.
The 6th column is a fsck option. fsck looks at the number in the 6th column to determine in which order the filesystems should be checked. If it's zero, fsck won't check the filesystem.
As an example, we'll take a look at a couple of fstab entries that have been a source of endless frustration for new Linux users: floppy and CD-ROM (although these days floppies aren't that important anymore).
/dev/fd0 /media/floppy auto rw,noauto,user,sync 0 0
This line means that the floppy is mounted to /media/floppy by default and that its filesystem type is detected automatically. This is useful because the type of the floppy may wary. Note especially the rw and user options: they must be there if you want to be able to mount and write to the floppy as a normal user. If you have trouble with this, check your fstab file to see if these options are there. Also note the sync option. It can be async just as well, but it's sync because of reasons discussed a bit earlier.
/dev/cdrom /media/cdrom auto ro,noauto,user,exec 0 0
Note, again, the user option that enables you to mount the CD as a normal user. The CD-ROM has the ro option because it's no use mounting a CD-ROM read-write because you wouldn't be able to write to it anyway. Also note the exec option. It's especially useful if you'd like to be able to execute something from your CD.
Also note that the noauto option is used with the floppy and CD-ROM. This means that they won't be automatically mounted when your Linux system boots up. This is useful for removable media, because sometimes there won't be any floppy or CD-ROM when you boot up your system, so there isn't any reason to try to mount something that doesn't even exist.
