This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| docs:3500:0400 [2025/06/11 08:16] – aware_support3 | docs:3500:0400 [2025/06/12 04:00] (current) – Change to AwareIM aware_support3 |
|---|
| A channel therefore must translate the service request or notification message that is sent by //**AwareIM**// to the external party into whatever format the external party understands. Similarly a channel has to translate a message sent by the external party into the service request or notification message that can be understood by //**AwareIM**//. | A channel therefore must translate the service request or notification message that is sent by //**AwareIM**// to the external party into whatever format the external party understands. Similarly a channel has to translate a message sent by the external party into the service request or notification message that can be understood by //**AwareIM**//. |
| |
| Note that if an external party is sending service requests to //**AwareIM**// it must first log into //**AwareIM**// as a particular user (an intelligent business object representing the external party must be a member of the SystemUsers business object group), otherwise the service request will be sent on behalf of a “guest” user. Sending notifications to //**Aware IM,**// on the other hand, does not require logging in. | Note that if an external party is sending service requests to //**AwareIM**// it must first log into //**AwareIM**// as a particular user (an intelligent business object representing the external party must be a member of the SystemUsers business object group), otherwise the service request will be sent on behalf of a “guest” user. Sending notifications to //**AwareIM,**// on the other hand, does not require logging in. |
| |
| There are a number of predefined channels that //**AwareIM**// comes with, such as the E-mail channel, the SOAP channel and others (see the “Defining Intelligent Business Objects” section in the “Aware IM User Guide”). If your application connects to external software systems or hardware using protocols that are not supported by //**AwareIM**// out-of-the-box, you are likely to need to write your own custom channel that will connect your //**AwareIM**// system with the required software system or a hardware device. | There are a number of predefined channels that //**AwareIM**// comes with, such as the E-mail channel, the SOAP channel and others (see the “Defining Intelligent Business Objects” section in the “AwareIM User Guide”). If your application connects to external software systems or hardware using protocols that are not supported by //**AwareIM**// out-of-the-box, you are likely to need to write your own custom channel that will connect your //**AwareIM**// system with the required software system or a hardware device. |
| |
| The following section describes what is involved in adding a new custom channel to //**AwareIM**//. | The following section describes what is involved in adding a new custom channel to //**AwareIM**//. |