![wonderware intouch 10 alarm db logger manager wonderware intouch 10 alarm db logger manager](https://docplayer.net/docs-images/40/15359764/images/page_9.jpg)
- #Wonderware intouch 10 alarm db logger manager how to
- #Wonderware intouch 10 alarm db logger manager Patch
- #Wonderware intouch 10 alarm db logger manager windows
However as I'm not including any archestra objects in the appications or DIObjects I don't think this is of any benefit to me.
#Wonderware intouch 10 alarm db logger manager Patch
I have the redundancy enabled for my AppEngine and installed the crossover patch cable. I know its possible to select queries in your historical alarm view to separate the data but I would prefer to have the data in separate DB's if possible.įor synchronizing the data in the WWALMDB across both servers is this usually completed using synchronization in SQLManagementStudio or is it possible to do it in Archestra? Is this possible?įrom my research it looks like the Alarm db logger manager can only write to a single database. I would like to have a separate WWALMDB database for each application.
![wonderware intouch 10 alarm db logger manager wonderware intouch 10 alarm db logger manager](https://i.ytimg.com/vi/HsEkUCPq-48/hqdefault.jpg)
#Wonderware intouch 10 alarm db logger manager how to
However I'm having trouble finding information on how to create redundancy for the WWALMDB. I've figured out the OS logins, audit trail and alarm logging for a simple application. As part of this I am upgrading the applications to have audit-trails, domain login etc. The project is to have redundancy between two servers. Its not intended to convert any of the existing applications symbols into archestra objects. Both applications will be managed and deployed in the same Galaxy. I'm migrating two large standalone intouch applications to Archestra 2014 (Both applications are different). Please click "report" on spam Related sub-reddits:
![wonderware intouch 10 alarm db logger manager wonderware intouch 10 alarm db logger manager](https://s3.manualzz.com/store/data/036172781_1-690e75ee1d38a924b8a1b58573c857db.png)
(*) At mods' discretion, certain self-promotion submissions from people who contribute to this sub in other ways may be allowed and tagged with the "Self-promo" flair
![wonderware intouch 10 alarm db logger manager wonderware intouch 10 alarm db logger manager](https://demo.pdfslide.net/img/380x512/reader019/reader/2020041015/5b3558f97f8b9a5f288b7786/r-1.jpg)
#Wonderware intouch 10 alarm db logger manager windows
Under security we set the server to use SQL Authentication and Windows Authentication. To fix this, logged into SQL MAnagement Studio using Windows Authentication, then right clicked on the server name in the tree and went to properties. As such it was setup to only allow Windows Authentication, and not SQL Authentication (aka Mixed mode) as required by the Wonderware products. The SQL Server had been installed using the default settings.