send feedback

❮ Previous Next ❯

Connector settings

About connectors

Connectors are specialized components that register APIs in Mobile Enterprise Platform, and provide communication with a range of third-party systems.

All connector types allow your app developers to easily register any source API call within the system of record. Developers can then easily leverage source system functionality within their apps without knowing the specifics of how communication with each ERP system is performed. Advanced Inventory continually updates these interfaces, in conjunction with major ERP releases, so that as your system adds functionality and updates features, your Advanced Inventory system can keep pace.

You can configure the following connectors in Mobile Enterprise Platform to enable communication between Mobile Enterprise Platform and the specified enterprise software. If the system interfaces with multiple enterprise environments, the environment for which to configure the enterprise connector must also be selected.

EnterpriseOne Web Connector

Enables the Advanced Inventory MASP to register any JDE business function that is published as a Web service on the Oracle Business Services Server (BSSV).

EnterpriseOne XML Connector

Enables the MASP to register and call any JDE business function available in the system. This connector leverages the E1 Interoperability Client, using XML to send and receive API requests between the MASP and the E1 Enterprise/Application server.

Procedure Connector for Oracle

Enables you to register and call any PL-SQL package within the Oracle Database, assuming the registering user has read and execute authority to the PL-SQL package and associated tables.

Lawson Connector

Enables you to register and call any Lawson API through the Movex or M3 Enterprise Management System, assuming the registering user has authority to read and execute the APIs within the management system.

Microsoft Dynamics 365 Connector

Enables communication with Microsoft Dynamics 365.

Microsoft Dynamics AX Connector

Enables communication with Microsoft Dynamics AX.

Oracle Web Services Connector

Enables communication with the Oracle Application Integration Architecture, which integrates any combination of custom, Oracle, and non-Oracle applications into business processes.

SAP .NET Connector

Enables you to register and call any SAP BAPI on the SAP Application Server, assuming the registering user has the appropriate authority in the SAP System.

Webservices Connector

Enables communications with external systems via SOAP and REST web service APIs. With this connector, you can define web service definitions that leverage public API providers such as Google Maps and Weather Underground within a Mobile Enterprise Platform app.

TIMETrac Connector

Receives transactions from time clocks and other devices and moves them to TIMETrac using the TIMETrac web service.

Configure the EnterpriseOne Web Connector

The EnterpriseOne Web Connector transmits data among components and the EnterpriseOne enterprise software. When configuring this connector, elements are specified, such as WSDL file location, user ID, and password.

To configure the EnterpriseOne web connector, complete the following steps in Advanced Inventory Platform Manager.

Note: If you are using version 9.2.4.3 or later of Tools, see 64-bit Tools Setup below.

Go to Admin > Configuration > Connector Settings.
From the list of connectors, select the EnterpriseOne Web Connector.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.

Advanced Inventory

For WSDL file location, enter the location of the .WSDL file. This file describes the app interface methods that can be called when sending data to the EnterpriseOne web module.
For User ID, enter the user identification used when managing profiles and permissions in EnterpriseOne Web. Entry for this alphanumeric field is required and can range from 1 to 10 characters, with the first character being a letter. For example, barnesjp01. Letters, numbers, dashes, and underscores are allowed.
For Password, enter the user password assigned to this user profile in EnterpriseOne Web. Password formats vary depending on the parameters established in the Security tab on the System Settings page.
For Log request/response documents, enable this to log request/response documents to the Logging folder in the installation.

Step Information

Note:This field should only be enabled when troubleshooting API issues, and typically only when requested by the Advanced Inventory team. The resulting log file name format is E1Web_Request_TrackingIDGUID.xml.
For Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the web service when sending a request. A default value is provided; however, it can be changed. Entry in this numeric field can range from 5 to 300 seconds.
Select Save.

Configure the EnterpriseOne XML Connector

