Generate Installation Key

You need an installation key to install from, or upgrade to, SAP ECC from Release 5.0

Procedure

In the SAP Solution Manager system

1. Call the Solution Manager System Landscape (transaction SMSY), in your SAP Solution Manager system.

2. Create the product system for which you want to generate the installation key, in the system landscape:

   1. Select the landscape component Product System, and choose Create New Product System from the context menu.

   2. Enter the system ID as product system name in the next dialog box.

   3. Choose the product and product version from the possible entries help. Save.

   4. Complete the system data, as far as possible.

   5. Save your entries.

3. Generate the key:

   1. Choose  System Landscape Other Object , in the menu.

   2. Set the Product System flag, and choose the product system to be installed or upgraded, from the possible entries help. If you created the product system in the SAP Solution Manager in the previous step, choose this product system.

   3. Choose Generate Installation/Upgrade Key.

   4. Enter the required data and choose Generate Key.

      The system displays the key.

In Installation/Upgrade Tool

Enter this key in the installation or upgrade tool. 

Solution Manager System Landscape (SMSY)

You create and manage the system landscape centrally in SAP Solution Manager to use the settings in the following areas:

• Implementation and template projects

• Monitor change requests (Change Management)

• Customizing synchronization (Customizing Scout, Customizing Distribution)

• In operational processing (for example System Monitoring or Incident Management)

• in Maintenance Optimizer maintenance transactions

 

Features

• Create product systems

• Assign the active product version for a product system and choose relevant product instances

• Definition of non-SAP products for use as system landscape settings

• Overview of system groups and logical components

• Create logical components

• Specify and assign attributes to landscape components

• Graphic display

  • Landscape components (servers, databases, product system)

  • Assign attributes to landscape components

• Analysis of system landscape by components

 

Activities

Call the Solution Manager System Landscape (transaction SMSY).

Deactivate progress indicator

To improve performance, deactivate the progress indicator that is displayed by default in the status bar at the bottom of the screen:

1. Choose  Goto Configure System Landscape Maintenance Edit Advanced Settings .

2. Enter a value for the Deactivate Progress Indicator option, for example, X.

3. Choose Continue.

 

 

SAP Solution Manager Configuration Work Center

This work center gives you access to the guided procedures with which you can perform basic SAP Solution Manager and managed system configuration processes, automatically.

It is divided into views, in which guided procedures lead you through various configuration scenarios.

Features

• System preparation

  You make settings which are the prerequisite for the configuration of the SAP Solutioin Manager.

• Basic Configuration

  The configuration steps required, to be able to use the basic SAP Solution Manager functions. You configure the most important SAP Solution Manager functions, applications and work centers, for example:

  • Communication with SAP

  • Service Desk

  • SAP EarlyWatch Alert

  • Maintenance Optimizer

  • Service Delivery

  • Diagnostics

• Configuration of Managed Systems

  Connect managed systems to the SAP Solution Manager, and configure them for basic SAP Solution Manager functions.

Other scenarios are optional parts of the SAP Solution Manager, which depend on your implementation plans:

• Technical Monitoring: In the technical monitoring configuration, you configure the following subscenarios:

  • Self-Monitoring monitors the status of the SAP Solution Manager

  • System Monitoring monitors the status of the managed systems

  • End User Experience monitors the availability and performance of business processes, from the end user's perspective

  • PI Monitoring monitors XI (SAP Exchange Infrastructure) and PI (Process Integration) systems, which enable data exchange between managed systems

  • Connection Monitoring monitors connections between managed systems

• Measurement Platform: Set up the infrastructure to measure key figures, and monitor the overall operating costs of your systems

• Other Configuration gives access to tools and documentation which support further configuration scenarios. You configure these scenarios manually. They include, for example, test management and quality gate management.

SAP Solution Manager Basic Configuration

You can use this process to configure the SAP Solution Manager, immediately after installation, after an upgrade, or after importing Support Packages. The system leads you through this process.

 

 

Prerequisites

 

• The license key is installed.

