API Creator supports MongoDB. As a software engineer, you can use the MongoDB integration to:

1. Using the Resource Editor in API Creator, create a new resource by clicking New Resource.
2. Change the resource name, select MongoDB as the resource type, enter the remaining fields for the MongoDB Server, database name, and collection name. (Optional depending on your security settings) Enter the username and password. You can pass a filter into the resource using MongoDB syntax such as {attributeName: "value"}.
3. Click Save.

Select Attributes to Display

Add the sub-resource MongoOrders using MongoDB resource type  

REST Lab - testing our new resource SQLCustomer with MongoDB orders

Join two MongoDB Collections 

MongoDB developers are told that they cannot do joins across collections. In a strict language sense, this is true. MongoDB is not a relational database. In Live API Creator, resources are created dynamically and incrementally so a parent resource can pass detail row information to a child to retrieve a sub-resource of another collection.

Attach Path

In the previous example, when we join a MongoDB collection, we need to tell the Resource logic where to insert this sub-resource collection. If the name is unique; then the result is a new attribute array with the result. If the name is an existing attribute array - the collection is inserted inside that array.

	{name: 1, balance: 1}

	{ coordinates: {$slice: 2}}

Filter

This is a way to specify additional filtering on the resource, e.g. if you want to restrict the rows that should be returned by the resource.For SQL resources, this should simply be a fragment of a where expression;         

   amount_total < 1000 and paid = 'Y'

For MongoDB resources, you should use the Mongo syntax:         

 :{"$and": [{"$lt": {"amount_total": 1000}}, {"paid": "Y"}]}

REST Lab Example - GET MongoDepartment with EmployeesInDepartment

Add Request/Response events to MongoDB 

Using the API Creator additional pre-and post-event handling services can be added for your MongoDB resources. Event handling begins with incoming requests. The JavaScript editor and access to internal request state information (e.g. a GET, PUT, POST, DELETE):

• A request event is invoked right after a request has been received, but before any processing work has begun. Your request handler will have access to all the relevant information, such as which API key is being used, what the request verb is (GET, POST, PUT,DELETE.), the JSON payload for POST and PUT, and the URL parameters.
• A response event is invoked after the request has been processed, but before the response is sent back to the client. Additional work cam be performed to modify the response.

Use Resources in Business Rules

Authentication and Access Control 

0

Advanced Access to MongoDB using JavaScript

MongoDB and JDBC (Experimental)

There are several JDBC drivers that can connect to MongoDB and perform selects, joins, order by, group by, and filtered where clauses. This example is shown using one of these drivers. The JDBC driver is loaded using the Project/Library upload facility to add new driver JAR files and optionally any JavaScript into the system. This example is using a JDBC driver to connect to MongoDB and execute an SQL query with a where clause. The JDBC driver can also do joins, sorts, column selection and some drivers allow selection into nested arrays (e.g Customer.Orders.Items.PartNum = 12345);