The EnterpriseOne XML Connector transmits data among components and the EnterpriseOne software. When configuring this connector, elements are specified, such as include path, enterprise system parameters, and system username and password.

To configure the EnterpriseOne XML Connector, complete the following steps in Advanced Inventory Platform Manager.

Note:If you are using version 9.2.4.3 or later of Tools, see 64-bit Tools Setup below.

Go to Admin > Configuration > Connector Settings.
From the list of connectors, select the EnterpriseOne XML Connector.
If the system interfaces with multiple enterprise environments, select the environment for which to configure the connector.
If you are on a Advanced Inventory Cloud implementation, for Gateway, select the gateway to use.

Step Information

Note: This field only displays for Advanced Inventory Cloud customers.
For Include path, enter the location of the header files for the EnterpriseOne business functions.
Step Information
Note:The system configuration determines whether this path is a network path or a local path.

The path for a network location must include the server name, for example, \\enterprise1\B7\PROD733\Include.

The path for a local folder includes a drive letter, for example, c:\B7\PROD733\Include. The local folder is local to the server and not the computer. Additionally, the Windows Service Account must have read access to the deployment server files for all environments.
Step Information

Note:To avoid potential problems, use the UNC naming convention. UNC consists of three parts: a server name, a share name, and an optional file path. These are combined using backslashes, as follows: \\ servername\sharename\filepath.
For Host name/address, enter the name or IP address of the computer serving as host to the system to which XML requests are sent.

Step Information

Note:This value must be specified based on the particular configuration. For example, "10.255.255.255" indicates that 10.255.255.255 is the IP address of the host computer.
For Host port, enter the network port on which the host computer communicates with the server.

Step Information

Note:This port number is specified in the JDE install.
For Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the web service when sending a request.

Step Information

Note:A default value is provided; however, it can be changed. Entry in this numeric field can range from 5 to 300 seconds. Advanced Inventory recommends a starting value of 120 seconds.
For User ID, enter the user identification that the EnterpriseOne system uses when managing profiles and permissions.
For Password, enter the EnterpriseOne password of the user seeking to use the program.
For JDE environment, enter the name of the EnterpriseOne environment that the connector uses, for example, DEMOB73. This value must match the enterprise system settings.

Step Information

Note:If you are configuring multiple environments for this installation, this value will change for each environment configuration page.
For Use JDE sessions, enable this to specify that sessions are allocated by processing threads, thereby more efficiently managing calls between the system and the enterprise software.

Step Information

Note:This setting is required for tool releases E1 8.94 and later.

Expected Result

Result: A session is established on each processing thread. Each subsequent call on the thread is sent to the established EnterpriseOne session, saving on session initiation overhead and improving performance. The system monitors the status of each session and references the session idle limit option to stop sessions when limits are reached. This option is selected by default; however, it can be changed.
For Maximum number of calls per sessions, enter the maximum number of requests allowed to use each session before the connector closes it and creates a new session.

Step Information

Note:A value of zero (0) is no limit. Advanced Inventory recommends a starting value of 1000 calls.
For Role, enter the EnterpriseOne role used to sign on to the enterprise system.

Step Information

Note:Advanced Inventory recommends using *ALL so the user uses all available roles assigned to the users.
For Session idle limit (sec), enter the amount of time (in seconds) that the session is allowed to be idle.

Step Information

Note: If the session has not had any requests processed within this amount of time, the session "times out" and is closed. The next time the session is requested to process a call, the system establishes a new session so that the call is not lost.

Step Information

Note:A default value is provided; however, it can be changed. Entry in this numeric field can range from 1 to 99999 seconds. This option can be disabled by leaving this field blank, which means that Mobile Enterprise Platform does not override the default set by the enterprise system.

Note:Advanced Inventory recommends a start value of 3600 seconds, or 1 hour, to override the JDE default session idle value. This prevents timeouts on a system where gaps in transaction processing occur.
For Log request/response documents, enable this to specify that request/response documents are logged to the Logging folder in the installation.

