Cool Solutions

WebAccess Agent and Domain Considerations


July 10, 2007 3:05 am






A Forum reader recently asked:

“I’m configuring a WebAccess agent running on NetWare, accessing a GroupWise domain on Linux. On Linux (the GroupWise path) there is reiserfs with no access from NetWare or Windows. But the WebAccess server will have access to this domain. The webac70a.waa-file points to the path of the domain. How can I resolve the issue of the file commgr.cfg I can’t find any more?”

And here’s the response from Jim Michael …


This is not a good setup. In general, running an agent remotely from its domain is a bad idea, and it becomes a Really Bad Idea when you don’t have native file system access to the domain, as in this case …

There are two better solutions:

1) Install a secondary domain on the NetWare box and make the Webaccess agent part of that domain (now local to it), and link the domains via IP. This is the preferred configuration.

2) Install the WebAccess agent on the Linux box (so it can be local to the domain) and install ONLY the WebAccess Application portion on the NetWare box. This will communicate with the agent over IP, and no file system access between servers is necessary.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.