Book a Demo

Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

WebConfig - Add or Edit an Integration Data Provider

The 'Add Data Provider' and 'Edit Data Provider' screens allow you to configure an Integration Data Provider. The options provided are the same in both cases, except that when editing you cannot modify the Provider and Prefix.

Wherever possible the Add/Edit Data Provider screen will fill each field with a default value in order to make it easier for you; if the default values are not correct, simply overwrite them.

The Integration settings are broken up into a number of groupings.

Data Provider

This group of settings contains the basic information to identify the Data Provider and determine how the Plug-in communicates with the Provider Server.



See also


This value controls if the Integration Server (SBPI.exe) should allow communications to be forwarded to this Data Provider.


This value represents the friendly name for the current Data Provider, it will be shown to users of Enterprise Architect.


This value specifies the Provider type of the current Data Provider.  When this value is changed a number of other fields could be automatically updated.


This field is available only when the 'Custom Integration' provider type is selected.

Typically in Enterprise Architect, integrations are grouped by the Provider type (such as 'Jira' or 'Dropbox'). For Custom Integrations, the Grouping is applied based on the value entered in this field.


This value represents a short unique name to identify the current Data Provider.  This value will be saved against every Enterprise Architect element that is linked to an external element.

Auto Start

This value controls if the Integration Server (SBPI.exe) should maintain a running process (*sbpi.exe) for this Data Provider. 

For standard Integration Plug-ins we would expect this value to be checked; however, for custom ones it might be useful to not auto-start the Plug-in and instead manually control when it is running, particularly while developing it.


This value represents the Port that the Integration Server should use to communicate with the Integration Plug-in.  The Integration Server assumes the Port is relative to the current machine (or http://localhost:{port}).

Each Integration Plug-in requires a unique Port number, which will be checked when an attempt is made to save the Plug-in's settings.  However the Pro Cloud Server can only check what Ports are in use by the Pro Cloud Server itself and its components, there is still a possibility of a Port clash with other applications.

DLL Path

This field is only available for 'Custom Service' and 'Custom Integration' provider types.

This value represents the physical path to the custom DLL, that will be called by the CustomService.exe or CustomIntegration.exe Data Provider processes.

Custom Properties

The Custom Properties section is only shown for Data Providers of type 'Custom Service'. This table allows you to define Item/Value pairs that can be used by the Custom Service.



See also


The 'name' of the custom property.


The value of the custom property.


This column provides Action buttons which apply to the property in this row.

Accept New Custom Property - This appears when adding or editing a property. Click this button to save the Item/Value.

Edit Custom Property - Click this button to allow editing of the property's item/value.

Delete Custom Property - Click this button to delete the property.

Provider Server

This group of settings relates to the details of the external data provider, such as Dropbox or Jira.  The Integration Plug-in will use the defined details to connect to the remote system and retrieve data from it so that it can be sent back to Enterprise Architect.  The combination of Protocol, Server Name and Port must be resolvable by the server hosting the Integration Plug-in, which in the simplest case is the Pro Cloud Server.



See also

Provider URL

The Provider URL consists of these four fields, which make up the URL that the Plug-in will use to access the external data.

  • Protocol - The Protocol to be used
  • Server Name/IP - The Server Name or IP address
  • Port - The Port to be used; if the data is typically accessed using a URL without a Port, then enter the default Port value (80 for HTTP or 443 for HTTPS)
  • URL Folder - Some external Data Providers allow for the concept of multiple repositories at a single location; for such Data Providers this field acts as a filter

For example, it is possible to use another Enterprise Architect model as an external data source; in this case the 'Protocol', 'Server' and 'Port' determine the Pro Cloud Server (for example, http://myEAServer:804) while the 'URL Folder' is the DB Alias of the repository (myModel). Thus:


Below these fields is a label showing the full URL that will be used by the Plug-in (based on the values that have been entered).

Ignore SSL Errors

This option is only displayed if the protocol 'HTTPS' has been selected.

This checkbox controls if the Integration Plug-in should ignore SSL related errors that occur as a result of communicating with the external system.


This value represents the user name that should be used (in combination with the password) to access the data within the external system.  If a value is defined in this field all Enterprise Architect users of the current Data Provider will use the same set of credentials to read the external system. Otherwise if the user name field is left empty, Enterprise Architect will prompt each user independently for their credentials.


This value represents the matching password for the specified user name.

Create Items

This checkbox controls if Enterprise Architect users are able to create new items within the external system.

Modify Items

This checkbox controls if Enterprise Architect users are able to modify the details of external items within the external system.

Post Discussions

This checkbox controls if Enterprise Architect users are able to create discussions against elements within the external system.

Maximum Request Time (sec)

This value represents the maximum amount of time (in seconds) that calls to the Provider system will wait before timing out.  Increasing this value is particularly useful when the Provider systems are remote or have slow performance.

The default value is 60 seconds.

Note: This is a new setting introduced in Pro Cloud Server v4.2 build 65.


This group of settings relates to how the Integration Plug-in will create entries in its log file(s). Since the Integration Plug-ins run without user intervention, it is important for them to be able to write any messages or potential problems to a log file.  However, special consideration must be given to ensuring that performance isn't impacted by writing to such files, which is possible if the log file continually grows without limits.  It is also unreasonable to expect that manual intervention should be required to ensure that the size and number of log files don't impact performance. For these reasons each Integration Plug-in has its own set of log files and configuration options to manage its log files.

The current log file will always include a '1' on the end of its filename.  A new log file will be created whenever the Integration Plug-in is started or the physical size of the current log file reaches the Max File Size.  When this occurs all existing files will be 'rolled over', meaning their file numbers will be incremented and a new '{filename}1.log' created.  If the roll over process causes more files to exist than the 'File Count' setting allows, these additional files will be deleted.



See also

File Count

Default value:  3

This value represents the 'rolling' number of log files that should be retained for the current Integration Plug-in.

Max File Size

Default value:  1048576

This value represents the maximum number of bytes a log file can be before a new one is created.


Default value:   WARNING

This value represents the maximum level of messages that should be written to the log file. The levels are: OFF, FATAL, WARNING, INFO and SYSTEM.  A defined log level is inclusive of all lower levels, therefore if a Plug-in is set to a log level of INFO then all FATAL, WARNING and INFO messages will be written to its log file.


(READ-ONLY) This field displays the physically location of where the log files for the current Data Provider will be saved.


This group of settings relate to how the Integration Plug-in should communicate with the External Data Provider when they are separated by a Proxy Server.



See also

Server Name/IP

The server name (or IP) and Port number of the Proxy Server. For example,


This field provides a mechanism for certain addresses to bypass the proxy; it accepts multiple values separated by semi-colons (;).  For example, 192.168.*;*;

User Name

If the Proxy Server requires credentials, then enter the user name into this field.


If the Proxy Server requires credentials, then enter the password into this field.

Learn more