One Identity Manager SAP Experience #11 Installation Prerequisites and SAP Transports

[MUSIC PLAYING] When identity manager's SAP connector supports SAP ABAP based instances from version 7.0 to 7.5 and SAP S4 Hana Window version 18.09. If you want to connect to such an instance in the ECC R/3 or S4 Hana versions of that SAP environment, the application server ABAP must be available as prerequisites since the SAP connector does not support a Java application server. To install the SAP connector, we will require additional software and prerequisites that need to be done on the SAP instance. For SAP, we will require the SAP NCo libraries and our ABAP application transports to be installed on the SAP instance that needs to be connected. So if you have several clients on the SAP system that you want to connect to, we will need these transports to be applied to all the instance's clients on that SAP system. For connecting to these systems, we will also require an SAP application user that will have the required permissions to change these users and add these roles to the users and profiles. So additionally we will require on our site software from SAP, we will need the NCo 3.0 connectors from SAP. These connectors are needed to connect to the [? ident ?] is the SAP system and cannot be provided by One Identity Manager. This software has to be provided by the customer whose SAP instance is being connected to. These NCo drivers need to be installed on each and every job server instance that need to connect to the SAP environment as well as on the identity server-- Identity Manager administrators who want to connect to the SAP environment using the job service or using the synchronization editor. We have specific requirements for the NCo versions that can be verified in the identity manager documentation. And in case the software is installed on the job service, please don't forget to upload the software into the database using the software load. [MUSIC PLAYING] When connecting an SAP client to One Identity Manager, we also require some transport to be imported into the specific client. These transports are ABAP code that is part of our shipment and will create reserve namespace at additional tables into the system as well as additional ABAP program functions and code that the connector relies on to execute the needed functionality in the SAP system. This is due to the different versions of the SAP environment. So we will have a constant or clear interface that we can connect to, and the specifics of the underlying version of SAP will be hidden behind our transports. In order to apply these transports, there is a specific order in that the transport need to be imported. The first transport that needs to be imported is the SAP repository transport. This will create the namespace in the SAP environment and will provide every namespace called VIAENET. The second transport is the SAP table transport, which will create additional tables in that specific namespace that are used to hold preliminary data while accessing the system. And the third transport, this depending on the version of your SAP environment whether it's SAP 4.7 or 7.0 instance, you will have to select a sub-transport package, and there is a distinction between a Unicode and non-Unicode system in that transport. The fourth and last transport is an optional transport. It's a convenient transport that we provide for customers who don't want to create their own roles and on permit-- grant their own permissions to the user account-- the service account that is being used. This SAP role can be imported and assigned to the service account that the connector will use on that instance. If the customer has specific requirements on how roles are named or created or maintained in the SAP environment that it's going to be connected to, then the customer can create his own SAP role. The required permission and authorizations for this service account are documented in our documentation, and the specifics can be assigned and built in the role as the customer sees fit. [MUSIC PLAYING]