Creating a new data store connection in Atrium Integrator
Consider the following when creating data store connections:
- For XML and CSV connection, if there are too many files in the folder, check if the fields from these files are populated in NGIE:FileMetaData file before you create a job.
- For XML and CSV connection, do not add files under root folder.
- For database connection, if you plan to create a transformation with Response enabled, ensure that user has permissions to access the associated tables in the data base.
- You can create a CSV or XML datastore connection with a remote Atrium Integrator Carte server.
To support this capability, Job_FileMetaLoader job is added to Atrium Integrator sample jobs. Do not delete this job or you will not be able to create CSV or XML datastore connection with Atrium Integrator Carte server. For more information, see Using Atrium Integrator sample jobs.
To create data store connection
- In the BMC Remedy AR System Home Page, select BMC Atrium Integrator > Atrium Integrator.
The Atrium Integrator console appears. - Click Manage Data Store Connections
.
The Manage Data Stores window appears, with a list of defined data sources.
Manage Data Stores window
- Click New Data Store
The New Data Store section appears on the right side of the Manage Data Stores window.
New Data Store section of the Manage Data Stores window
Select the Data Store Type.
The fields below the Data Store Type change depending on the data store that you selected.Note
You must specify only the server name, and not the fully qualified domain name, in the Database Host Name field.
- To create a connection to BMC Remedy AR System, complete the following steps. To create a connection to a CSV or XML file, skip to step 6. To create a connection to a database, skip to step 7.
- Type a name for the connection.
- In the AR Server Name field, type the name of your BMC Remedy AR System server.
- (optional ) In the Port field, type the port number.
(optional) Type the port number.
Note
You can specify a private RPC Program Number for data transfers into BMC Atrium CMDB through BMC Atrium Integrator Spoon. You must use the ports defined by BMC Atrium CMDB. For more information about the RPC ports defined by BMC Atrium CMDB, see RPC ports in BMC Atrium CMDB.
- Type the password to log on to BMC Remedy AR System.
To create a connection to a CSV or XML file, complete the following steps:
Note
You must structure your XML source file based on the sample PULL_MONITOR.xml file that is located in the ARInstallationDirectory\diserver\data-integration\NGIE-Sample directory.
- In the Data Store Name field, type a name for the connection.
- In the Directory Path field, specify the path to the folder that contains the source file.
- From the Carte Server drop-down list, select the Atrium Integrator Carte server.
- Click Refresh to get the latest file.
- If space is used in a field or column in the CSV or XML file then the space is replaced by an underscore.
- The source files must be on the same computer on which you have installed the Atrium Integrator server.
- For an XML connection, duplicate attributes will be renamed with an underscore and copy number( attribute name1, _attribute name_2 and so on)
- To create a connection to a database, complete the following steps:
Creating a connection to a database
## - Type a name for the connection.
- Enter the host name.
- Specify the database type.
- Enter the name of the database you want to connect to.
The default port for the specified database is displayed. - (optional ) For a SQL Server database, type the instance name.
- Type the user ID and password to log on to the database.
- Click Test Connection to verify the connection parameters.
Click Save.
The data store connection is created and displayed in the Data Stores section on the left side of the Manage Data Stores window. Each connection has an icon attached to it depending on the data store type, as described in the following table.
Icons associated with data storesIcon
Associated data store type
AR System
CSV file
XML file
Database
Click on a data store to view the connection parameter details for that source.
Comments
NGIE:FileMeta ??
can you give some context to this? In what way (and for what reason) do I need to "check if the fields from [my csv data files] are populated" into this form?
Hello Andrew,
Thank you for your comment. I will verify this with the concerned SME and get back to you.
Thanks,
Prachi
Hello Andrew,
Thank you for your comment.
Fields are created for every row in the CSV file. Thus when saving the form, it could so happen that all the fields might not get saved due to refresh or sync issues. Hence, before creating new data store connection, it is advisable to check if the fields are populated properly into the form.
Hope this helps.
Regards,
Amol
the text from this page that I have a question about:
>> "For XML and CSV connection, if there are too many files in the folder, check if the fields from these files are populated in NGIE:FileMeta file before you create a job."
is this the form you meant?
Your response above is incomprehensible. Please respond to these specific questions:
>> Fields are created for every row in the CSV file.
What fields? Do you mean fields on the NGIE:FileMetaData form (like the way that Atrium Class Manager can dynamically change the definition of the CMDB class forms?). Like Atrium Integrator will dynamically change this form to add fields corresponding to every input file in the directory?
are you sure? That's highly unusual ... if that is the case, why is it not mentioned in the documentation? That seems like a pretty important thing to understand?
>> Thus when saving the form, it could so happen that all the fields might not get saved due to refresh or sync issues.
what? Why would I be saving the form? Do you mean I need to modify the NGIE:FileMetaData form in Dev-Studio? Why would I be doing that, and for what reason? Perhaps that's something worth mentioning in this documentation?
>> Hence, before creating new data store connection, it is advisable to check if the fields are populated properly into the form.
What fields. What form. What does "properly" even mean in this context?