Step Information

Note:This field should only be enabled when troubleshooting API issues, and typically only when requested by the Advanced Inventory team. The resulting log file name format is EnterpriseOne XML_GUID.txt.
For Support Unicode, specify whether or not the installation of EnterpriseOne XML supports Unicode.

Step Information

Note:This applies to EnterpriseOne 8.9 or later.
For Use Advanced Inventory tracking ID for GUID parameter, indicate whether or not the function caller program should generate a GUID value when a business function contains a specific parameter (szGuidUniqueID_GUID) for the 32-character unique identifier.

Step Information

Note:This functionality supports FDA 21 Part 11 auditing requirements.

Expected Result

Result: The generated value is passed to the enterprise system.
For Buffer size, specify the field used to configure the size of the buffer that accepts the returned data.

Step Information

Note:The size of call outputs is unknown so the buffer size may need to be increased.
Select Save.

64-bit Tools Setup

JD Edwards is strongly encouraging that all customers upgrade to their latest 64-bit tools. We've updated our connector to accommodate this upgrade. Customers currently running version 9.0 SP12 or higher of the platform will have access to this update. On premises customers will need to coordinate with our Customer Success Center.

Once we install the update to your system, your Cloud Inventory® admin must enable the JDE tools release 9.2.4.3+ option by going to the Admin > Configuration > Connector Settings > EnterpriseOne XML Connector page. Once this option is enabled, you need to set the AIS port and check the option for Use SSL for AIS, depending on your environment.

Note:Once we install the update to your system, your Cloud Inventory® admin must enable the JDE tools release 9.2.4.3+ option by going to the Admin > Configuration > Connector Settings > EnterpriseOne XML Connector page. Once this option is enabled, you need to set the AIS port and check the option for Use SSL for AIS , depending on your environment.

Configure the Procedure Connector for Oracle

The Procedure Connector for Oracle transmits data among components and the Oracle enterprise software. When configuring this connector, specify the connection string and whether or not to log request/response documents.

To configure the Procedure Connector for Oracle, complete the following steps in Advanced Inventory Platform Manager.

Go to Admin > Configuration > Connector Settings page.
From the list of connectors, choose the Procedure Connector for Oracle.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.
For Provider, select the database provider.

Step Information

Note:If OleDB Provider for .NET is selected, the Connection String must be manually entered. It cannot be built here.
If you are on a Advanced Inventory Cloud implementation, for Gateway, select the gateway to use.

Step Information

Note: This field only displays for Advanced Inventory Cloud customers.
For Connection string, enter a string that contains information about a data source and the means of connecting to it.
Select Log request/response documents in order for request/response documents to be logged to the Logging folder in the installation.

Step Information

Note:The document name format to which they are logged is: Oracle Procedure_GUID.txt.
For Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the web service when sending a request.

Step Information

Note:A default value is provided; however, it can be changed. Entry in this numeric field can range from 5 to 300 seconds.
Select Save.

Configure the Lawson Connector

The Lawson Connector enables communication with the Lawson M3 Enterprise Management System.

To configure the Lawson Connector, complete the following steps in Advanced Inventory Platform Manager.

Go to Admin > Configuration > Connector Settings page.
From the list of connectors, choose the Lawson Connector.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.
If you are on a Advanced Inventory Cloud implementation, for Gateway, select the gateway to use.

Step Information

Note: This field only displays for Advanced Inventory Cloud customers.
For Lawson user ID, enter the user identification for accessing the Lawson application server.

Step Information

Note:Ensure the user ID specified is assigned to a valid user profile for the enterprise environment for which the connector is being configured.
For Password, enter the password of the user requesting access to the app server.
For Host name/address, enter the server name or IP address of the Lawson application server (host system) to which the system makes function calls.
For Host port, enter the TCP/IP socket port on which the Lawson application server (host system) listens for incoming messages.

