Information Systems:Iptor Integrator - Revision history

Norwinu: Remove HikariCP info

2021-06-03T20:16:58Z

Remove HikariCP info

2021-06-02T00:28:35Z

Removed classpath tip

2021-06-01T23:34:22Z

Important files and folders

2021-05-28T16:47:02Z

Add bit about classpath

2021-05-28T16:46:50Z

Tips

2021-05-28T16:46:03Z

Add bit about classpath

2021-05-28T00:53:08Z

2021-05-27T18:25:46Z

2021-05-13T19:59:36Z

Moved Tips and Tricks to own page

2021-03-23T18:21:40Z

@@ Line 65: / Line 65: @@
 ===Database Connection Pool===
-A database connection pool is a pool of connections to a database that is usable by programs. The idea is to provide central management of connections (through a pool manager) such as limiting the total number used at any one time and ensuring that connections don't remain open. This feature is not being used currently because it requires a commitment to the rest of the database facilities in Integrator, which requires training/instruction from Iptor.
+A database connection pool is a pool of connections to a database that is usable by programs. The idea is to provide central management of connections (through a pool manager) such as limiting the total number used at any one time and ensuring that connections don't remain open. This feature is not being used currently because its usage requires training/instruction from Iptor. [[Information Systems: Using JDBC|Refer to this article for more information.]]
 ===Class runner===
 The class runner allows the manual running of a class (e.g. if you need to test program by running it within Integrator immediately instead of configuring a job trigger or condition).

@@ Line 79: / Line 79: @@
 ==Tips==
 * Integrator will not execute the class when the modifier for the default constructor is not set to <code>public</code>.
 * Integrator will not execute the class when a default constructor is not explicitly specified.
 ==Other notes==

@@ Line 21: / Line 21: @@
 * '''Source code''' - C:\Integrator\bin\classes
 * '''Input/output files''' - C:\Integrator_Data\in and C:\Integrator_Data\out. Some of the sub-folders are watch folders.
-* '''Libraries''' - C:\Integrator\bin\extensions\ibs\eclipse\plugins\
+* '''Libraries''' - C:\Integrator\bin\extensions\ibs\eclipse\plugins\IBSExternalPackages. Additional JARs go here. However, read [[Information Systems:Managing dependencies in Iptor Integrator| this article]] for more information on Integrator systema and project dependencies.
 ===Integrator Studio IDE===

@@ Line 82: / Line 82: @@
 * FolderWatcher and Timer jobs are best run with the following JVM arguments (which can be set in the options for the job):
  ''-Xmx768m -classpath C:\Integrator\bin\extensions\ibs\eclipse\plugins\IBSUserPackages\lib\*;C:\Integrator\bin\extensions\ibs\eclipse\plugins\IBSFramework\lib\*;C:\Integrator\bin\extensions\ibs\eclipse\plugins\IBSFrameworkBase\lib\*''
  The class path is important - this avoids the default class path which is <code>C:\Integrator\bin\extensions\ibs\eclipse\plugins\IBSExternalPackages\lib</code>. This path contains packages needed by Integrator itself, but the project often needs a newer version.

@@ Line 80: / Line 80: @@
 * Integrator will not execute the class when the modifier for the default constructor is not set to <code>public</code>.
 * Integrator will not execute the class when a default constructor is not explicitly specified.
 ==Other notes==
  ''It is worth noting that I do not use Integrator in a "stock" manner i.e. I don't use Integrator Studio, nor do I use many of its facilities. The reasons are more thoroughly discussed ''[[Information_Systems:Developing_integrations_using_Java_and_Iptor_Integrator|here]]''. It just deserves to be mentioned here because if you were an Integrator specialist (rather than a generic developer), you may find the programs difficult to work with as I work around a lot of it. However, this point shouldn't affect the creation of new programs.-[[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]])''

← Older revision		Revision as of 00:53, 28 May 2021
Line 76:		Line 76:

	* Currently, email alerts for errors are sent to [[User:Norwinu\|norwizzle]] ([[User talk:Norwinu\|talk]]). The message itself is not very useful as it does not provide much details about the error, but it does contain a link to the log.		* Currently, email alerts for errors are sent to [[User:Norwinu\|norwizzle]] ([[User talk:Norwinu\|talk]]). The message itself is not very useful as it does not provide much details about the error, but it does contain a link to the log.
		+
		+	==Tips==
		+	* Integrator will not execute the class when the modifier for the default constructor is not set to <code>public</code>.
		+	* Integrator will not execute the class when a default constructor is not explicitly specified.

	==Other notes==		==Other notes==

← Older revision		Revision as of 19:59, 13 May 2021
Line 74:		Line 74:

	* Currently, email alerts for errors are sent to [[User:Norwinu\|norwizzle]] ([[User talk:Norwinu\|talk]]). The message itself is not very useful as it does not provide much details about the error, but it does contain a link to the log.		* Currently, email alerts for errors are sent to [[User:Norwinu\|norwizzle]] ([[User talk:Norwinu\|talk]]). The message itself is not very useful as it does not provide much details about the error, but it does contain a link to the log.
−
−	==Tips and Tricks==
−	===Processing a file again for a Folder Watcher job===
−	This depends somewhat on the particular job configuration, but the convention has been for the root folder of the Folder Watcher job to be structured like such:
−
−	[[File:2021-03-19 12_02_54-__xtgui.unipharm.local_c$_Integrator_Data_in_carrier_interface_invoices_atlas.png\|400px]]
−
−	Therefore:
−	# Determine this root folder for the job in question
−	# Navigate to the temp\hash\ folder
−	# Because the filenames of these files are hashes of the actual filenames, it is not obvious which one correlates to the file you want to delete, so you'll need to go by the date. Depending on the job, it might be ok to delete a few surrounding ones. For example for Carrier Interface import jobs.

	==Other notes==		==Other notes==

@@ Line 69: / Line 69: @@
 The class runner allows the manual running of a class (e.g. if you need to test program by running it within Integrator immediately instead of configuring a job trigger or condition).
 ===Logs===
-Logging can be configured and viewed for each job:
+* Logging can be configured and set for a minimum log level (debug, info etc.). A separate log is associated with each job:
 [[File:2021-03-23 11_13_15-Iptor XT Platform.png|400px]]
- Currently, email alerts for errors are sent to [[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]])
+* Currently, email alerts for errors are sent to [[User:Norwinu|norwizzle]] ([[User talk:Norwinu|talk]]). The message itself is not very useful as it does not provide much details about the error, but it does contain a link to the log.
 ==Tips and Tricks==