• 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

 

 

Process

1. To perform the assisted basic configuration of the SAP Solution Manager, start the work center 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.

2. Execute the required and desired configuration scenarios:

   • In the case of a new installation, execute at least the configuration scenarios System Preparation, Basic Configuration, and Configuration of Managed Systems.

   • After an upgrade, check in the steps of the different configuration scenarios which activities are marked in the column Update. You need to execute the marked activities again.

   The system starts a guided procedure, and leads you through the steps of the configuration scenario.

3. Follow the instructions in the relevant 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 or 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.

Available Functionalities in Solution Manager 7.0

 

Service Delivery & Service Support with SAP Solution Manager

 

Sizing Recommendations for Additional Components

Diagnostics - For additional Diagnostics Sizing, see the according documents for installation and configuration service.sap.com/diagnostics

 

Wily Introscope Enterprise Manager - SAP Note 797147

 

System Landscape Directory  - service.sap.com/sld

 

Software Lifecycle Manager - service.sap.com/slm

 

Adobe Document Services - service.sap.com/adobe

 

Business Intelligence - If BI runs on the same client as Solution Manager additional sizing is necessary service.sap.com/bi

 

SAP Quality Center by HP - service.sap.com/solutionmanager

 

SAP Redwood Job Scheduling - service.sap.com/job-scheduling

 

Windows editions and memory support (FAQ) - SAP Note 313347

 

Master Guide SAP NetWeaver 7.0 - service.sap.com/installNW70

 

Help on Application Usage for SolutionManager; Links to further documentation for SAP NetWeaver, SAP Business Suite - help.sap.com

 

Initial Sizing for SAP Solution Manager - Assumptions

 

 

All assumption examples should be regarded as general assumptions regarding numbers of servers, etc.. In practice, you may have a greater or smaller number of servers, etc. We recommend that you base your sizing estimate on the assumptions for the landscape with the next highest number of servers. For example, if your server number is 60, then you should base your estimate on the sizing recommendations for

Large sized system landscapes.

In general, all assumptions in this paper are based on

Unicode. For more information on specific dependencies, see: http://service.sap.com/unicode -> Unicode at SAP -> Unicode Media Library ->Unicode Information on Specific Topics -> Unicode: Hardware Requirements and Customer Experience.

Scenario Overview of SAP Solution Manager

The Implementation and Upgrade scenarios support the implementation of customer projects and the definition of template projects and upgrade projects. In template projects, you define one or more templates containing scenarios, documents and configuration for re-use in other systems, e.g. for a global roll-out of centrally defined implementation settings. These Implementation and Upgrade scenarios include roadmaps, an editor for creating and maintaining business blueprints, access to the Implementation Guides (IMG), and tools for testing, monitoring and distributing Customizing.

 

The Solution Monitoring scenario provides support for functionalities such as Service-Level Reporting, EarlyWatch Alert, Business Process Monitoring, System Monitoring, Central System Administration, System Landscape Reporting, as well as user-defined alerts.

 

The Service Desk of the SAP Solution Manager offers a complete infrastructure for organizing and operating a solution-wide support organization at your site. The Service Desk promotes effective user support in your SAP solution landscape every step of the way - from the end-users to your internal support organization and when necessary to SAP.

 

Change Request Management in SAP Solution Manager is aligned to the processes in the IT Infrastructure Library (ITIL), the de facto standard for service management. As defined in ITIL, the objective of Change Management is to carry out changes economically and in a timely manner with minimal risk. Change Request Management includes processes for managing change requests, project management, and change logistics.

 

The operations Collaboration section of the SAP Solution Manager is the point of access to SAP support services, including remote services, on-site services, self services, and Best Practice documents. Based on your solution configuration, recommendations for these services are triggered dynamically. The reports resulting from each service are available and are archived in the operations section. The reports are useful documentation stored in the SAP Solution Manager and serve as reference information for the efficient future operation of your solution landscape.

 

