07-13-2021 11:16 AM
Hyland FLOS configured our app server so that the Unity Client and Web Client can authenticate successfully. We are using AD - Enhanced authentication. However, all our custom applications that use the Unity API now fail to authenticate/connect. We are using CreateDomainAuthenticationProperties(). The solution I was given was to stand up a new app server with different authentication properties in IIS just for the API. I thought that the Unity API contained all the functionality that the Unity Client has. So why do I need a second app server? Before upgrading to EP3 we were using OnBase 17 and AD - Basic authentication. Thanks for your feedback/input!
07-14-2021 08:16 AM
07-13-2021 02:11 PM
Were you requested to create a new AppServer that was identical to the one you already have? Or a new AppServer that was configured slightly differently?
Unity and Web Client may require different authentication or may require the AppServer to be configured differently in some other way than the custom applications that connect using Unity API.
CreateDomainAuthenticationProperties() indicates using Windows authentication at the AppServer level when connecting via Unity API. You may need to check what settings were needed for your Unity and Web Client to work on the AppServer level.
As others have mentioned multiple AppServers can be run on the same Windows server you shouldn't need a change to your number of servers or architecture.
Having said that, embracing separate AppServers are for different clients is actually a good thing so that they can use different AppPools so that:
1) recycling one AppPool wouldn't affect everything else.
2) a crash in one of the AppPools wouldn't affect everything else.
3) they can have be run under different credentials there is any such need.
4) they can have different configurations such as timeout settings, # of worker processes, memory limits, fail protection settings etc.
The only downside to running different AppServers (within the same Windows server) is there is slightly more memory used since each AppPool has some memory overhead. This is usually only a few hundred MBs but is considered negligible since servers usually have memory in the GB ranges assigned to them.
07-14-2021 03:05 PM
07-15-2021 05:00 AM
When you say stand up a new app server - does that mean you need a 2nd licenses for the app server? I am looking to migrate our Onbase 18.144 to EP5. I know we will need to use AD however, I am confused as to how all our 'generic' forms will be accessed by the public? We do not want to use an AD account. Currently they use generic accounts that are not on our domain. How will this work?
07-15-2021 05:11 AM
Appservers do not require a license. You can have as many appservers as you like. Generic forms (unity or eforms) can be served via a non-AD account
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.