This documentation is archived and is not being maintained.

Loading 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.

For Microsoft SIP Processing Language (MSPL) script applications, load the application manifest manually using the Microsoft Management Console. For more information, in the Microsoft Office Communications Server 2007 Administration Guide see "Adding Script-Only Applications."

NoteNote

Script-only applications cannot be loaded directly through WMI.

For SIP managed code applications, load the application manifest using the ApplicationManifest class, and compile the manifest by calling the ApplicationManifest.Compile method, as illustrated in the following code:

ResourceManager myResourceManager = new ResourceManager(MyApplicationType);
string appManifestXml = myResourceManager.GetString("appManifest");

ApplicationManifest myAppManifest = ApplicationManifest.CreateFromString(appManifestXml);
try {
  myAppManifest.Compile();
}
catch (CompilerErrorException cee) {
  Console.WriteLine("Failed to compile.");
  foreach (string message in cee.ErrorMessages) {
      Console.WriteLine(message);
  }
  return;
}

The compiled application manifest is presented to the server agent, which uses the application attributes along with the rules defined in the MSPL message filter to dispatch only those SIP messages that the application is designed to process. All other message are proxied, or dropped (if so specified).

Show: