ManagedEngine ServiceDesk Plus (Zoho) Connector for JAVA
In this article you will learn how to integrate Using ManagedEngine ServiceDesk Plus (Zoho) Connector you will be able to connect, read, and write data from within JAVA. Follow the steps below to see how we would accomplish that. The driver mentioned above is part of ODBC PowerPack which is a collection of high-performance Drivers for various API data source (i.e. REST API, JSON, XML, CSV, Amazon S3 and many more). Using familiar SQL query language you can make live connections and read/write data from API sources or JSON / XML / CSV Files inside SQL Server (T-SQL) or your favorite Reporting (i.e. Power BI, Tableau, Qlik, SSRS, MicroStrategy, Excel, MS Access), ETL Tools (i.e. Informatica, Talend, Pentaho, SSIS). You can also call our drivers from programming languages such as JAVA, C#, Python, PowerShell etc. If you are new to ODBC and ZappySys ODBC PowerPack then check the following links to get started. |
Connect to ManagedEngine ServiceDesk Plus (Zoho) in other apps
|
Create Data Source in ZappySys Data Gateway based on API Driver
-
Download and install ZappySys ODBC PowerPack.
-
Search for gateway in start menu and Open ZappySys Data Gateway:
-
Go to Users Tab to add our first Gateway user. Click Add; we will give it a name tdsuser and enter password you like to give. Check Admin option and click OK to save. We will use these details later when we create linked server:
-
Now we are ready to add a data source. Click Add, give data source a name (Copy this name somewhere, we will need it later) and then select Native - ZappySys API Driver. Finally, click OK. And it will create the Data Set for it and open the ZS driver UI.
ManagedEngineServiceDeskPlus(Zoho)DSN
-
When the Configuration window appears give your data source a name if you haven't done that already, then select "ManagedEngine ServiceDesk Plus (Zoho)" from the list of Popular Connectors. If "ManagedEngine ServiceDesk Plus (Zoho)" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:
ManagedEngineServiceDeskPlus(Zoho)DSNManagedEngine ServiceDesk Plus (Zoho) -
Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.
OAuth Connection for ManageEngine ServiceDesk Plus API [API Help..]
Steps to get ManagedEngine ServiceDesk Plus (Zoho) Credentials : OAuth [OAuth]
To register custom App, perform the following steps (Detailed steps found in the help link at the end)- Go to Zoho API Console
- Click Add Client link
- Select Server-based Applications option
- Enter desired client name (Display purpose only)
- Enter some URL for Company homepage
- For Authorized Redirect URI enter https://zappysys.com/oauth (Or enter your own but we recommend using ZappySys one if possible). This URL must match on Zoho Connector UI.
- Click CREATE.
- Copy Client ID and Secret and paste on Zoho Connector UI.
Fill in all required parameters and set optional parameters if needed:
ManagedEngineServiceDeskPlus(Zoho)DSNManagedEngine ServiceDesk Plus (Zoho)OAuth [OAuth]https://sdpondemand.manageengine.com/api/v3Required Parameters Optional Parameters ClientId Fill in the parameter... ClientSecret Fill in the parameter... Permissions Fill in the parameter... AccountUrl Fill in the parameter... RedirectUrl Fill in the parameter... RetryMode Fill in the parameter... RetryStatusCodeList Fill in the parameter... RetryCountMax Fill in the parameter... RetryMultiplyWaitTime Fill in the parameter... -
Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
-
Click OK to finish creating the data source.
Read data in Java from the DSN
-
Java code to get the data:
"jdbc:sqlserver://localhost:5000;databasename=ManagedEngineServiceDeskPlus(Zoho)DSN;user=tdsuser;password=test" -
When you run the code it will make the API call and read the data:
-
Here is Java program's code in text format:
//Step-1: Install ZappySys ODBC PowerPack and Configure Data Gateway //Step-2:Assuming the Microsoft SQL Server JDBC Driver is in below folder //C:\Program Files\Microsoft Jdbc Driver 6.0 for SQL Server\sqljdbc_6.0\enu\auth\x64 package padaone; import java.sql.*; public class zappy { public static void main(String[] args) { // Create a variable for the connection string. String connectionUrl = "jdbc:sqlserver://localhost:5000;databasename=ManagedEngineServiceDeskPlus(Zoho)DSN;user=test;password=test"; // Declare the JDBC objects. Connection con = null; Statement stmt = null; ResultSet rs = null; try { // Establish the connection. Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); con = DriverManager.getConnection(connectionUrl); // Create and execute an SQL statement that returns some data. String SQL = "SELECT Country , SUM(UnitPrice * Quantity) Total " + "FROM value " + "GROUP BY Country " + "WITH (SRC='https://services.odata.org/V3/Northwind/Northwind.svc/Invoices?$format=json')"; stmt = con.createStatement(); rs = stmt.executeQuery(SQL); // Iterate through the data in the result set and display it. while (rs.next()) { System.out.println(rs.getString(1) + " " + rs.getString(2)); } } // Handle any errors that may have occurred. catch (Exception e) { e.printStackTrace(); } finally { if (rs != null) try { rs.close(); } catch (Exception e) {} if (stmt != null) try { stmt.close(); } catch (Exception e) {} if (con != null) try { con.close(); } catch (Exception e) {} } } }
Advanced topics
Create Custom Stored Procedure in ZappySys Driver
You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.
Steps to create Custom Stored Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
-
Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
-
Enter the desired Procedure name and click on OK:
-
Select the created Stored Procedure and write the your desired stored procedure and Save it and it will create the custom stored procedure in the ZappySys Driver:
Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here
CREATE PROCEDURE [usp_get_orders] @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>' AS SELECT * FROM Orders where OrderDate >= '<@fromdate>';
-
That's it now go to Preview Tab and Execute your Stored Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01:
Exec usp_get_orders '1996-01-01';
-
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC usp_get_orders @fromdate=''1996-07-30''')
-
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
Create Custom Virtual Table in ZappySys Driver
ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.
If you're dealing with Microsoft Access and need to import data from an SQL query, it's important to note that Access doesn't allow direct import of SQL queries. Instead, you can create custom objects (Virtual Tables) to handle the import process.
Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.
-
Go to Custom Objects Tab and Click on Add button and Select Add Table:
-
Enter the desired Table name and click on OK:
-
And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.
-
Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here
SELECT "ShipCountry", "OrderID", "CustomerID", "EmployeeID", "OrderDate", "RequiredDate", "ShippedDate", "ShipVia", "Freight", "ShipName", "ShipAddress", "ShipCity", "ShipRegion", "ShipPostalCode" FROM "Orders" Where "ShipCountry"='USA'
-
That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only:
SELECT * FROM "vt__usa_orders_only"
-
Let's generate the SQL Server Query Code to make the API call using stored procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder.
SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')
-
Now go to SQL served and execute that query and it will make the API call using stored procedure and provide you the response.
Actions supported by ManagedEngine ServiceDesk Plus (Zoho) Connector
ManagedEngine ServiceDesk Plus (Zoho) Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.Parameter | Description |
---|
Parameter | Description |
---|---|
RequestId |
|
Parameter | Description |
---|---|
RequestId |
|
Parameter | Description |
---|---|
RequestId |
|
TaskId |
|
Parameter | Description |
---|---|
RequestId |
|
TaskId |
|
Parameter | Description |
---|---|
RequestId |
|
TaskId |
|
CommentId |
|
Parameter | Description |
---|---|
RequestId |
|
Parameter | Description |
---|---|
RequestId |
|
NoteId |
|
Parameter | Description |
---|---|
RequestId |
|
Parameter | Description |
---|---|
RequestId |
|
WorklogId |
|
Parameter | Description |
---|---|
RequestId |
|
TaskId |
|
Parameter | Description |
---|---|
RequestId |
|
TaskId |
|
WorklogId |
|
Parameter | Description |
---|---|
RequestId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
ChangeId |
|
Parameter | Description |
---|---|
ChangeId |
|
Parameter | Description |
---|---|
ChangeId |
|
TaskId |
|
Parameter | Description |
---|---|
ChangeId |
|
TaskId |
|
Parameter | Description |
---|---|
ChangeId |
|
TaskId |
|
CommentId |
|
Parameter | Description |
---|---|
ChangeId |
|
Parameter | Description |
---|---|
ChangeId |
|
NoteId |
|
Parameter | Description |
---|---|
ChangeId |
|
Parameter | Description |
---|---|
ChangeId |
|
WorklogId |
|
Parameter | Description |
---|---|
ChangeId |
|
TaskId |
|
Parameter | Description |
---|---|
ChangeId |
|
TaskId |
|
WorklogId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
ProblemId |
|
Parameter | Description |
---|---|
ProblemId |
|
Parameter | Description |
---|---|
ProblemId |
|
TaskId |
|
Parameter | Description |
---|---|
ProblemId |
|
TaskId |
|
Parameter | Description |
---|---|
ProblemId |
|
TaskId |
|
CommentId |
|
Parameter | Description |
---|---|
ProblemId |
|
Parameter | Description |
---|---|
ProblemId |
|
NoteId |
|
Parameter | Description |
---|---|
ProblemId |
|
Parameter | Description |
---|---|
ProblemId |
|
WorklogId |
|
Parameter | Description |
---|---|
ProblemId |
|
TaskId |
|
Parameter | Description |
---|---|
ProblemId |
|
TaskId |
|
WorklogId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
MilestoneId |
|
Parameter | Description |
---|---|
ProjectId |
|
TaskId |
|
Parameter | Description |
---|---|
ProjectId |
|
TaskId |
|
Parameter | Description |
---|---|
ProjectId |
|
TaskId |
|
CommentId |
|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
NoteId |
|
Parameter | Description |
---|---|
ProjectId |
|
Parameter | Description |
---|---|
ProjectId |
|
WorklogId |
|
Parameter | Description |
---|---|
ProjectId |
|
TaskId |
|
Parameter | Description |
---|---|
ProjectId |
|
TaskId |
|
WorklogId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
ReleaseId |
|
Parameter | Description |
---|---|
ReleaseId |
|
Parameter | Description |
---|---|
ReleaseId |
|
TaskId |
|
Parameter | Description |
---|---|
ReleaseId |
|
TaskId |
|
Parameter | Description |
---|---|
ReleaseId |
|
TaskId |
|
CommentId |
|
Parameter | Description |
---|---|
ReleaseId |
|
Parameter | Description |
---|---|
ReleaseId |
|
NoteId |
|
Parameter | Description |
---|---|
ReleaseId |
|
Parameter | Description |
---|---|
ReleaseId |
|
WorklogId |
|
Parameter | Description |
---|---|
ReleaseId |
|
TaskId |
|
Parameter | Description |
---|---|
ReleaseId |
|
TaskId |
|
WorklogId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
AssetId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
TaskId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
ContractId |
|
Parameter | Description |
---|
Parameter | Description |
---|---|
PurchaseOrderId |
|
Parameter | Description |
---|---|
Url |
|
Body |
|
IsMultiPart |
|
Filter |
|
Headers |
|
ManagedEngine ServiceDesk Plus (Zoho) Connector Examples for JAVA Connection
This page offers a collection of SQL examples designed for seamless integration with the ZappySys API ODBC Driver under ODBC Data Source (36/64) or ZappySys Data Gateway, enhancing your ability to connect and interact with Prebuilt Connectors effectively.
List requests [Read more...]
This example shows how to list requests.
SELECT * FROM Requests
Read request details by ID [Read more...]
This example shows how to read extended information about a single request
SELECT * FROM Requests Where id=111112345
Delete request [Read more...]
This example shows how to delete a request by ID.
DELETE FROM Requests Where id=111112345
List request tasks [Read more...]
This example shows how to read all tasks for a single Request ID
SELECT * FROM get_Request_Tasks WITH (RequestId=111112345)
Read request task details [Read more...]
This example shows how to read request task details by single Request ID and Task ID
SELECT * FROM get_Request_Task_Details (RequestId=111112345, TaskId=222212345)
List request task comments [Read more...]
This example shows how to read all comment for specific task
SELECT * FROM get_Request_Task_Comments (RequestId=111112345, TaskId=222212345)
Read request task comment details [Read more...]
This example shows how to read a single comment details for a specific task
SELECT * FROM get_Request_Task_Comment_Details (RequestId=111112345, TaskId=222212345, CommentId=333312345)
List request notes [Read more...]
This example shows how to read all notes for a single Request ID
SELECT * FROM get_Request_Notes WITH (RequestId=111112345)
Read request note details [Read more...]
This example shows how to read request note details by single Request ID and Note ID
SELECT * FROM get_Request_Note_Details (RequestId=111112345, NoteId=222212345)
List request worklog [Read more...]
This example shows how to read all worklogs for a single Request ID
SELECT * FROM get_Request_Worklogs WITH (RequestId=111112345)
Read request worklog details [Read more...]
This example shows how to read request worklog details by single Request ID and Worklog ID
SELECT * FROM get_Request_Worklog_Details (RequestId=111112345, WorklogId=222212345)
List request task worklog [Read more...]
This example shows how to read all worklogs for a single Request Task ID
SELECT * FROM get_Request_Task_Worklogs WITH (RequestId=111112345, TaskId=22222345)
Read request task worklog details [Read more...]
This example shows how to read request task worklog details by single Request Task ID and Worklog ID
SELECT * FROM get_Request_Task_Worklog_Details (RequestId=111112345, TaskId=22222345, WorklogId=333312345)
List projects [Read more...]
This example shows how to list projects.
SELECT * FROM Projects
Read project details by ID [Read more...]
This example shows how to read extended information about a single project
SELECT * FROM Projects Where id=111112345
List assets [Read more...]
This example shows how to list assets.
SELECT * FROM Assets
Read asset by ID [Read more...]
This example shows how to read extended information about an asset
SELECT * FROM Assets Where id=111112345
List purchase orders [Read more...]
This example shows how to list purchase orders.
SELECT * FROM PurchaseOrders
Read purchase order details by ID [Read more...]
This example shows how to read extended information about a single purchase order
SELECT * FROM PurchaseOrders Where id=111112345
List changes [Read more...]
This example shows how to list changes.
SELECT * FROM Changes
Read change details by ID [Read more...]
This example shows how to read extended information about a change
SELECT * FROM Changes Where id=111112345
List contracts [Read more...]
This example shows how to list contracts.
SELECT * FROM Contracts
Read contract details by ID [Read more...]
This example shows how to read extended information about a contract
SELECT * FROM Contracts Where id=111112345
List tasks [Read more...]
This example shows how to list tasks.
SELECT * FROM Tasks
Read task details by ID [Read more...]
This example shows how to read extended information about a task
SELECT * FROM Tasks Where id=111112345
Conclusion
In this article we discussed how to connect to ManagedEngine ServiceDesk Plus (Zoho) in JAVA and integrate data without any coding. Click here to Download ManagedEngine ServiceDesk Plus (Zoho) Connector for JAVA and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).
Download ManagedEngine ServiceDesk Plus (Zoho) Connector for JAVA
Documentation
More integrations
Other application integration scenarios for ManagedEngine ServiceDesk Plus (Zoho)
Other connectors for JAVA
Download ManagedEngine ServiceDesk Plus (Zoho) Connector for JAVA
Documentation
How to connect ManagedEngine ServiceDesk Plus (Zoho) in JAVA?
How to get ManagedEngine ServiceDesk Plus (Zoho) data in JAVA?
How to read ManagedEngine ServiceDesk Plus (Zoho) data in JAVA?
How to load ManagedEngine ServiceDesk Plus (Zoho) data in JAVA?
How to import ManagedEngine ServiceDesk Plus (Zoho) data in JAVA?
How to pull ManagedEngine ServiceDesk Plus (Zoho) data in JAVA?
How to push data to ManagedEngine ServiceDesk Plus (Zoho) in JAVA?
How to write data to ManagedEngine ServiceDesk Plus (Zoho) in JAVA?
How to POST data to ManagedEngine ServiceDesk Plus (Zoho) in JAVA?
Call ManagedEngine ServiceDesk Plus (Zoho) API in JAVA
Consume ManagedEngine ServiceDesk Plus (Zoho) API in JAVA
ManagedEngine ServiceDesk Plus (Zoho) JAVA Automate
ManagedEngine ServiceDesk Plus (Zoho) JAVA Integration
Integration ManagedEngine ServiceDesk Plus (Zoho) in JAVA
Consume real-time ManagedEngine ServiceDesk Plus (Zoho) data in JAVA
Consume real-time ManagedEngine ServiceDesk Plus (Zoho) API data in JAVA
ManagedEngine ServiceDesk Plus (Zoho) ODBC Driver | ODBC Driver for ManagedEngine ServiceDesk Plus (Zoho) | ODBC ManagedEngine ServiceDesk Plus (Zoho) Driver | SSIS ManagedEngine ServiceDesk Plus (Zoho) Source | SSIS ManagedEngine ServiceDesk Plus (Zoho) Destination
Connect ManagedEngine ServiceDesk Plus (Zoho) in JAVA
Load ManagedEngine ServiceDesk Plus (Zoho) in JAVA
Load ManagedEngine ServiceDesk Plus (Zoho) data in JAVA
Read ManagedEngine ServiceDesk Plus (Zoho) data in JAVA
ManagedEngine ServiceDesk Plus (Zoho) API Call in JAVA