--- title: AS400 description: AS400 is a mainframe on-premises computer and database that can store identity data. The AS400 application enables you to manage and synchronize users between AS400 and Advanced Identity Cloud. The application can only be a target application. component: pingoneaic page_id: pingoneaic:app-management:applications/as400 canonical_url: https://docs.pingidentity.com/pingoneaic/app-management/applications/as400.html page_aliases: ["release-notes:rapid-channel/as400-connector.adoc"] section_ids: register_the_application: Register the application configure_provisioning: Configure provisioning provision_side_tabs: Provision side tabs next_steps: Next steps --- # AS400 AS400 is a mainframe on-premises computer and database that can store identity data. The AS400 application enables you to manage and synchronize users between AS400 and Advanced Identity Cloud. The application can only be a [target application](../applications.html#target_and_authoritative_applications). The following instructions assume you have access to an AS400 instance as an administrator. ## Register the application 1. In the Advanced Identity Cloud admin console, go to Applications, and click [icon: grid_view, set=material, size=inline] Browse App Catalog. 2. In the Browse App Catalog modal, select an application, and click Next. 3. Review the Application Integration information, and click Next. 4. In the Application Details window, specify the name, description, application owners, and logo for the application. 5. To make the application an [Authoritative](../applications.html#target_and_authoritative_applications) source of identity data, select the Authoritative check box. This option is not available for every application. 6. Click Create Application. ## Configure provisioning After you register the application, you can configure provisioning. 1. Set up a [remote connector server (RCS)](../../identities/sync-identities.html). 2. Set up the [AS400 connector](https://docs.pingidentity.com/openicf/connector-reference/as400.html#install_the_as400_connector) with your RCS. 3. In the Advanced Identity Cloud admin console, on the Provisioning tab: * If setting up provisioning for the first time, click Set up Provisioning. * When editing existing settings in the Connection area, click Settings. 4. Configure the following fields: | Field | Description | | --------- | ------------------------------------------------------------------------------------ | | Host Name | Host name or IP address of AS400. | | User Name | The username to log in to AS400. | | Password | The password to log in to AS400. | | Use SSL? | Enable to use SSL to connect to the AS400 application. The default value is `false`. | 5. Optionally, click Show advanced settings to set any of the following options: **Application specific settings** | Option | Description | | ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | Maximum Connections (optional) | The maximum number of connections. | | Maximum Lifetime (optional) | The maximum time for an available connection to exist. The default value is 86400000 milliseconds. | | Maximum Inactivity (optional) | The the maximum amount of inactive time before an available connection closes. The default value is 3600000 milliseconds. | | Maximum Use Time (optional) | The maximum time a connection can be in use before it closes. The default value is `-1` which indicates that there is no time limit. | | Maximum Use Count (optional) | The maximum number of times a connection can be used before it is replaced in the pool. The default value is `-1` which indicates that there is no limit. | | Is run Maintenance | Indicates whether the maintenance thread is used to cleanup expired connections. The default is `true`. | | Is thread used | Indicates whether threads are used in communication with the host servers and for running maintenance. The default is `true`. | | Cleanup Interval (optional) | Specifies how often the maintenance daemon runs. The default value is 300000 milliseconds. | | Exclude Unmodified | Select this option to synchronize only the modified properties on a target resource. | **Pool configuration** | Field | Description | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Max idle and active container instances | The maximum number of idle and active container instances. The default value is `10`. | | Max Idle Connector Instances | The maximum number of idle connector instances. The default value is `10`. | | Set Timeout Period | Select to enable a timeout period for the connection. After enabling, configure the following:- Timeout period (ms): The timeout period in milliseconds. | | Set Minimum Idle Time | Select to set a minimum time (in milliseconds) before an idle object is removed. After enabling, configure the following:- Min idle time (ms): The minimum idle time in milliseconds. | | Min Idle Instances | The minimum number of idle connector instances. | **Result Handler configuration** | Field | Description | | ----------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | Enable for connectors with the attribute normalizer interface | Enables the attribute normalizer interface for supported connectors. | | Enable local filtering/search features | Enables local filtering and search capabilities. | | Enable case insensitive filter | Configures filters to ignore case sensitivity. | | Enable configuration of search attributes; disable for local connectors | Enables search attribute configuration. Disable this option for local connectors. | 1. In the Operation Timeouts (ms) area, select the operations to enforce timeouts on and enter the duration in milliseconds. Available operations include Create, Validate, Test, Enable a Script on the Connector, Schema, Delete, Update, Sync, Authenticate, Get, Enable a Script on the Target, and Search. 2. In the Operation Rate Limits area, select the operations to enforce rate limits on. You can enforce limits on specific operations, including Create, Validate, Test, Script on Connector, Schema, Delete, Update, Sync, Authenticate, Get, Script on Target, and Search. For each selected operation, configure the following fields: | Field | Description | | --------------- | ---------------------------------- | | Request Limit | Requests allowed over time. | | Request Period | Limit resets after this time (ms). | | Request Timeout | Time before exception thrown (ms). | 6. Click Connect. 7. Verify the information in the Details tab. ## Provision side tabs The object type determines the side tabs that display on the Provisioning tab. Use the object type list to select an object type, such as `Group`. Afterward, you can configure properties in the different sub-tabs under the Provisioning tab. ![Sub-tabs under the Provisioning tab](../_images/ui-workforce-provisioning.png) | Provisioning tab | Description | Related sections | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | Details | View and manage an application, including name, ID, and native type. | Select the specific application from [Provision settings for an application](../provision-an-application.html#provision_settings_for_an_application). | | Properties | View and manage properties for the selected object type. | [Manage application attributes](../provision-an-application.html#manage_application_attributes) | | Data | View data about the selected object type. | [View user access data](../provision-an-application.html#view_user_access_data) | | Mapping | View and manage mappings from the Advanced Identity Cloud admin console properties to external system properties and from external system properties to the Advanced Identity Cloud admin console properties. | [Manage mappings](../provision-an-application.html#manage_mappings) | | Reconciliation | Preview mappings on target applications between external systems and the Advanced Identity Cloud admin console, and reconcile the data between the two systems.View and manage rules for the users and groups that use your application.View and manage schedules for Full and Incremental reconciliation. | [Reconcile and synchronize end-user accounts](../provision-an-application.html#recon-sync-end-users) | | Privacy & Consent | Manage end-user data sharing and synchronization. | [Configure end-user data sharing](../provision-an-application.html#config-end-user-data-sharing) | | Rules | View and manage provisioning rules for mappings between Advanced Identity Cloud and a target application. | [Manage provisioning rules](../provision-an-application.html#manage-provisioning-rules) | | Advanced Sync | Create and manage mappings between a managed object type and an application or between applications. | [Manage advanced sync](../provision-an-application.html#manage-advanced-sync) | ## Next steps * [icon: check-square-o, set=fa][Application management](../applications.html) * [icon: check-square-o, set=fa][App catalog](../app-catalog.html) * [icon: check-square-o, set=fa][Register an application](../register-an-application.html) or [Register a custom or SSO application](../register-a-custom-application.html) * [icon: check-square-o, set=fa][Provision an application](../provision-an-application.html) * [icon: square-o, set=fa]*[Manage end users and roles](../manage-users-and-roles.html)* * [icon: square-o, set=fa][Manage application registrations](../manage-app-status.html)