Creating an Application Manifest
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
Creating an application manifest is the first step in the process of creating a SIP application that runs on Microsoft Office Communications Server 2007 R2. The application manifest contains both the basic rules for message delivery to the application and the message filtering script.
Start by considering the functionality of the potential application and deciding which type of application is appropriate. You can use Microsoft Office Communications Server 2007 R2 Server SDK to create two types of applications:
Microsoft SIP Processing Language (MSPL) script applications that are embedded in the application manifest.
SIP managed code applications.
MSPL script applications are appropriate for doing either of the following:
Proxying SIP messages of a specific type.
Handling potentially complex branching proxy scenarios or supporting multiple points-of-presence (MPOP), where extensibility is not required.
See the topics contained in Microsoft SIP Processing Language Reference for descriptions of the functionality that MSPL supports.
SIP managed code applications are appropriate for doing either of the following:
Handling potentially complex branching proxy scenarios or supporting MPOP, where extensibility is required.
Working directly with SIP transaction objects and supporting multiple work threads.
If you build a SIP managed code application, you must also determine the subdivision of labor between the message filter and the application.
Application Manifest Template
After deciding which type of application you need, use an XML or text editor to write the content of the application manifest using the following template:
<?xml version="1.0" ?> <lc:applicationManifest lc:appUri="URI" xmlns:lc=http://schemas.microsoft.com/lcs/2006/05> insert_application_attribute_elements_here <lc:splScript> <![CDATA[ insert_message_filter_script_here ]]> </lc:splScript> </lc:applicationManifest>
The application attribute elements must precede the message filter script.
Saving the Application Manifest
For MSPL script applications, save the manifest as a text file with the extension ".am"
For SIP managed code applications, either save the manifest as a text file with the extension ".am" or embed it in an application assembly as a resource. Application manifests can also be generated in-line or dynamically as appropriate. For example, an application could filter on location-specific URIs or domain values supplied by code logic.