A key requirement for efficient and safe support of IT solutions is the ability to perform root cause analysis with speed and efficiency. Diagnostics in SAP Solution Manager provides standardized tools for the support of customer solutions, including third-party components. The tools enable a systematic and targeted cross-component localization of the root cause of IT problems. The centralized approach avoids that many experts have to search for possible root causes on all components involved, in most cases without success. With the possibilities of Diagnostics, your support organization can both save costs and accelerate the time required for problem resolution.

Parallelizing Send Processes for Improved Performance

To improve performance for busy message periods, you have the option of parallelizing the SAPconnect send process. This enables send requests to be processed on multiple work processes that can run on different application servers. Only one background job is executed, which starts multiple work processes. This divides the send requests into packages and sends them in parallel over different servers. These work processes are dialog work processes that are started in addition to the work process on which the send job (report RSCONN01) is running.

 

The option of dividing up send requests requires additional control parameters, however these do not normally have to be changed. These are parameters of report RSCONN01. These parameters are job-specific, meaning that different parameters can be set for different send jobs. They can be set when creating a send job in the job maintenance. They are always stored as variants of report RSCONN01.

Prerequisites

You must only implement parallelization if a very large number of send requests have to be processed, subsequently hindering the performance.

Procedure

To parallelize the send process, proceed as follows:

...

       1.      Call transaction SCOT and choose Settings  ® Send Jobs  or symbol  (send jobs).

       2.      Choose Schedule Job.

You are given a menu for the different address types (FAX, INT and so on). You use this to preselect the job name and the standard variant delivered by SAP that are to serve as a template for the job. You can still change these values in the subsequent dialog box Send Job: Select Variant.

       3.      If required, adjust the job values or variant values in the dialog box Send Job: Select Variant.

If individual parameters of the selected variant are changed, a prompt appears after confirming the changes, asking you to save the variant. Here you can still change the variant name, which creates a new variant with this name.

The values in the Job Values group box always depend on the variant chosen above. If you change the values here, you also have to save a new variant for them.

As the same thing happens during parallelization, from a technical point of view, as when starting the send process, the fields in the Variant Values group box are the same as those that are displayed under Utilities ® Start Send Process:

Field	Variant Value
Number of Work Processes	If a value greater than 1 has been entered in the Number of Work Processes field for an SAPconnect send job, the processing of the messages being sent is distributed across the corresponding number of dialog work processes. If the value for Number of Work Processes is set to 1, or if the number of waiting messages lies below a defined threshold value, no parallelization takes place, and no additional dialog work process is used. You configure this threshold value using the Minimum Packet Size parameter (under Details).
Server Group	The Server Group parameter specifies the application server that is used for the send process. If no value has been entered, then all available servers are used. If the number of work processes is set to 1, this parameter can be ignored.
Details	Under Details you can find parameters for maximum and minimum packet size, maximum number of send requests to be read at once from the queue, timeout factor for each send request, timeout offset for aRFCs and Commit Work. In most cases, you do not have to change the predefined settings for these details parameters that were delivered by SAP. For help about the individual fields, see the system documentation (F1 help) or the info buttons on the user interface.

 

 

Scheduling a Send Process as a Background Job

A send process should be scheduled periodically. The period should not be too short. Performance can therefore be optimized because the RFC connection is used many times (for example, every 5 minutes during busy message periods and every 15 minutes for quiet message periods). During busy message periods, the SAPconnect send processes should be distributed across various SAP application servers or all assigned to one dedicated SAP application server.

Procedure

You can schedule a send process as a background job in two ways:

·        Conventional Job Scheduling

·        Simplified Job Scheduling

 

 

Conventional Job Scheduling

 

 1.      Call transaction SCOT to start SAPconnect administration and choose View ® Jobs. 

 

  2.      Choose . 

 

  3.      Enter a job name.

 

A list of all the available variants is displayed.

 

 4.      Position the cursor on the variant that you want to start the send process with.

