Link to home
Start Free TrialLog in
Avatar of ditkis
ditkis

asked on

does a web server need to have Interdev extentions...

installed in order to deploy / develop MTS application?
ASKER CERTIFIED SOLUTION
Avatar of scontreras
scontreras

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ditkis
ditkis

ASKER

The instructions I found for invoking the MTS component from an ASP page required use of Interdev.  Not sure why, but I didn't find any alternative.  Why exactly do I need Interdev for that and do I need to have a full blown Interdev project, or just opening a stand along file is enough?
Have you created the MTS package?  After you create the package, you should export it.  When you export, MTS will create for you a .exe in the clients subdir of the folder to which you've exported.  Run this exe on the web server.  This .exe actually sets the DCOM link to the MTS package.  It helps to test if the link was successful by running OLEView on the web server, instantiating your object (inside of OLEView), and then popping over to your MTS box to check that the component is activated.  You'll know it's activated if you see it spinning inside the MTS Explorer.
Avatar of ditkis

ASKER

Got it!
And how do you instantiate the object inside of OLEView?
thanks
To instantiate an object inside OLEView, first make sure you are in Expert Mode by pulling down the view menu and ensure "Expert Mode" is checked.  Then, within the "Object Classes" branch (it is expanded by default when you open up OLEView in Expert Mode), expand the "All Objects" branch.  At this point, OLEView will enumerate all Interfaces it is aware on the machine.  Simply look for the app id's in your library.  For example, if, when you compiled your project, you set your project name to "MyLibrary" (by setting the project name on the Project|Properties|General tab) and you have two classes called "Class1" and "Class2", then in this expanded branch you'll look for two entries: "MyLibaray.Class1" and "MyLibrary.Class2".  These are obviously the objects inside of your library that can be instantiated by OLEView.  If you expand the branch for whichever object you're interested in, you should see several COM interface "spoons" appear.  At this point, you will have effectively instantiated the object.  You should then jump back over to your MTS box and check to verify inside of Transaction Server Explorer that the object is spinning (in the Components folder of the package).
Avatar of ditkis

ASKER

THANKS!