Step Information

Note:Use the default setting, either 6000 (ThisGen) or 6800 (NextGen), or contact your enterprise system administrator.
For Repository program, enter the name of the Lawson API repository.

Step Information

Note:If necessary, qualify the entry with a library name as well.
For Encryption key, enter the Lawson encryption key used to secure system communications.

Step Information

Note:This value must exactly match the key specified in the host environment to ensure system interoperability. If no encryption key is specified for the host environment, leave this field blank.
For API library, ensure the API library specified corresponds with the enterprise environment for which the connector is being configured.

Step Information

Note:This is the name of the library on the Lawson application server (host system) in which the function calls reside.
Select Log request/response documents to specify that request/response documents are logged to the Logging folder in the installation.

Step Information

Note:The document name format to which they are logged is: Lawson_GUID.txt.
For Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the web service when sending a request.

Step Information

Note:A default value is provided; however, it can be changed. Entry in this numeric field can range from 5 to 300 seconds.
Select Save.

Configure the Microsoft Dynamics AX Connector

The Microsoft Dynamics AX Connector transmits data among components and the Microsoft Dynamics AX enterprise software.

Prerequisite: To configure this connector, Microsoft Dynamics AX and ScanworkX Server must already be installed. Additionally, the required licenses must be installed.

To configure the Microsoft Dynamics AX Connector, complete the following steps in Advanced Inventory Platform Manager.

Go to Admin > Configuration > Connector Settings page.
From the list of connectors, choose the Microsoft Dynamics AX Connector.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.
For Dynamics AX connector, enter the name of the computer serving as host to the Dynamics AX AOS system. This value must be specified based on the particular configuration.
For Dynamics AX WSDL port, enter the network port on which the host computer communicates with the server. This port number is specified in the Dynamics AX connector install. The default port number is 8201.
For Dynamics AX UPN, enter the User Principal Name that is used by Dynamic AX when managing profiles and permissions. Additionally this needs to be a ScanWorkX user.
For Dynamics AX UPN domain, enter the User Principal Name domain that the Dynamics AX system uses when managing profiles and permissions.
For ScanWorkX host name, enter the name or IP address of the computer serving as host to the system to which requests are sent. This value must be specified based on the particular configuration.
For ScanWorkX port, enter the network port on which the host computer communicates with the server. This port number is specified in the ScanWorkX install. The default port number is 20001.
Select Log request/response documents, to specify that request/response documents are logged to the Logging folder in the installation. The document name format to which they are logged is: Microsoft Dynamics AX_(GUID).txt (The GUID section will vary). This is a transaction ID which should be unique.
For Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the web service when sending a request. A default value is provided; however, it can be changed. Entry in this numeric field can range from 5 to 300 seconds.
Select Save.

Configure the Oracle Web Services Connector

The Oracle Web Services Connector allows communication with the Oracle Application Integration Architecture, which integrates any combination of custom, Oracle, and non-Oracle applications into business processes.

To configure the Oracle Web Services Connector, complete the following steps in Advanced Inventory Platform Manager.

Go to Admin > Configuration > Connector Settings page.
From the list of connectors, select the Oracle Web Services Connector.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.
If you are on a Advanced Inventory Cloud implementation, for Gateway, select the gateway to use.

Step Information

Note: This field only displays for Advanced Inventory Cloud customers.
For WSDL file location, enter the location of the WSDL file. The .WSDL file describes the application interface methods that the system can call when sending data to the TIMETrac module, such as method names, parameters, and data types.
For Log request/response documents, select this box to request/response documents are logged to the Logging folder in the installation. The document name format to which they are logged is: AIAFC_GUID.txt.
For Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the web service when sending a request. A default value is provided; however, it can be changed. Entry in this numeric field can range from 5 to 300 seconds.
Select Save.

Configure the SAP .NET Connector