You can also create a new variant or change an existing variant. To do this, choose  Variant or  Variant. Proceed as described in Variant Maintenance. Then choose  to return to the list of available variants and position the cursor on the new variant.

  5.      Choose Schedule.

  6.      Specify the first date for execution.

  7.      Choose Schedule periodically.

 8.      Specify the length of the interval after which the job is to be started, for example every 5 minutes, depending on the amount of transmission activity in your system.

 9.      Choose .  

 

 Simplified Job Scheduling 

1.      Call transaction SCOT and choose Settings  ® Send Jobs or the job symbol from the toolbar.

 2.      Choose Schedule Job.

You are given a menu for the different address types (FAX, INT and so on). You use this to preselect the job name and the standard variant delivered by SAP that are to serve as a template for the job. You can still change these values in the subsequent dialog box Send Job: Select Variant.

 3.      If required, adjust the job values or variant values in the dialog box Send Job: Select Variant.

If individual parameters of the selected variant are changed, a prompt appears after confirming the changes, asking you to save the variant. Here you can still change the variant name, which creates a new variant with this name.

The values in the Job Values group box always depend on the variant chosen above. If you change the values here, you also have to save a new variant for them.

Send Processes

A send process reads the messages that are to be sent from the SAPconnect queue, determines the appropriate nodes, and transfers the messages to the external communication systems. Messages are, therefore, only sent externally if regular send processes are scheduled.

The send processes are scheduled as regular background jobs. For test purposes, you can also start a send process in dialog. You can restrict a send process to one or more communication methods or you can schedule a send process for all communication methods.

If you are using the SMTP plug-in but have not activated it on all application servers, you have to let the send process run as a background job on the application servers on which it is activated.

Activities

Two options are available for scheduling send processes:

·        In SAP job maintenance

In this case, you create jobs that start the ABAP program RSCONN01 with the requested variant and at the requested time as a background job.

·        directly in SAPconnect administration as a background job or in dialog mode.

 

Testing Routing

 

You can use this test to check whether routing for outgoing messages runs correctly in your communications environment. The test provides information on how the appropriate node is determined using the recipient address you specified and whether fax and paging numbers are converted according to the rules for recipient number adjustment.

Procedure

Choose Utilities ® Routing test.

Specify a user name as the sender. Your user name is the default setting.

Specify a recipient address and the relevant address type.

Choose .

In the Outbound node and address frame, the node responsible for the specified recipient address and the format into which the recipient address was converted are displayed. If no node is found, you receive an error message.

Choose .

You receive a description of how the address was checked, how the node was determined, and whether the recipient address was converted into an external format. If an error occurs, the reason for the error and the step in which it occurred are displayed.

 

The SMTP Node

If you want to use the SMTP plug-in to send Internet mails, faxes, and/or SMSs externally, use the SMTP node. This node is delivered with SAPconnect and has to be adjusted to meet the requirements of your system landscape. In contrast to the other nodes, you cannot create any more SMTP nodes, nor can you delete the existing one. If you do not use the SMTP node, you cannot activate it (that is, you cannot set the Node in use indicator).

 

To send using the SMTP plug-in, you have to set parameters for the profile of the Internet Communication Manager (ICM).

 

Activities

 

In SAPconnect administration (transaction SCOT), double-click on the SMTP node.

 

Specify the following parameters with the ICM server/port combination to be used to send the messages:

Parameter	Description
Mail host	Host name of mail server for outgoing messages
Mail port	Port number for mail server for outgoing messages
Code page	The code page to be used when sending messages.

 

Also specify the following attributes:

Attribute	Description
Maximum waiting time for repeat send attempt procedure	Specify how long the send attempts are to be repeated for before the send process is cancelled, in the event of a communication error occurring when connecting to the mail server.
Node in use	Select this attribute when you are using the node.

 

Choose Set for the communication methods that the node can process. For each communication method, enter the formats and address areas that the node is to process. In the case of the communication methods FAX and SMS, also specify the domains to be used for address conversion. If, for example, you enter faxserver.company.com, the fax number DE 06227/7-455555 is converted into the following address:

