Last post Feb 21, 2007 11:17 AM by Jenni Phillips
Feb 20, 2007 06:06 AM|christophep|LINK
1° general question
Is there a technical/marketing material for performance issues on HMC 3.5 and specifically MS Provisioning System ?
customer scenario is : custom resource manager + custom namespace for wrapping all the mailbox functions.
2° Special createMailBox scenario
to handle a special feature for the CreateMailBox business operation, MCS team decided to create a custom resource manager and a custom namespace to handle some technical point.
Does it exist a simple way for creating mailbox or it is possible to decide where to create a mailbox (ex:on a dedicated mailstore) without doing such a "Tour de Pise" ?
(Tour de Pise is a architectural construction, which tend to be destroyed)
Feb 21, 2007 10:44 AM|christophep|LINK
I will ask my question in another way.
Custom developmenet around HMC 3.5 and MPS is very strange. XML exotic syntax requires some skills restricted to the MPS engine, not the MS Technologies. What is the smartesy wat to do custom dev with MPS without doing any XML files (custom namespace) ?
It is possible to do only .NET dévelopment or C++ development ? My customer ask for Microsoft Development skills and do not want MPS/dedicated MPS development. Painfull.
Feb 21, 2007 11:17 AM|Steve@Planet|LINK
Well deving against MPS with VS.NET isn't complicated at all.
You can reference an MPS client warpper DLL and then you can pass this certain XML requests that it will send to the MPS engine. Knowing a little about the MPS XML structure is required here, but the full XML is generally provided in the HMC 3.5 documention,
so very little needs to be changed. All you need to do is construct the XML in your app and then pass to the MPS DLL. This is basic XML manipulation and any dev should be able to do it.
If you want to ignore the XML all together then you can reference the MPS Web Services that should have been installed on PROV01. This expose a normal web service interface and from your app you can call functions without worrying about the XML as the web
service does all this for you. The web service MPSWS:MPSGeneral can be used to replace the client DLL and allows you to pass your own constructed XML to it.
If you want to create your own custom namespace then you're going to require a little more knowledge on how MPS deals with and manipulates this.
Regarding creating a mailbox, here is the XML for creating a mailbox and specifying the mail store:
<execute namespace="Hosted Exchange" procedure="CreateMailbox" impersonate="1">
<after source="executeData" destination="data" mode="merge"/>
If you look at the HMC 3.5 documention there are more xml examples given for creating a mailbox using their exetended usage.
Feb 21, 2007 11:17 AM|Jenni Phillips|LINK
Rather than using the XML entry point to the MPS APIs if you use the Web Services one instead, yes you still have to mess about with XML but its only small fairly easily to understand chunks.
Technically its easier to use .NET but not because of MPS because I find its way of treating web services no differently to the developer as any other reference good.
Personally I've not found any "specific" MPS only skills needed, I've just used my existing XML skills, ok I had to learn about exchange but considering thats the life blood of the company I work for and everything I do is Exchange related thats not a major
ask and I've found its no more "custom" than learning any other API.
As for creating an mailbox on a specific mailstore thats fairly easy, the mailStore/serverName and mailStore/mailStoreName are specified on the CreateMailbox call.
However you mentioned a custom resource manager and custom wrappers, these may make things more difficult but as provided the MPS APIs are fairly easy to use I've found, however having an understanding of the Exchange system underneath is essencial.
If you need help on anything specific if you post examples of what you are doing now, and what you are trying to achieve I'm sure someone can give you some help.