The SAP .NET Connector transmits data among components and the SAP enterprise software. When configuring this connector, elements are specified, such as include the app server, system number, and system user name and password.

To configure the SAP .NET Connector, complete the following steps in Advanced Inventory Platform Manager.

Go to Admin > Configuration > Connector Settings page.
From the list of connectors, select the SAP .NET Connector.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.
If you are on a Advanced Inventory Cloud implementation, for Gateway, select the gateway to use.

Step Information

Note: This field only displays for Advanced Inventory Cloud customers.
Select the Logon Type from the drop-down menu and complete one of the following options.
- If Single Logon is selected, complete the following fields.
  - For Application server, enter the name or IP address of the computer serving as a gateway host to the SAP system. The gateway host is the computer on which the gateway server runs and may be the same as the host computer. This value must be specified based on the particular configuration. For example, "10.255.255.255" indicates that 10.255.255.255 is the IP address of the computer.
  - For System number, enter the system number based on the enterprise configuration, for example, 00. If necessary, the basis administrator (enterprise system administrator) can provide this value.
- If Group Logon is selected, complete the following fields.
  - For Message server, enter the host name of the SAP system's message server (central instance).
  - For Message server service, enter the service name (as defined in etc/services) or the port number under which the message server is listening for load- balancing requests.
    Note:Usually this parameter can be omitted. By default RFC uses the service name “sapmsABC”, where ABC is the system ID of the SAP system.
  - For System ID, enter the SAP system's three-letter system ID.
  - For Logon Group, enter the logon group, from which the SAP system's message server shall select an app server.
For Client, enter the name of the enterprise environment to use when connecting to the SAP system.

Step Information

Note:Generally, only one environment is the production or "live" environment. There can also be other environments with access to other subsets of data, for example, for development and testing.
For User ID, enter user identification that the SAP system uses when managing profiles and permissions.
For Password, enter the SAP password of the user seeking to use the program. Entry in this field is hidden by asterisks, so the password is not readable.
For Supports Unicode, specify whether or not the installation of SAP supports Unicode.
For Log request/response documents, specify whether or not the request/response documents are logged to the Logging folder in the installation.

Step Information

Note:The document name format to which they are logged is SAP_(GUID).txt. (The GUID section will vary. This is a transaction ID which should be unique).
For Auto commit, select and complete one of the following options.
- If None is selected, then no calls are auto-committed by Mobile Enterprise Platform. The BAPIs called are responsible for committing data.
- If Per Function Call is selected, then all new functions that are registered will have an extra parameter for Auto commit that can be set when the function is called.
  - If parameter is set to 1 (true), then BAPI CommitWork is called immediately after the requested function is called. If a failure is detected, such as a communications failure, system failure, etc., then CommitWork is not called.
- If All is selected, then every call through the SAP .NET Connector will call CommitWork as if the Auto commit parameter was set to 1 (true). This, however, will not happen if an error is detected.
  - This option overrides any calls where the Auto commit parameter is set to 0.
For Language, select the logon language to be used. This setting is configured in SAP.
For Idle Time-out (seconds), enter the seconds for the idle time-out.

Step Information

Note:If a connection has been idle for more than the Idle Time-out seconds, it will be closed and removed from the connection pool. This setting is configured in SAP.
For Pool Size, enter the maximum number of RFC connections that this destination will keep in its pool as set in the SAP system.

Step Information

Note:More connections can be opened (until MaxPoolSize) is reached, but they are closed again immediately after usage. This setting is configured in SAP.
For Max Pool Size, use the parameter that is set in the SAP system.

Step Information

