Source Configuration of Database Importer for JSM Assets
To integrate with external Databases, you first need to define sources.
You will need the Database Administrator's and Network Administrator’s help with the following configuration.
Select Source Tab.
2. You will be presented with a list of supported database types:
PostgreSQL
MySQL
Microsoft SQL Server
Oracle
Aurora MySQL
Aurora PostgreSQL
|
Select the database type that matches your data source by clicking on it.
Please contact a Database Admin for the database-related information below.
Give a name to your source and enter the following:
Region - US (us-east-1) or EU (eu-central-1).
Database Address
Username and Password
Database Name
Query - SQL query to retrieve data from your database.
Contact your Security Team and request them to allow access to your database from the Pio Database Gateway according to the security recommendation.
Pio Region Name | Service Provider | Location | Region Description | Public IP Address for Outbound Traffic |
|---|---|---|---|---|
US | AWS | North America (Virginia, US) | us-east-1 | 52.45.180.198 |
EU | AWS | Europe (Frankfurt, Germany) | eu-central-1 | 18.199.1.227 |
Depending on the database you would like to connect to, please allow the TCP ports on your network's firewall/router.
Database | TCP Port |
|---|---|
MySQL | 3306 |
PostgreSQL | 5432 |
Microsoft SQL Server | 1433 |
Oracle | 1521 |
Click Add Source to add the source configuration.
A success message will appear if the connection settings are correct, and the total number of table rows will be displayed.
If you encounter a 500 Internal Server error, it may indicate a connection issue. To troubleshoot, first check the logs located under the Admin Tab. Next, verify your network configuration to ensure that it accepts requests from the specified IP addresses listed above.
12. Click the “Close” button to return to the list of sources.
Click the “Create Schema” button to configure the table columns. Review each table column and update the configuration if necessary through the Edit Schema option.
Object Type Name: Give a name for your new Object Type, which our application will create automatically in the later steps.
Due to the design of the Atlassian Assets, it is mandatory for our application to create the object type. It is not allowed to use an existing Object Type. Please make sure that there is no existing Object Type with the same name in case you plan to use an existing object schema. (The Object Schema setting is in the Destination configuration step.)
Attribute Name: The attribute name is listed as the column name according to the result of your SQL query. You have the chance to change it in this step in case you need to make it more user friendly or better fitting to JSM context.
Type: The default is Text. You can change it to another attribute type if needed, such as Status, URL, Integer, Boolean, etc.
Label: You can select the Yes option for one of the attributes to set it as Label. The Label of the Object is displayed on the ticket view when the object is selected.
Unique: You can select the Yes option to enable unique constraints for the attribute.
External ID: If the attribute is the unique identifier (or, in other words, the primary key of your table), you can select Yes.
|
If you want to create referenced attributes and map them to other object types in your Assets environment, please find the steps on the following page:
Click the “Save Configuration” button once you finalize updating the attribute settings.
After the success message, click “Close” to return to the list of sources.
Repeat these steps if you need to create more source configurations.
Select the Destination tab to configure your destinations once the Source Configuration is complete.