Windows Server

cliff · Guest

Hi, everybody:

When a HIP component dll is created, it will be deployed to HIS server
using TI manager. But how about the configurable information like connection
string or wsdl url?

Can the component dll deployed in HIS still be able to read this kind of
informaiton from a conif file or how this kind of issue should be properly
handled in HIS world?

Thanks!

Rob Beardsworth [MSFT] · Guest

You will have to add configuration information to a HIPService.exe.config
file. Note that this will then be applicable to all HIPServices running on
the machine you have the file on. We don't actually copy any files from
machine to machine, so we also do not copy any config files for you.

Rob Beardsworth
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
Thread-Topic: config files for HIP component?
From: "=?Utf-8?B?Y2xpZmY=?=" <cliff@discussions.microsoft.com>
Subject: config files for HIP component?
Date: Tue, 3 May 2005 16:41:03 -0700

Hi, everybody:

When a HIP component dll is created, it will be deployed to HIS server
using TI manager. But how about the configurable information like
connection
string or wsdl url?

Can the component dll deployed in HIS still be able to read this kind of
informaiton from a conif file or how this kind of issue should be properly
handled in HIS world?

Thanks!

cliff · Guest

I post a reply just now. But looks like it got lost.

Rob:

Thanks for your help. The approach you suggested will work.

"Rob Beardsworth [MSFT]" wrote:

cliff · Guest

Rob:

Thanks for your reply. Yeah, I noiced that each HIP component will be
running as 1 windows service and there is only one HIPService.exe, so it
means multiple HIP components will share the same HIPService.exe.config file.
Since different people are working on different HIP components, it is likely
that there will be config entry name collision, eg, 2 HIP components both
read "ConnectionString" entry but actually connection strings are different.

What is the best pratice to handle this kind of situation? Let each
developer to make sure his config entry name is unique could be working, but
I don't think it is a good idea.

Thanks!

"Rob Beardsworth [MSFT]" wrote:

Rob Beardsworth [MSFT] · Guest

Well to some extent, having "ConnectionString" as a config element name for
an Object is not not really clever,as you can't really know if in the
future that object and a.n.other object (which also uses
"ConnectionString") might be in the same process. This is not a HIP problem
per se. Generally I would suggest preceding the config element names with
something that is specific to your object
"MyCompanyMyGroupMyObjectConnectionString" or similar. Some time ago we
decided against having copying the HIPService.exe with differing names.

Rob Beardsworth
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
Thread-Topic: config files for HIP component?
tFrom: "=?Utf-8?B?Y2xpZmY=?=" <cliff@discussions.microsoft.com>
References: <25B848E2-1C8C-4FCF-88C1-2529B9C2A7AA@microsoft.com>
<7J$9UqOUFHA.3928@TK2MSFTNGXA01.phx.gbl>
Subject: RE: config files for HIP component?
Date: Wed, 4 May 2005 16:10:02 -0700

Rob:

Thanks for your reply. Yeah, I noiced that each HIP component will be
running as 1 windows service and there is only one HIPService.exe, so it
means multiple HIP components will share the same HIPService.exe.config
file.
Since different people are working on different HIP components, it is
likely
that there will be config entry name collision, eg, 2 HIP components both
read "ConnectionString" entry but actually connection strings are
different.

What is the best pratice to handle this kind of situation? Let each
developer to make sure his config entry name is unique could be working,
but
I don't think it is a good idea.

Thanks!

"Rob Beardsworth [MSFT]" wrote:

cliff · Guest

Thanks, Rob, looks like it is the best way so far.

"Rob Beardsworth [MSFT]" wrote:

	Windows Server Forum Index -> Host Integration Server	All times are GMT
Page 1 of 1