- The base environment for Hello DBP is 10.1 GA, labeled 2017 October (Apama and webMethods 10.1, Terracotta 4.3/DB 10.1, Adabas, Natural).
- Be sure to use Software AG Update Manager to install the latest fixes.
- Software AG makes no warrantees for third party software and mentioning them here does not constitute an endorsement.
- Link to Air Server Software, for mirroring an iPhone screen onto a Windows or Mac desktop. A free trial is available.
- Link to Ditto Clipboard Manager, for managing your own collection of text snippets to allow for easily filling in text fields from named clipboard entries.
- Link to Postman, to test APIs.
- Link to Elasticsearch Head plugin, a web front end for Elasticsearch, to browse persisted digital events.
To reproduce this sprint demo, you'll need the following:
- Link to create your own trial Cumulocity tenant.
- Link to Cloud Sensor App for Android. But you also scan the QR code from the Cockpit "Add Smartphone" wizard.
- Link to Cloud Sensor App for iPhone (coming soon).
- Link to Cloud Sensor App Documentation.
- Link to Cumulocity Cockpit Documentation. You can save one of the Acceleration measurements as a Data Point into the library, and set thresholds. This is what it looks like after saving it.
- The built-in alarm keyword is
c8y_ThresholdAlarm
. This is used in the second SmartRule. - Text for SmartRule to send a notification to a smart phone using the Cloud Sensor App:
{
"c8y_Message": {
"text": "Slow down!"
}
}
To reproduce this sprint demo, you'll need the following:
- Your own or access to a shared Cumulocity tenant.
- Integration Server with CloudStreams installed.
- Designer with Service Development plugins.
- Link to Cumulocity Provider for CloudStreams, follow instructions in the associated documentation to install to IS.
- Download and install the latest HelloDBP package from IS folder.
- From Designer Service Development, you'll also have to use File > Sync Document Types > All Out-of-Sync... to sync the two Digital Event Services types to the common repository.
- Disable and then edit the Cumulocity connector from IS Administration screens to change to your tenant URL, your username and password. It will look something like this:
- You'll also have to go through the steps for configuring Terracotta DB described in the next section.
To reproduce this sprint, you'll need the following, in addition to everything from previous sprints:
- Terracotta DB and Terracotta DB IS Adapter installed, with license file configured.
- Manually create a new dataset called "Things", you can do that via the Terracotta DB IS Adapter administration.
To reproduce this sprint, you'll need the following, in addition to everything from previous sprints:
- Edit the HelloREST API Descriptor to adjust for your IS machine name and port:
- Warning: this HelloDBP package includes a Flow service called "HelloDBP.Utility:getSwagger", which in turn uses an unsupported IS built-in service. This is only for convenience in the demo. You can also save the swagger file to a file on disk and import into API Gateway, API Portal or Postman.
- Here is a sample json payload for a new Thing object:
{ "Thing" : { "Name" : "Thing 1", "Health" : 100, "Account" : "Account 1" } }
To reproduce this sprint, you'll need the following, in addition to everything from previous sprints:
- API Gateway installed, which includes Event Data Store.
- Use the following URL to import the HelloDBP REST API into Gateway
http://localhost:5555/invoke/HelloDBP.Utility:getSwagger?RESTDescriptorName=HelloDBP.HelloIS:HelloREST
- To use the API Key policy, your calling applications must include the HTTP header key
x-Gateway-APIKey
and the actual key generated when creating the new application in API Gateway.
To reproduce this sprint, you'll need the following, in addition to everything from previous sprints:
- API Portal installed and running.
- To enable publishing from Gateway to Portal, you must configure that in Gateway administration:
To reproduce this sprint, you'll need the following, in addition to everything from previous sprints:
- Digital Event Services (DES) and associated Designer plug-in installed.
- Command Central server, not necessarily on same machine or same suite folder.
- Platform Manager in same suite folder as Integration Server.
- Universal Messaging installed, including a Digital Event Service license.
- Integration Server Digital Event Services configured, e.g. the default configuration is:
To reproduce this sprint, you'll need the following, in addition to everything from previous sprints:
- Digital Event Persistence (DEP) Driver installed.
- JDBC Adapter installed on Integration Server.
- DEP Library jar file copied to JDBC Adapter code/jars folder.
- Event Data Store installed and running, or a supported Elasticsearch or Hadoop server with associated DES custom configuration.
- Integration Server Digital Event Services configured for Event Persistence, e.g. the default configuration is:
- Configure a DES Service Group to store to Elasticsearch in addition to publishing to Universal Messaging, e.g. the configuration for HelloDBP is:
To reproduce this sprint, you'll need the following, in addition to everything from previous sprints:
- Apama server, Platform Manager plugin for Apama, and Designer Application Development plugin installed.
- The DES event types for ThingAlert and ThingEvent should already have been synchronized to the DES Event Type repository in the same suite folder as Apama.
- The full Apama project can be found at HelloApama.
- Here's the snippet of EPL code for the HelloApama.mon script:
using com.softwareag.connectivity.ConnectivityPlugins;
monitor HelloApama {
action onload {
ConnectivityPlugins.onApplicationInitialized();
monitor.subscribe( HelloDBP.HelloEvents.ThingEvent.CHANNEL );
HelloDBP.HelloEvents.ThingEvent thingEvent;
on all HelloDBP.HelloEvents.ThingEvent() : thingEvent {
send thingEvent to "com.apama.queries";
log thingEvent.toString() at INFO;
}
}
}
- To build the query, these are the shortcuts:
- Condition:
(t1.Health.toFloat() - t2.Health.toFloat()) / t1.Health.toFloat() >= 0.5
- Custom EPL Action:
send HelloDBP.HelloEvents.ThingAlert( t1.Id, "Thing '" + t1.Name + "' may be unhealthy.", t1.EventTime, "Normal", "", new sequence<integer> ) to HelloDBP.HelloEvents.ThingAlert.CHANNEL;
- Condition:
- Create a new Apama instance in Command Central, e.g. with settings like these:
To reproduce this sprint, you'll need the following, in addition to everything from previous sprints:
- MashZone NextGen installed.
- To import MashZone assets
- Go to folder MashZoneNG > prestocli > bin and run these commands:
padmin importAlias -u <User> -w <Password> -f "<local git path>\hello-dbp\assets\MashZone\Aliases.zip"
padmin importDashboard -u <User> -w <Password> -f "<local git path>\hello-dbp\assets\MashZone\Dashboard.zip"
- Restart MashZone NextGen. This is needed for the Event Services to restart properly.
- Update the URL of EventStore under DataSources in Admin Console and test the connection. Make sure to update the index “hellodbp” with correct index (default_index).
To reproduce this sprint, you'll need the following, in addition to everything from previous sprints:
- AgileApps installed locally or an AgileApps tenant in the public cloud.
- In the IS package called HelloDBP, edit the HelloDynamicApps > handleThingAlert trigger and enable it.
- In the IS service called HelloDynamicApps > createThingAlertCase
To reproduce this sprint, you'll need the following, in addition to everything from previous sprints:
- Dynamic Business Orchestrator IS package installed plus Designer plugin for DBO and My webMethods User Interface for DBO.
- The full DBO project can be found at HelloDBOProject and HelloDBOTasks. These can be imported into Designer.
- After importing the Designer project, you could open the HelloDBO process and click "Upload for Dynamic Process".
- If you want to create the process from scratch, make it look like this:
- Link to Mobile Business Console App for iPhone or Mobile Business Console App for Android