hyperledger-archives
diff --git a/‎packages/composer-website/jekylldocs/applications/subscribing-to-events.md‎
Lines changed: 34 additions & 0 deletions b/‎packages/composer-website/jekylldocs/applications/subscribing-to-events.md‎
Lines changed: 34 additions & 0 deletions
diff --git a/‎packages/composer-website/jekylldocs/business-network/deploybusinessnetwork.md‎
Lines changed: 28 additions & 31 deletions b/‎packages/composer-website/jekylldocs/business-network/deploybusinessnetwork.md‎
Lines changed: 28 additions & 31 deletions
@@ -0,0 +1,34 @@
+---
+layout: default
+title: Subscribing to events
+category: tasks
+sidebar: sidebars/applications.md
+excerpt: Subscribing to events
+---
+
+# Subscribing to events
+
+Applications can subscribe to events from a business network by using the `composer-client.BusinessNetworkConnection.on` API call. Events are defined in the business network model file and are emitted by specified transactions in the transaction processor function file. For more information on publishing events, see [publishing events](../business-network/publishing-events.html).
+
+## Before you begin
+
+Before an application can subscribe to events, you must have defined some events and the transactions which will emit them. The business network must also be deployed and you must have connected to it. Follow the steps for [connecting to the {{site.data.conrefs.composer_full}} runtime](../applications/getting-started-nodejs-app.html).
+
+## Procedure
+
+1. An application must send a specific API call to subscribe to events emitted transactions in a business network. Currently, an application which subscribes to events will receive all events which are emitted. The API call should take the following format:
+
+  ```Javascript
+  businessNetworkConnection.on('event', (event) => {
+  // event: { "$class": "org.namespace.BasicEvent", "eventId": "0000-0000-0000-000000#0" }
+  console.log(event);
+  });
+  ```
+
+ This includes an event called `BasicEvent` which was created in the [publishing events](../business-network/publishing-events.html) documentation. The `eventId` property is always the same as the `transactionId` of the transaction which emitted the event, with an appended number in the form `"transactionId": "<transactionId>#number"`.
+
+## What next?
+
+The application will now receive all of the events emitted by the business network, and it's up to the application to choose to what extent those events are integrated.
+
+---
@@ -1,6 +1,6 @@
 ---
 layout: default
-title: Task - Deploy a Business Network
+title: Task - Deploy a Business Network Definition
 category: tasks
 sidebar: sidebars/businessnetworks.md
 excerpt: How to deploy a Business Network
@@ -10,45 +10,42 @@ excerpt: How to deploy a Business Network
 
 ---
 
-A business network is deployed using the `composer network deploy` command.
+A business network definition is deployed using the `composer network deploy` command.
 
-## Procedure
-
-1. Before deploying a business network, a [Business Network Definition](../business-network/businessnetworkdefinition.html) is needed as a `zip` file with the following structure:
+# Before you begin
 
- ```
- BusinessNetworkArchive.zip
- ├── lib
- │   └── mozart.cto.js
- ├── models
- │   └── mozart.cto
- └── package.json
- ```
+Before deploying a business network, a [Business Network Definition](../business-network/businessnetworkdefinition.html) is needed as a `zip` file with the following structure:
 
- -_lib_ contains all of the transactions processor functions
- -_models_ contains all of the model files written in the [CTO Language](../reference/cto_language.html).
- -_package.json_ is required, and is used to create the [Business Network Definition](../business-network/businessnetworkdefinition.html)'s identifier
+```
+BusinessNetworkArchive.zip
+├── lib
+│   └── mozart.cto.js
+├── models
+│   └── mozart.cto
+└── package.json
+```
+<!--
+You can use the `composer archive` command to create an archive with the correct format.
 
- You can use the `composer archive` command to create an archive with the correct format.
+**NOTE**: *Do not zip a a folder containing **lib**, **models**, and **package.json** to create an Business Network Archive, zip the contents themselves*
+-->
 
- **NOTE**: *Do not zip a a folder containing **lib**, **models**, and **package.json** to create an Business Network Archive, zip the contents themselves*
-
-2. Start [Hyperledger Fabric Peer and Membership Service](runtime-start.md)
+## Procedure
 
-3. [Create a Connection Profile](../installing/createconnectionprofile.html) or do *not* use `-p` and allow {{site.data.conrefs.composer_full}} to create a `Default Connection Profile` for you.
+1. Start [Hyperledger Fabric Peer and Membership Service](runtime-start.md).
 
-4. Enter the command on a single line. For example:
+2. [Create a Connection Profile](../installing/createconnectionprofile.html) or do *not* use `-p` and allow {{site.data.conrefs.composer_full}} to create a `Default Connection Profile` for you.
 
- `composer network deploy -a <BusinessNetworkDefinition>.zip -i <Your EnrollmentID>`
+3. Enter the command on a single line. For example:
 
-5. Enter your Enrollment Secret when prompted.
+  `composer network deploy -a <BusinessNetworkDefinition>.zip -i <Your EnrollmentID>`
 
- `prompt: What is the enrollment secret of the user?:`
+4. Enter your Enrollment Secret when prompted.
 
-6. When you see
+5. When you see
 
- ```
- Deploying business network definition. This may take a little time.
- Command completed successfully.
- ```
-  you have successfully deployed a business network!
+   ```
+   Deploying business network definition. This may take a little time.
+   Command completed successfully.
+   ```
+ the business network definition has been successfully deployed.