Note:In order to prevent an unlimited number of connections to be opened (which, from a certain point on, would cause the entire machine's performance to deteriorate dramatically). NCo will not open further connections for this destination when this limit is reached. This setting is configured in SAP.
For Trace, set a trace level for this specific destination or server. This setting is configured in SAP.
ABAP Debug can be used for R/3 systems with release 6.20 and above, where "external breakpoints" are not yet available.

Step Information

Note:The connections are opened in debug mode and the invoked function module can be stepped through in the debugger. This setting is configured in SAP.
For CPIC Trace Level, use this trace level for all destinations and servers, which do not define their own trace level. CPIC Trace Level is also used for writing traces in those deeper level layers of NCo, which are not directly related to a particular destination or server and consequently cannot use a destination/server trace level for their trace output. Select one of the following options.
- None/”0”: no tracing
- Level1/”1”: trace all function calls
- Level2/”2”: function calls and public API calls
- Level3/”3”: function calls, public API calls and internal method calls
- Level4/”4”: function calls, public API calls, internal method calls and network hex dump
Select Save.

Configure the Webservices Connector

The Webservices Connector enables integration with external systems via standards-based Web service APIs. The basic connector is configured here. The API registration to define the web server and port for API execution, and additional fields are done in Application Studio > Service Definitions.

To configure the Webservices Connector, complete the following steps in Advanced Inventory Platform Manager.

Go to Admin > Configuration > Connector Settings page.
From the list of connectors, select the Webservices Connector.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.
For Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the web service when sending a request.

Step Information

Note: A default value is provided; however, it can be changed. Entry in this numeric field can range from 5 to 300 seconds.
For Detailed logging, select this box to log the communication between the source and the Webservices Connector.
Select Save.

Configure the TIMETrac Connector

TIMETrac is a module that gathers time and labor data from Advanced Inventory Platform system and sends it to the enterprise software. When configuring this connector, specify elements such as WSDL file location, Web services password, and time-out. Other servers might have different configurations.

For example, one server might use a WSDL file residing in a different location from other servers. The TIMETrac connector receives transactions from time clocks and other devices and moves them to TIMETrac using the TIMETrac web service.

To configure the TIMETrac Connector, complete the following steps in Advanced Inventory Platform Manager.

Go to Admin > Configuration > Connector Settings page.
From the list of connectors, select the TIMETrac Connector.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.
If you are on a Advanced Inventory Cloud implementation, for Gateway, select the gateway to use.

Step Information

Note: This field only displays for Advanced Inventory Cloud customers.
For WSDL file location, enter the location of the WSDL file.

Step Information

Note:The WSDL file describes the application interface methods that the system can call when sending data to the TIMETrac module, such as method names, parameters, and data types.
For Web service password, enter the password for the web service, which must accompany all transactions passed to the TIMETrac web service.

Step Information

Note:This password is used by the system to access the TIMETrac web service.
For Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the web service when sending a request.

Step Information

Note:A default value is provided; however, it can be changed. Entry in this numeric field can range from 5 to 300 seconds.
For Log request/response documents, select this box to request/response documents are logged to the Logging folder in the installation.

Step Information

Note:The document name format to which these are logged is: TIMETrac_GUID.txt.
Select Save.

Configure the Facebook Connector

The Facebook Connector transmits data among components and the Facebook social network. When configuring this connector, elements are specified, such as client ID, and client secret.

Note:Facebook connectors are no longer supported functionality as of 9.5.5. This information is provided for legacy versions.

Prerequisite: An administrator must have already created a Facebook app with asynchronous function calls.

To configure the Facebook Connector, complete the following steps in Advanced Inventory Platform Manager.

Go to Admin > Configuration > Connector Settings.
From the list of connectors, select Facebook Connector.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.
If you are on a Advanced Inventory Cloud implementation, for Gateway, select the gateway to use.

Step Information

Note: This field only displays for Advanced Inventory Cloud customers.
For App ID, enter the random ID string created for the user by Facebook. The app ID is generated only once.
For App Secret, enter the string that is populated when sign-in is successful. The Facebook API sends this token which is then used for user authentication.
Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the Web service when sending a request. A default value is provided; however, it can be changed. Entry in this numeric field can range from 5 to 300 seconds.
Once the information in the previous fields has been entered, select Login with Facebook.
The Access token field is populated when sign in is successful. The Facebook API sends this token which is then used for user authentication.
For Detailed logging, enable this box to log the communication between Facebook and the Mobile Enterprise Platform.
Select Save to save the settings.

Step Information

Note:If any changes or updates are made in the Facebook account, it is necessary to get a new Access Token for the connector to work.

Postrequisite: After you configure the Facebook Connector, you can create functions and use function calls in Mobile Enterprise Platform apps to post to Facebook.

Configure the Twitter Connector

The Twitter Connector transmits data among components and the Twitter social network. When configuring this connector, elements are specified, such as client ID, and client secret.

Note:Twitter connectors are no longer supported functionality as of 9.5.5. This information is provided for legacy versions.

Prerequisite: An administrator must have already completed Twitter setup.

To configure the Twitter connector, complete the following steps in Advanced Inventory Platform Manager.

Go to Admin > Configuration > Connector Settings page.
From the list of connectors, select the Twitter Connector.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.
On the Twitter Connector page, select Sign in with Twitter to access the Twitter application and account that was created and use the information to complete the following fields.

Advanced Inventory

For Consumer key, enter the random key string created for the user by Twitter.

Step Information

Note: The company administrator will obtain this information when creating the app in Twitter. The consumer key can be reset by the company administrator through the Twitter application manager.
For Consumer secret, enter the random secret string created for the user by Twitter.

Step Information

Note: The company administrator will obtain this information when creating the app in Twitter. The consumer secret can be reset by the company administrator through the Twitter application manager.
For Access token, enter the specific token string created for the user by Twitter to gain access to and use the Twitter's application API.

Step Information

Note: The company administrator will obtain this information when creating the app in Twitter. The Access token can be recreated by the company administrator through the Twitter application manager.
For Access token secret, enter the specific secret string created for the user by Twitter to gain access to and to use the Twitter's application API.

Step Information

Note: The company administrator will obtain this information when creating the app in Twitter. The Access token secret can be recreated by the company administrator through the Twitter application manager.
For Detailed logging, select this box to log the communication between Twitter and the Mobile Enterprise Platform.
For Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the web service when sending a request.

Step Information

Note: A default value is provided; however, it can be changed. Entry in this numeric field can range from 5 to 300 seconds.
Select Save.

Postrequisite: After configuring the Twitter Connector, you can create functions and use function calls in Mobile Enterprise Platform apps to post to Twitter. Note that Function Calls for Twitter must be asynchronous.

Configure the Yammer Connector

The Yammer Connector transmits data among components and the Yammer social network. When configuring this connector, elements are specified, such as client ID, and client secret.

Note:Yammer connectors are no longer supported functionality as of 9.5.5. This information is provided for legacy versions.

Prerequisite: An administrator must have already created a Yammer app.

To configure the Yammer connector, complete the following steps in Advanced Inventory Platform Manager.

Go to Admin > Configuration > Connector Settings page.
From the list of connectors, select the Yammer Connector.
If the system interfaces with multiple enterprise environments, also choose the environment for which to configure the connector.

Advanced Inventory

For Client ID, enter the random ID string created for the user by Yammer.

Step Information

Note:The client ID is generated only once. The company Admin will obtain this information when creating the app in Yammer.
For Client secret, enter the random secret string created for the user by Yammer.

Step Information

Note:The client secret is generated only once. The company Admin will obtain this information when creating the app in Yammer.
For Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the web service when sending a request. A default value is provided; however, it can be changed. Entry in this numeric field can range from 5 to 300 seconds.
Select Save.

Postrequisite: After you configure the Yammer Connector, you can create functions and then use function calls in Mobile Enterprise Platform apps to post to Yammer. Note that Function Calls for Yammer must be asynchronous.

There was a problem loading this topic