OMS development overview

OMS (outlook Mobile Service)Is a web service that provides SMS sending and receiving functions for the outlook mobile plug-in. In fact, Outlook only provides a plug-in client integrated in outlook, which points to the Web service of a text message supplier through configuration and automatically calls the Web Service through the Protocol interface, the Web Service is responsible for receiving SOAP requests sent from Outlook, so as to send real text messages. Currently this function in China's Microsoft certified service providers can be found on the following website http://messaging.office.microsoft.com/HostingProviders.aspx? Src = o14 & lc = 2052. Theoretically, anyone can develop such ws. As long as the interfaces are consistent, Microsoft authentication is not required. I recently researched this function. Due to horizontal restrictions, I encountered many difficulties in implementation, took a lot of detours, and learned a lot. Fortunately, I basically implemented the interface at the end, deployment is also implemented. This article is just a summary.

Development and deployment points of OMS Development

Outlook client Configuration

CurrentlyOutlook2007 and later versionsThis function is supported. Outlook users who want to use this function need to simply Configure Outlook. outlook2010 is used as an example here.

1. open account settings and select Add new account:

2. Select text messaging (SMS) and next (Note: select other in outlook2007 ):

 

Enter the WS address provided by the WS service provider in the service provider URL, and enter the user name and password. the user name and password here refer to the user registered at the service provider and have nothing to do with the Outlook account. After entering the information, clickTest account settingsIf there is no error, OK.

After setting, you can send text messages via email. Click new items and select text message (SMS ):

 

On the pop-up text message page, enter a text message. The page is very similar to the new email interface. You can enter a mobile phone number directly in the to interface. Multiple numbers can be separated by commas (,) or imported from contacts, enter the text message content in the body, and you can see the preview on the left side (the number of texts displayed on each screen is set by the service provider ). After entering the information, click send. Outlook will automatically call the interface to send text messages. If the sending fails, outlook will return the cause of the error in the form of an email; if the sending is successful, the text message will appear in "sent.

 

OMS development overview

The above content is what the user needs to do. For service providers, you need to develop a web service to implement the interface defined by outlook. The official Microsoft development documentation can be found at the following address, with a total of three guideline:

Http://msdn.microsoft.com/en-us/library/bb277361 (V = office.12). aspx

The document above does describe how to develop such a ws in detail, but there are a lot of tricky problems in actual deployment and testing.

Interface definition overview

The following four interfaces must be implemented by Outlook:

• String getserviceinfo ()Outlook will call this method when you test and click test account settings. This method needs to return the server settings, such as the provider name, provided functions (SMS, MMS), and short message format restrictions.
• String getuserinfo (string xmsuser)After getserviceinfo is successfully called, outlook will send the user name and password entered in the configuration to the server through this method. The server is responsible for verifying whether the use is legal and returning XML results. If the use is legal, the result can contain the mobile phone number and email address when the user registers. The two messages saved by the service provider can be used to send a reply message in the future.
• String deliverxms (string xmsdata)After a user clicks send, outlook calls this method. The xmsdata format is complex, including the user name and password of the user, the recipient list of the SMS, And the content. If it is a MMS Message, there is additional data. After the server receives this call, it should first authenticate the user, then send a text message, and return the result in XML.
• String sendxms (string xmsdata)Microsoft officially said that this method was called after outlook2007sp1 to replace deliverxms, and the interface definition is exactly the same as deliverxms. In fact, during the outlook2010 test, I found that deliverxms is still called when the deliverxms method is provided.

It is not difficult to implement the above four interfaces. Microsoft documents have detailed protocol descriptions.

Technical Selection Problems

Due to system requirements, at first we considered using WCF to develop a WS and work in Windows Service boarding mode. When I learned that HTTPS is required, I also studied Xu's article, but in the end I only realized the full trust of the browser to access WS, and outlook still encountered an error (see the deployment article for details ). After debugging, it was found that outlook did not call any ws method at all. However, you can only return to ASP. NET web service. After all, the official examples and some successful examples do the same.

We didn't try to test the WCF ws in IIS because on the one hand, I have a limited level, but I only know about WCF. On the other hand, I am not allowed to try too many times. Finally, we deployed this ws Based on ASP. NET and iis7.5. The detailed deployment method will be involved in the next article.

 

Labor fruit, reproduced please indicate the source: http://www.cnblogs.com/P_Chou/archive/2011/01/10/oms-develop-overview.html