Windows Server

Dan & Jenny · Guest

Dear All

We have a HIS domain with totally 9 Servers located in 3 different sites
(3 servers each site) , and these 3 site is connected by E1 line.
and now the configration file(COM.cfg) is around 5M. Our current issue is
the configration file sync. take 5 mins to finish which cause config file
lock for long time. is there any way I can fine tunning or compress the
configration file to fast the sync.???

Thks

lsring@hotmail.com · Guest

Our config file is also close to 5Mb and it does take a while to save the
config. Not quite 5 minutes but a couple of minutes. We are centralizing our
servers.

"Dan & Jenny" wrote:

Neil Pike · Guest

Other than removing redundant configs to reduce the filesize I can't think of
anything within HIS as you can't compress the file within HIS.

There are such things a network/application accelerators that could be put at
the ends of the E1 links and speed ransmissions based on transparently
compressing stuff and doing file delta type tracking. I've not heard of anyone
explicitly using them for HIS configs though - but it might be worth a look.

Jeremy Remlinger [MSFT] · Guest

Hello,

Host Integration Server does not have any internal mechanisms for 'tuning'
the synchronization of large configuration files between the servers. In
most instances where this has become an issue, we have made suggestions
concerning the server placement to, as LSRING suggested, a Central
deployment.

This would consolidate the HIS Servers to a central location, and would
then place the client traffic over the WAN links. However, I understand
that this would then place a large load on the WAN links to then carry the
breadth of the client traffic.

Another option is to simply break the servers into separate SNA Subdomains,
or into smaller SNA Subdomains to allow for load balancing/redundancy.

I'm afraid that there might not be an obvious 'magic bullet' that can be
used here. However, separating your SNA Subdomains into smaller chunks may
be the only real route to go.

ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸
Jeremy "Rem" Remlinger, MSCE
SNA/HIS Engineer
Microsoft

This posting is provided 'AS IS' with no warranties, and confers no rights.
© 2004 Microsoft Corporation. All rights reserved.
ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸

--------------------
Thread-Topic: HIS configration file
thread-index: AcTATfBmlSDnwKG0Q0qS0i8f/4IS7g==
X-WBNR-Posting-Host: 68.206.51.17
From: =?Utf-8?B?bHNyaW5nQGhvdG1haWwuY29t?=
<lsringhotmailcom@discussions.microsoft.com>
References: <eAt7mQCwEHA.3108@TK2MSFTNGP14.phx.gbl>
Subject: RE: HIS configration file
Date: Mon, 1 Nov 2004 12:04:05 -0800
Lines: 20
Message-ID: <F66ADD32-8744-4A45-97F9-28AC6BE29A95@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.hiserver.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.hiserver.general:4367
X-Tomcat-NG: microsoft.public.hiserver.general

Our config file is also close to 5Mb and it does take a while to save the
config. Not quite 5 minutes but a couple of minutes. We are centralizing
our
servers.

"Dan & Jenny" wrote:

lsring@hotmail.com · Guest

With earlier versions on SNA Server there used to be the option to have a
server defined as "member" instead of "backup". In that configuration the
"member" server did not get a copy of the config file if I am not mistaken
and only the backup servers got and updated copy of the com config when
changes were made. I think the original rational was for the distribution of
servers to remote sites. I hope I got that right. Perhaps this would be a
good suggestion for future releases of HIS. I think it might be good to have
something like that so that a could have a remote server if needed for local
printing but want to centralize the administration, etc... Just a thought.

"Dan & Jenny" wrote:

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