FAX=+4962277455555@faxserver.company.com.

Setting Device Types for Format Conversion

 

In the case of printer-dependent output formats, you have to specify the device type for which the format is to be converted.

Procedure

In SAPconnect administration (transaction SCOT), choose Settings ® Device Types for Format Conversion.

Specify for each printer-dependent format (PDF, PCL, PS and TXT) the device type that is to be used for the formatting.

A list of the device types available can be found in SAPNet note 8928. This list is continually updated.

It is indicated in the list whether a format is specified as an output format for a node.

 

Formats

 

You have to specify for each node the format in which messages with internal SAP formats are to be output for each communication method. Output means sent when the SMTP plug-in is used and transferred to these systems when external communication systems are used. If necessary, the external communication systems convert the format into another format, in which the message is then sent.

Activities

You assign the formats to a

node during the creation process. You can change formats in node maintenance. To do this, choose Set in the node data display for the relevant communication method. The following formatting options are available:

Internal SAP format	Possible output formats
SAPscript/SmartForms	PDF, PCL, PS, TXT
ABAP list	HTM, PDF, PCL, PS, TXT
Link to a business object	HTM, TXT
Internal SAP text format (RAW)	PDF, PCL, PS, TXT

In the case of printer-specific formats (PDF, PCL, PS and TXT), you have to specify the device type for which the format is to be converted.

When messages are converted into a printer-specific format, temporary spool requests are generated. These are deleted in the next spool reorganization.

 

Address Area

 

The SAPconnect send processes read the messages from the SAPconnect queue for outbound messages. By using the recipient addresses, the system determines which nodes the messages are transferred to. If there are several recipients, there can also be several nodes. Every node must therefore be assigned the addresses, which it can edit. In normal cases a node is not assigned individual addresses, but rather address areas. The send process only sends messages with recipient addresses within one of the specified address areas to the node.

Node determination on the basis of recipient addresses is known as routing. If one recipient address to address areas corresponds to several nodes, the one that fits best is selected, that is the address area which contains the most characters of the recipient address. Non-generic entries have the highest priority when decisions are made.

The SAPconnect routing concept is based exclusively on the address areas. It is not possible to use other data, like for example the formats supported by the nodes, as the basis for the routing.

Activities

You assign the address areas to a node during the creation process. You can change the address areas in the node maintenance or by choosing Goto ® Address area ®Create in the node- or routing view.

Address areas always apply per address type. Generic address areas ending with the special character * can be created, as well as Internet addresses starting with the same special character. If you do not assign an address area, all addresses of the address type entered are processed.

A node can process all Internet addresses:

Address type: INT

Address area: *

A node should only process local faxes within Walldorf:

Address type: FAX

Address area: DE06227*

To check how the routing of messages on the basis of address areas functions, you can carry out routing tests.

 

Nodes

A node represents a logical view of an external communication system in the SAP system, for example, an e-mail system, a fax system, or an additional SAP system. The SMTP node, which controls sending using the SMTP plug-in, is a special case.

Each node has all the information necessary for sending from the SAP system using the external communication system. A node must be created for every external communication system that is used to send documents from your SAP system. Indeed, nodes are not necessarily required for receiving messages. Despite this, it is recommended for the communication environment administration that a node is also created for receiving.

Prerequisites

For the connection using an external communication system

Outgoing messages are transferred from SAPconnect via RFC to the external communication system. For calling the communication system, the SAPconnect node must recognize the RFC destination. RFC destinations are maintained in transaction SM59. When creating a SAPconnect node, you can use an existing RFC destination or you can create a new one.

For the connection using the SMTP plug-in

The parameters of the ICM have to be set on every application server used for sending.

Activities

You must assign the information below for accessing the external communication system and its attributes to the other nodes.

The attributes that you allocate to the node must correspond to those of the external communication system that the node represents. For more information, see the communication system documentation.

It is recommended that you carry out node maintenance in SAPconnect administration under View  ® Node.

 

