Ed2003
asked on
Modifying COM+ proxy applications
I am working on a 3-tier web-fronted business system, where some support functionality is provided via desktop GUIs. Communication with the application server (middle tier) is via components in COM+ packages which are exported and the proxies installed on the desktops using the MSIs generated.
At present, when we wish to issue a new software release, the COM+ packages are rebuilt and exported in production, and the proxies installed straight away. However we are moving to a remote packaging paradigm, where the COM+ applications will need to be built and exported on a different build server, and the proxy MSIs sent away to be packaged at a remote location ready for install at the time of release. My question is whether (and how) it is possible either using MST files or otherwise to modify, at a later stage, the MSIs created on the build server so that they point at the production server. Will there be a problem with GUIDs not matching, etc?
At present, when we wish to issue a new software release, the COM+ packages are rebuilt and exported in production, and the proxies installed straight away. However we are moving to a remote packaging paradigm, where the COM+ applications will need to be built and exported on a different build server, and the proxy MSIs sent away to be packaged at a remote location ready for install at the time of release. My question is whether (and how) it is possible either using MST files or otherwise to modify, at a later stage, the MSIs created on the build server so that they point at the production server. Will there be a problem with GUIDs not matching, etc?
ASKER
I'm not sure that I understand this, but I'll have look at the COM+ console when I'm next at work and try to see what you mean. I'll repost if necessary. Please would you check out this thread again after 25/10/2004 - I'm off on holiday to Rome for the week!
Thanks very much for your help.
Thanks very much for your help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks very much for this. Can I clarify a little? If I understand you correctly, we should create the COM+ proxies in the usual way using the export function in the COM+ console. Then we can run msiexec from the command line either on the build server, or on the target workstation, and that will modify the msi file to point to the server specified in the command line argument?
The above will be fine for us, if you wouldn't mind just confirming that I've understood it correctly. I was interested that you say the process can be carried out from DCOMCNFG. Our COM+ apps don't appear in the list in DCOMCNFG - all that is there is literally DCOM apps (ie ActiveX .exe files).
The above will be fine for us, if you wouldn't mind just confirming that I've understood it correctly. I was interested that you say the process can be carried out from DCOMCNFG. Our COM+ apps don't appear in the list in DCOMCNFG - all that is there is literally DCOM apps (ie ActiveX .exe files).
You have to run this script on the client machine which is target workstation. You can ship this script with your client msi. So you use msiexec to install the msi and change remote server point to the server you specified.
In DCOMCNFG, you can find it using your GUID or progid. Some showing, some not. I am not exactly sure why.
In DCOMCNFG, you can find it using your GUID or progid. Some showing, some not. I am not exactly sure why.
ASKER
Worked like a dream!
Many thanks for your help.
Ed
Many thanks for your help.
Ed
. You have to use the same GUID.