| Author |
|
pkennett
Member
Joined: 15-November-2006
Location: United Kingdom
Posts: 4
|
| Posted: 04-May-2007 at 3:58am
|
|
|
We have a potential client for Omni Mobile using WebAccess on NW already, but there are 2 possible complications:
1/ The Web Access Application is clustered and separate from the Agent: It is installed on all 3 nodes in the local Tomcat, but the SYS:/Novell stuff has been moved to a cluster volume. When the resource migrates, Apache / Tomcat is restarted on the old and new nodes to reinitialise it. Only one instance of WebAccess is ever active at any time. This works very well and gives high availability to Web Access.
I haven't seen any info on your site about clustering. I can see that I can possibly do an Omni install to each nodes while the cluster resource is local, and I can use the Cluster resource name as the Omni server name, and its IP as the local address. My question is whether this will work, and whether the Omni Mobile license will be happy with this, technically and legally? I'd hate to have to reinstall stand-alone just to get Omni to work.
2/ Their Web Access Server is reverse proxied from the Internet using iChain which is authenticated. Will this break Omni Mobile authentication from the clients? Again I haven't seen any information about this interoperability on your site.
regards
Paul Kennett
ST-FOUR
|
| Back to Top |
|
| |
Gordon Welling
Admin Group
Manager Technnical Support Services
Joined: 11-December-2003
Location: Canada
Posts: 502
|
| Posted: 07-May-2007 at 12:15pm
|
|
|
Hello, Paul.
At present, Omni Mobile server cannot be installed on fail-over clusters because the data store is normally located in the SYS:Tomcat\4\Data folder on the WebAccess Application Server. We are currently working on modifying Omni Mobile so that it could connect to a centralized data store. Once that feature is available, it would be possible to install Omni Mobile server on multiple fail-over cluster nodes of the WebAccess Application server, with Omni Mobile server installed on each node using the same Omni Mobile data store. We may have that available for a beta test within the next couple of weeks. Please pay attention to the Omni Mobile website (http://www.omni-ts.com/mobile-groupwise/) for the changelog of future releases. Additional documentation will be made available to support clustered installations.
Omni Mobile supports iChain implementations. Omni Mobile server module is still installed on the server hosting the GroupWise WebAccess Application Server. There may be a small issue with the license.key when Omni Mobile server is first installed and implemented (refer to "How to Fix Servername Licence Problem"). iChain will sometimes report a different server name to the internet browser that is not included in the Omni Mobile license.key file. If that occurs, you can contact Omni Technical Support at 780-423-4200 to request a replacement license.key file.
I recommend that you look at "Best Practices for Installing Omni Mobile" for additional information.
Edited by Gordon Welling on 08-May-2007 at 2:52pm
__________________
Gordon Welling, CNE MCSE
Account Manager & Product Specialist
www.omni-ts.com
+1.780.423.4200 Phone
+1.780.423.4711 Fax
|
| Back to Top |
|
| |
Gordon Welling
Admin Group
Manager Technnical Support Services
Joined: 11-December-2003
Location: Canada
Posts: 502
|
| Posted: 08-May-2007 at 2:51pm
|
|
|
Hello, Paul.
We believe that we can manually change the location of the Omni Mobile data store (\data folder) so that it can be placed on central location that each Omni Mobile installation would be able to properly access.
Please contact me at 780-423-4200 to make arrangements to get the detailed instructions.
Regards,
__________________
Gordon Welling, CNE MCSE
Account Manager & Product Specialist
www.omni-ts.com
+1.780.423.4200 Phone
+1.780.423.4711 Fax
|
| Back to Top |
|
| |
pkennett
Member
Joined: 15-November-2006
Location: United Kingdom
Posts: 4
|
| Posted: 12-May-2007 at 3:57am
|
|
|
Thanks for these replies Gordon. Good to know that this can be done without forcing them to have a standalone web application. At present this is a theoretical installation, as we are waiting on the client's approval. If it comes off this will be over the summer, and probably best to contact you then.
With regards to the iChain, it presents a wildcard certificate to the browser (*.domain.com), and then an iChain basic/proxy authentication popup. Credentials entered here are then used to automatically authenticate to Groupwise webaccess Are you saying Omni clients can negotiate this natively, or does it need passthrough access to the normal web login?
regards
Paul Kennett
|
| Back to Top |
|
| |
Gordon Welling
Admin Group
Manager Technnical Support Services
Joined: 11-December-2003
Location: Canada
Posts: 502
|
| Posted: 14-May-2007 at 12:16pm
|
|
|
Hello, Paul.
In answer to your questions:
1. Mobile devices do not recognize wildcard certificates. Proper certificates need to be installed on the iChain and WebAccess server.
2. iChain must be configured to permit mobile devices to have pass through access to the WebAccess server.
__________________
Gordon Welling, CNE MCSE
Account Manager & Product Specialist
www.omni-ts.com
+1.780.423.4200 Phone
+1.780.423.4711 Fax
|
| Back to Top |
|
| |
Omni Web Forum : GroupWise for PDAs and Smart Phones ~ Omni Mobile : Omni Mobile Server for GroupWise Synchronization
Topic: clustering and ichain