Function	Icon	Description
Create node		A wizard leads you through the creation process.
Display/change node		An overview of the attributes of the selected node is displayed. In order to display or change the settings for the address areas, formats and transmission control, choose Set next to one of the selected communication types.
Delete node		The selected node is deleted with all its attributes.

 

Specify the communication methods that the node can process. For each communication type enter the formats and address areas which should process the node. If necessary, you can specify rules for recipient number adjustment for the communication method Fax.

 

Also specify the following attributes:

Property	Description
Maximum waiting time for repeat send attempt procedure	Specify how long the send attempts are to be repeated for before the send process is cancelled, in the event of an RFC error occurring when connecting to the external communication system.
Node in use	Select this attribute when you are using the node.
Node can resolve path references	Specify whether the external communication system supports this attribute. SAP systems, the SAP Internet Mail Gateway, and the SAP Exchange Connector, for example, do not support this attribute.
Node is to be monitored by the alert monitor	You can only use the functions of the alert monitor for SAPconnect and SAPphone for this node if you select this attribute.
Node supports connection test, status, trace	You can only use the functions for querying the operating status and setting the external trace for this node if you select this attribute. If you select this attribute, you have to perform a connection test. The connection test checks the version of the external software. This enables the upward compatibility of the SAPconnect interface to be guaranteed in the future. When you call a function, the system then checks whether the external communication system supports this function by using the version. If the external communication system does not support the connection test and, despite this, you start the connection test, this can cause the external software to crash.

 

 

 

Creating an RFC User

To receive messages (including status messages), an RFC user is required. An RFC user has to be created in every client in which messages are to be received. An RFC user is also required in order to receive messages using the SMTP plug-in.

The RFC user is an SAP user of the type Service. Therefore, it is not possible for a person to logon with this user name in dialog.

Procedure... 

       1.      Choose Tools ® Administration ® User Maintenance ® Users.

       2.      Enter a name, for example MAIL_ADMIN.

       3.      Choose .

       4.      On the tab page Logon data, select the user type Service.

       5.      Enter a password.

       6.      On the Profiles tab page, enter the authorization profile S_A.SCON. This profile minimizes the risk of misuse, even if the communication system does not store the password is encoded form.

       7.      Choose .

Authorizations in SAPconnect

Authorizations for RFC users

External communication systems log onto the SAP System as an RFC user. The authorizations for this user are contained in the profile S_A.SCON. The profile is made up of the following authorizations:

Authorization object	Authorization	Field values
S_OC_SEND	S_OC_ALL	Range of the permitted number of recipients: * Permitted communication methods: ' '
S_DATASET	S_DS_WF_USER	Program name: SAPLSWT1 Activity: 034 Physical file name: *
S_RFC	S_RFC_SCON	Activity: 016 Name of the RFC object to be protected: SX02, SYST Type of the RFC object to be protected: FUGR
S_OC_TCD	S_OC_USER	Transaction codes: SBWP, SO00, SO03 - SO07, SO09, SO12, SO13, SO15, SOAD, SOCP, SODS

Authorizations for SAPconnect administrators

The SAPconnect administrator requires the authorizations for the RFC user and the authorizations for table maintenance, which are checked using the authorization object S_TABU_DIS. These authorizations are contained in the following roles:

• SAP_BC_SRV_COM_ADMIN
• SAP_BC_SRV_GBT_ADMIN

SMTP Configuration - II

User Maintenance (Transaction SU01)

·        Service user

You have to create a service user for processing incoming mails in every SAP system client in which you want to receive mails (or status notifications). Call transaction SU01 to create a user with type Service and assign the profile S_A.SCON to this user.

·        User addresses

Every user that is to receive e-mails in an SAP system requires an Internet mail address. This is also used as a sender address. Enter the Internet mail address for a user in transaction SU01, under E-Mail on the tab page Address.

 

Assigning the Client (Transaction SICF)

Every SAP system client that is to receive and process incoming mails (or status notifications) must have an SMTP server. One SMTP server (SAPconnect) has already been created in transaction SICF and is delivered with every SAP system. Use this to create the first client and then create another SMTP server for each additional client. Configure the following settings on the SMTP servers:

