《PEK - K2 connect configuration and administration》由会员分享，可在线阅读，更多相关《PEK - K2 connect configuration and administration（21页珍藏版）》请在金锄头文库上搜索。
1、K2 connect configuration and administration,This learning module describes how K2 connect is installed and how K2 connect installations are configured, administered and tested,Module prerequisites and target audience,Target AudienceK2 administrators and infrastructure administratorsSAP Developers an
2、d AdministratorsSolution architectsK2 DevelopersPrerequisite knowledgeSAP basics and SAP BAPIsK2 connect basics (200.PVG - Introduction to K2 connect)Visual Studio (basic experience)CompatibilityK2 4.6 or later with K2 connect 4.6 or laterScopeUnderstand the connect architectureInstalling and config
3、uring K2 connectUnderstanding connect securityTesting, logging and diagnostics,K2 connect and SAP: conceptual architecture,ERP connect is used to call SAP BAPIs via RFC,Destinations usually map 1:1 to connect Service Instances,Connect Service Objects usually map 1:1 to K2 Service Objects,Each Destin
4、ation connects to a specific SAP System,connect components and machine boundaries,K2 application server (K2 blackpearl and K2 connect),Developer workstation (with Visual Studio)Administrator workstation,SAP Server,K2 connect: Installation,K2 blackpearl must be installedServer components for serverK2
5、 for Visual Studio for developer workstationsInstall lib32rfc.dll provided by SAPCannot be distributed by K2, available from SAP Service MarketplaceMust install the correct version (32-bit or 64-bit)Required on each server hosting the K2 connect serviceRequired on developer workstations where Visual
6、 Studio plugins will be installedInstall ERPConnectAvailable for download from K2 portalSeparate installation from K2 connectRedistribution license and installation permits use for K2 connect ONLYRequired on each server hosting the K2 connect service Required on developer workstations where Visual S
7、tudio plugins will be installedInstall K2 connectServer installation for all K2 servers (license key required)Client-side installation for developers/admins (no license required),Destinations and Service Objects,Configuring Destinations (1/2),After installing connect, use the administration tool to
8、set up one or more DestinationsDestination names should be simple and clearOptional: specify static design-time credentials for the SAP systemIf no credentials in connection string (a.k.a. Predefined User Credentials), developers will need to provide SAP credentials at design timeRuntime credentials
9、 are determined by the Service Instance associated with the destination. Could be static or SSOBAPI security and access is managed by SAPOnly RFC-enabled BAPIs will be available to developersDevelopers will use these destinations into the Visual Studio tooling,Configuring Destinations (2/2),In the b
10、ackground, connect adds a Service Instance with the Destination Name in the Extra setting,LAB 1: Configuring Destinations,In this lab exercise you will configure a new Destination for an existing K2 connect installation. (To save time, K2 connect is already installed.)We want to create a SAP destina
11、tion to expose a particular SAP IDES system.,15 minutes,Note: you will be using a shared SAP IDES system which is hosted on the internet.,Multiple Destinations: Isolated Environments,Multiple Destinations: Shared Environments,Service Object Explorer and Test Cockpit,Visual Studio plugins used to exp
12、lore and test SAP BAPIsConnect to a K2 connect server and open destinationsUse Service Object Designer to explore available SAP BAPIs and launch Test CockpitUse Test Cockpit to test SAP BAPIs,LAB 2: Testing with Service Object Designer, Test Cockpit and generated SmartObjects,In this lab exercise yo
13、u will use the Visual Studio Test Cockpit to test a SAP BAPI in a specific Destination. You will also generate a SmartObject for a specific BAPI to verify that K2 connect is working as expected. Note: You will be using the SAP Destination that you configured in LAB 1,15 minutes,Show Context,Design-t
14、ime Authentication,Developers need permission to restart the K2 connect serviceOnly RFC-enabled BAPIs will be visible to developersAuthentication is defined by the Destination configurationPredefined credentials Set by connect administratorThe list of available BAPIs are based on the static credenti
15、alsNo predefined credentialsDeveloper will need to provide SAP authentication credentials The list of available BAPIs could be filtered based on the developer-provided credentialsDesign-time authentication is used for the Service Object Designer and Test Cockpit,Runtime Authentication,Authentication
16、 is determined by the Service Instance Authentication configuration (e.g. static/SSO)Change the authentication setting with the connect Administration toolStatic CredentialsUses static credentials at runtime (therefore no user-level security)K2 SSOUses the K2-cached credentials for the current userB
17、ased on the K2 SSO providerUser credentials are “converted” to equivalent SAP credentialsCredentials managed in K2 workspaceCan write code to add cached credentialsSAP SSORequires a SAP Logon Ticket (“token”) input parameter for each Service Object method callRequires SAP Netweaver portal to generate the Logon Ticket,
