3 create r3interactions1

7/31/2019 3 Create R3interactions1

http://slidepdf.com/reader/full/3-create-r3interactions1 1/24

1

EP 6.0: R/3 Connec t ion



2

© SAP AG 2002, Title of Presentation, Speaker Name 2

Acc essing an R/3 system

1. Creating a System

2. Creating an Alias for the System

3. Creating an iView which uses the above System

4. Add the iView into a page

5. Add the page into a role

6. Assign the role to a user



3


Creat ing a Sys tem (1 )



4





5





6





8


Creat ing a Sys tem a l i as (2 )



9


Pr oper t i es o f t he system (1 )



10





11





12





13


Cr ea t i ng an iV iew w h ich uses t he system a l i as (1 )



14





15





16





17





18


Edi t ing SAP syst em s

com.sap.portal.pcm.Title :The title, or friendly name, for the system object. The value is mandatory,exists for each property.

connectionFactoryClass :The name of the connector class; the connector to which the template isconnected. The value is mandatory when working with a connector.

ComponentType :Defines the type of the component; for example, when importingcomponents, the search could be based on this property. The value ismandatory, exists for each system.

Namespacesep : Defines the separator between name spaces

Title : Defines the system template title

SystemAlias : The logical system name to which the system is pointing

R3name : Points to an R/3 system, just like the system alias

SystemType : Type of the SAP system, such as R/3 Basis, BW, and so on.



19


Edi t ing SAP system s (Proper ty va lues c ont inued)

ServerPort : Port number of application server or message server

Type :Type of remote host. The default value is 3. Valid values: 1/31/21/E

ConnectionGroup :Type of connection group: Load Balancing or Dedicated Server. Propertycomes with a defined value

* ashost / mshost : SAP application server / SAP message server

* sysnr / group : SAP system number / Group of SAP application servers

Client :The SAP client. The R3 template supports a number of clients: iViewsbased on JCA connectors, SAPApplicationComponent, andjcoClientService

Trace : Enable/disable RFC trace



20



Properties for Security and Authorization:

snc_mode : Secure network connection mode

snc_partner_name : SNC partner name

snc_qop : SNC level of security

snc_myname : The SNC name. Overrides SNC partner.

snc_lib : Path to the library that provides SNC service

Logonmethod : The Authentication method for logging on to the

SAP system. Comes with the default value: SAPLOGONTICKET.Valid values: 14/SAPLOGONTICKET6/UIDPWD8/X509CERT



21



Properties related to the ITS:

wap.ITS.protocol : Protocol of the Internet Transaction Server (ITS)

wap.ITS.hostname : Hostname of the ITS

wap.ITS.path : Path in the ITS

wap.ITS.title : Default value: ITS

wap.ITS.category : Category of the ITS

wap.ITS.description : Description of the ITS



22



Properties related to the WAS:

wap.WAS.protocol : Protocol of the Web Application Server (WAS)

wap.WAS.hostname : Hostname of the WAS

wap.WAS.path : Path of the WAS

wap.WAS.title : Default value: WAS

wap.WAS.category : Category of WAS

wap.WAS.description : Description of the WAS



23



Properties related to the DRS:

wap.DRS.protocol : Protocol of the Drag&Relate Server (DRS)

wap.DRS.hostname : Hostname of the DRS

wap.DRS.title : The Default value is: DRS

wap.DRS.category : The Category of DRS

wap.DRS.description : The Description of the DRS





R3referencesystem :Property associated with user mapping. The R/3 username that isset in the ticket. Default value: “0“; the administrator configures

one system and gives the same ticket to other systems; the systemthat appears in the User Mapping UI. Valid values are : 1/01/1

Usermappingtype :Defines the type of user mapping needed for connection; who canperform user mapping

Usermappingfields :Additional comma separated user mapping fields.If otherparameters are needed for user mapping, they are defined here

3 create r3interactions1

Documents