·        Host data

Enter the sequence number of a parameter is/SMTP/virt_host_<*> from the profile. If you have only created one client and therefore have not specified this parameter type, enter 0.

·        Service data

Enter the client to which the mails received through the virtual mail host are to be forwarded, and then enter the logon data of the system user that you created for the incoming mails.

·        Handler list

Enter CL_SMTP_EXT_SAPCONNECT at position 1.

Note that each SMTP server must be activated (Service/Virt. Host ® Activate) after being created or changed. Inactive servers are grayed out.

 

SAPconnect Administration (Transaction SCOT)

You have to configure SAPconnect settings for every client that is used for send processes.

·        Default Domain

Under Settings ® Default Domain, define the domain of the SAP system client. This allows for the following to take place:

·         The SMTP plug-in logs on to the mail server using the domain as ID.

·         The message ID of the outbound e-mails is assembled with this domain.

·         If an SAP user who does not have an Internet mail address sends an e-mail, a sender address consisting of the SAP user name and this domain is generated.

·        Nodes

Each client has an SMTP node. This node is created by the SAP system and cannot be deleted. The following steps need to be carried out to configure the node so that sending Internet mail is possible:

i.         Make sure you are in the Node view.

ii.       Double-click the node name.

iii.      Choose Node in use.

iv.      In the Mail Host and Mail Port fields, specify the mail server to which the outbound mails are to be sent.

v.        Next to Internet, choose Settings.

vi.      Enter the address area of the recipient addresses that are to be reached using this node. In general, * is used if all e-mails are to be sent using SMTP.

vii.     Enter the output format for SAP documents. We recommend that you use the following settings:

SAPscript/Smart Forms	PDF
ABAP list	HTM
Business Object / Link	HTM
RAW Text	TXT

viii.   Confirm your selection.

If you also want to configure the node for sending faxes:

i.         Next to Fax, choose Settings.

ii.       Enter the address area of the recipient addresses that are to be reached using this node. In general, * is used if all faxes are to be sent using SMTP.

iii.      Enter the output format for SAP documents. We recommend that you use the following settings:

SAPscript/Smart Forms	PDF
ABAP list	PDF
Business Object / Link	TXT
RAW Text	TXT

iv.      Enter the domain of the fax server or fax provider under Conversion into Internet Address. The system generates the local part of the Internet address automatically. The address therefore takes this format: FAX=+RecipientNumber@Domain.

v.        Confirm your selection.

If you also want to configure the node for sending text messages (pager/SMS):

i.         Next to Pager (SMS), choose Settings.

ii.       Enter the address area of the recipient addresses that are to be reached using this node. In general, * is used if all text messages (pager/SMS) are to be sent using SMTP.

iii.      Enter the domain of the text message (pager/SMS) server or provider under Conversion into Internet Address. The system generates the local part of the Internet address automatically. The address therefore takes this format: SMS=+RecipientNumber@Domain.

iv.      Confirm your selection.

·        Send Job

E-mails sent from an SAP application are first stored in a queue. A periodical background process, the SAPconnect send job, gets the e-mails from this queue and sends them over the Internet. To schedule this job in SAPconnect: Administration, proceed as follows:

i.         Choose View ® Jobs.

ii.       If no other job has been scheduled, choose Job ® Create.

iii.      Enter a job name and confirm it.

iv.      Select the variant SAP&CONNECTALL by positioning the cursor on it.

v.        Choose Schedule Job.

vi.      Choose Schedule periodically.

vii.     Select the interval you require, such as 10 minutes.

viii.   Choose Create.

·        Inbound

If you want incoming e-mails that have a particular address or particular content to automatically start a program that processes these mails, you can configure this under Settings ® Inbound Processing.

If you want incoming e-mails that have a particular address or come from a particular sender to be automatically forwarded to another recipient or another distribution list, you can configure this under Settings ® Inbound Processing.