Party Activities Microservice

This is a party activity logging microservice from Pip.Services library.
It logs important party activities like signups, signins,
creation, changes or deletion of data items and so on.

The microservice currently supports the following deployment options:
* Deployment platforms: Standalone Process, Seneca
* External APIs: HTTP/REST, Seneca
* Persistence: In-Memory, Flat Files, MongoDB

This microservice has no dependencies on other microservices.

Quick Links:

* Download Links
* Development Guide
* Configuration Guide
* Deployment Guide
* Client SDKs
- Node.js SDK
* Communication Protocols
- HTTP Version 1
- Seneca Version 1

Contract

Logical contract of the microservice is presented below. For physical implementation (HTTP/REST, Thrift, Seneca, Lambda, etc.),
please, refer to documentation of the specific protocol.

``typescript
class PartyActivityV1 implements IStringIdentifiable {
/ Identification /
public id: string;

/ Identification fields /
public time: Date;
public type: string;
public party: ReferenceV1;

/ References objects (notes, goals, etc.) /
public ref_item: ReferenceV1;
public ref_parents: ReferenceV1[];
public ref_party: ReferenceV1;

/ Other details like % of progress or new status /
public details: StringValueMap;
}

class ReferenceV1 {
public id: string;
public type: string;
public name?: string;
}

interface IActivitiesV1 {
getPartyActivities(correlationId: string, filter: FilterParams, paging: PagingParams,
callback: (err: any, page: DataPage) => void): void;

logPartyActivity(correlationId: string, activity: PartyActivityV1,
callback?: (err: any, activity: PartyActivityV1) => void): void;

batchPartyActivities(correlationId: string, activities: PartyActivityV1[],
callback?: (err: any) => void): void;

deletePartyActivities(correlationId: string, filter: FilterParams,
callback?: (err: any) => void): void;
}

`

Download

Right now the only way to get the microservice is to check it out directly from github repository
`bash
git clone git@github.com:pip-services-users/pip-services-activities-node.git
`

Pip.Service team is working to implement packaging and make stable releases available for your
as zip downloadable archieves.

Run

Add config.yml file to the root of the microservice folder and set configuration parameters.
As the starting point you can use example configuration from config.example.yml file.

Example of microservice configuration
`yaml
---
- descriptor: "pip-services-commons:logger:console:default:1.0"
level: "trace"

- descriptor: "pip-services-activities:persistence:file:default:1.0"
path: "./data/activities.json"

- descriptor: "pip-services-activities:controller:default:default:1.0"

- descriptor: "pip-services-activities:service:http:default:1.0"
connection:
protocol: "http"
host: "0.0.0.0"
port: 8080
`

For more information on the microservice configuration see Configuration Guide.

Start the microservice using the command:
`bash
node run
`

Use

The easiest way to work with the microservice is to use client SDK.
The complete list of available client SDKs for different languages is listed in the Quick Links

If you use Node.js then you should add dependency to the client SDK into package.json file of your project
`javascript
{
...
"dependencies": {
....
"pip-clients-activities-node": "^1.0.*",
...
}
}
`

Inside your code get the reference to the client SDK
`javascript
var sdk = new require('pip-clients-activities-node');
`

Define client configuration parameters that match configuration of the microservice external API
`javascript
// Client configuration
var config = {
connection: {
protocol: 'http',
host: 'localhost',
port: 8080
}
};
`

Instantiate the client and open connection to the microservice
`javascript
// Create the client instance
var client = sdk.ActivitiesHttpClient(config);

// Connect to the microservice
client.open(function(err) {
if (err) {
console.error('Connection to the microservice failed');
console.error(err);
return;
}

// Work with the microservice
...
});
`

Now the client is ready to perform operations
`javascript
// Log party activity
client.logPartyActivity(
null,
{
type: 'signup',
party: {
id: '123',
name: 'Test User'
}
},
function (err, activity) {
...
}
);
`

`javascript
var now = new Date();

// Get the list system activities
client.getPartyActivities(
null,
{
party_id: '123',
from_time: new Date(now.getTime() - 24 3600 1000),
to_time: now
},
{
total: true,
skip: 0,
take: 10
},
function(err, page) {
...
}
);
``

Acknowledgements

This microservice was created and currently maintained by Sergey Seroukhov.