Required security accounts
One of the functions of Mobile Enterprise Platform is to act as a middle-ware server to outside systems of record. This includes ERP systems, Web Servers, Database Servers, and other systems that routinely require user authentication or security accounts to access their data or functions. The following information outlines the accounts that should be set up prior to installation of the Mobile Enterprise Platform software. Creation and validation of these accounts will increase the efficiency of the installation process and allow adequate time for submission of user account creation by administrators of the various systems with which Advanced Inventory platform will integrate.
Windows Service Account
This account will be used to start the Windows NT services which will be installed on the servers. This account should be a Windows Domain Account with Local Administrative rights on the machine, and ideally be an interactive account.
ERP System Account
The ERP system accounts you need will vary based on your organization's requirements. If your server does not need to connect to one of the following ERPs, do not create a system account for that ERP.
JD Edwards EnterpriseOne
This account is used by the platform to provide the security context for API call submissions to EnterpriseOne from the Advanced Inventory Application Server. This account should be set up to have interactive login permissions, and initially have a developer type role assigned to it. Ideally, fast path and UTB access are also suggested.
JD Edwards World
This account is not needed prior to the installation, as it generally will be created by the Advanced Inventory for World Installation process. If the Advanced Inventory for World software is already in place, then Advanced Inventory will need to know the user and password information for the development environment on the iSeries. This account is an iSeries profile.
Oracle E-Business Suite
The Mobile Enterprise Platform does not require a specific account to interact with Oracle EBS, as the platform integrates to Oracle EBS directly using PL/SQL functionality. However, this does require an Oracle database account that will be used to call this PL/SQL functionality. Refer to the ERP System Database Account section below for information on this account.
SAP
This account is used by the platform to provide the security context for AHBAP call submissions to the SAP Application Server from the Advanced Inventory Application Server. This account should be created as a dialogue user with development rights.
Platform Database Account (Oracle/SQL Server)
The platform database accounts you need will vary based on your organization's requirements. If your server does not need to connect to one of the following databases, do not create a platform database account for that database.
Oracle
This account is used by the Platform Web Services to access the dsiTransactionLog and/or the printing tables, if either are being utilized. The required permissions are the CONNECT and RESOURCE Roles, and the user also needs full permissions over the tables being used.
SQL Server
This account is used by Platform applications and services to access the Platform database. This account should have Database Owner (dbo) authority to the Platform database, and can either be the Windows Account previously discussed, or be a separate SQL Server specific database account.
ERP System Database Account
The ERP system database accounts you need will vary based on your organization's requirements. If your server does not need to connect to one of the following ERPs, do not create a system database account for that ERP.
iSeries
Platform requires read-only access to most Enterprise System databases for validation of information when processing scripts or workflows. If your Enterprise System Database is iSeries hosted, Platform requires the use of a valid iSeries profile. The list of tables and libraries for which Platform will require read-access is based on the Enterprise System and what types of transactions will be occurring in the system.
Oracle
Platform requires read-only access to most Enterprise System databases for validation of information when processing scripts or workflows. If your Enterprise System Database is Oracle hosted, Advanced Inventory suggests creating an Oracle user ID and password. The list of tables and libraries for which Platform will require read-access is based on the Enterprise System and what types of transactions will be occurring in the system.
SQL Server
Platform requires read-only access to most Enterprise System databases for validation of information when processing scripts or workflows. If your Enterprise System Database is SQL Server hosted, Advanced Inventory suggests creating a SQL Server specific user ID and password. This should be available prior to installation, as it will be required for integration validation.
Loading...
There was a problem loading this topic