Appboard/2.4/builder/data sources/third party: Difference between revisions

imported>Jason.nicholls
imported>Jason.nicholls
No edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:3rd Party Data Source Adapters}}
{{DISPLAYTITLE:Third Party Data Adapters}}
[[Category:AppBoard 2.4]]
Third Party Data Adapters provide access to specific 3rd party applications. This is typically to provide better support, or any support in cases where the more generic data adapters cannot be used such as the database adapters or web service adapters.


Third Party Data Adapters provide some pre-configured options for loading data from certain popular data sources. This page details the options available for each of the Third Party Data Adapters.
The following list of third party adapters are available within AppBoard:


 
* [[appboard/2.4/builder/data_sources/third_party/hp_nnmi|HP Network Node Manager (NNMi)]]
==HP NNMi==
* [[appboard/2.4/builder/data_sources/third_party/omnibus|IBM Tivoli Netcool/OMNIbus]]
 
* [[appboard/2.4/builder/data_sources/third_party/servicenow|ServiceNow]]
The HP NNMi adapter retrieves information about nodes and incidents from the HP Network Node Manager (NNMi) application.
 
 
===Connecting with HP NNMi===
 
Perform the following steps to configure an HP NNMi Data Adapter:
 
#Log in to AppBoard as an administrator.
#Select Data Sources to launch the <b>Data Source Administration</b> panel.
#Click <b>Add</b>.
#Enter the name of the Data Source.
#Select the <b>Third Party</b> adapter type.
#Select the <b>HP NNMi</b> adapter.
#Click <b>Add Data Source</b>.
#Enter the configuration items as detailed in the following table:
 
 
{|claass="wikitable"
!Name
!Description
|-
|'''url'''
|The url for accessing the HP NNMi application.
|-
|'''httpAuthUsername'''
|The Username for accessing the HP NNMi application.
|-
|'''httpAuthPassword'''
|The Password for accessing the HP NNMi application.
|-
|'''cacheTimeout'''
|Time limit before re-loading results from the database.
|-
|}
 
 
 
==IBM Tivoli Netcool/OMNIbus==
 
 
The IBM Tivoli Netcool/OMNIbus adapter retrieves information from a Tivoli Netcool/OMNIbus object server.
 
 
 
===Connecting with IBM Tivoli Netcool/OMNIbus===
 
 
Perform the following steps to configure an IBM Tivoli Netcool/OMNIbus Data Adapter:
 
#Log in to AppBoard as an administrator.
#Select Data Sources to launch the <b>Data Source Administration</b> panel.
#Click <b>Add</b>.
#Enter the name of the Data Source.
#Select the <b>Third Party</b> adapter type.
#Select the <b>IBM Tivoli Netcool/OMNIbus</b> adapter.
#Click <b>Add Data Source</b>.
#Select a template (database type) from the drop-down list provided.
#Enter the configuration items as detailed in the following table:
 
{|class="wikitable"
!Name
!Description
|-
|'''driver'''
|The Java class name for the JDBC driver. Example: <tt>oracle.jdbc.driver.OracleDriver</tt>
|-
|'''connectTimeout'''
|Time (in seconds) after a timeout occurs to wait before attempting to re-establish the connection. Setting this value too low can impact the performance of the system.
|-
|'''timeout'''
|Time to wait before timing out on connecting to the datasource.
|-
|'''cacheTimeout'''
|Time limit before re-loading results from the database.
|-
|'''catalogName'''
| Database catalog name. It is not required, used to limit the set of tables found on the search.
|-
|'''schemaName'''
|The database schema name. It is not required, used to limit the set of tables found on the search.
|-
|'''tableNameRegex'''
|Regular expression specifying which tables you want returned from the server.
|-
|'''ansiMode'''
|Check this box if your database is running in ANSI mode. Some databases (including MySQL and SQL Server) provide this variation on the character used to quote elements such as columns when the SQL statement is being constructed.
|-
|'''host'''
|IP Address or DNS resolvable host name.
|-
|'''port'''
|TCP port for the server connection. Default is 4100.
|-
|'''dbname'''
|server name / database name.
|-
|'''url'''
|The JDBC connection string/URL for defining the connection. This typically contains information about the database server and name, the user id, a password for connecting to the database, and an Oracle SID at the end which uniquely identifies the name of a particular database to connect to. Example: <tt>jdbc:mysql://myservername:3306/mydbname</tt>. The default connection string provided when you create the JDBC/Oracle adapter Data Source in AppBoard is the following: <tt>jdbc:oracle:thin:@localhost:1521:portal</tt>. Note that the sample URL string contains an Oracle SID at the end ("portal"), which uniquely identifies the name of a particular database to connect to. It is recommended that you make sure the connection string includes this SID so the connection can be made between AppBoard and the database. You may need to ask the database or application administrator to provide the Oracle SID for the database. Example Oracle URL: <tt>jdbc:oracle:thin:@servername:1521:OracleSID</tt>
|-
|'''username'''
|Username credential used to connect
|-
|'''password'''
|Password credential used to connect
|-
|'''poolsize'''
|Number of connections to pool
|-
|}

Latest revision as of 07:03, 14 December 2013

Third Party Data Adapters provide access to specific 3rd party applications. This is typically to provide better support, or any support in cases where the more generic data adapters cannot be used such as the database adapters or web service adapters.

The following list of third party adapters are available within AppBoard: