FAQs: Running SirsiDynix Symphony on a Satellite Server
| • | What is SirsiDynix Symphony Anywhere? |
| • | How is the satellite server updated? |
| • | How is the main library server updated with satellite transactions? |
| • | How often should we update the satellite server(s)?? |
| • | We haven't updated in over a month. Can we still update our satellite server? |
| • | What policies need to be in place before using a satellite server? |
| • | How do we manage user access to updating and sychronizing the satellite server? |
| • | What is the process for maintaining a satellite server? |
What is SirsiDynix Symphony Anywhere?
SirsiDynix Symphony Anywhere allows sites to run SirsiDynix Symphony satellite servers so that library staff in remote locations, such as bookmobiles and other offline locations, can conduct library work with full SirsiDynix Symphony functionality. The satellite servers can be installed on a laptop or workstation, and WorkFlows can be installed on this laptop or workstation to conduct day-to-day activities. The satellite server operates independently and does not require a network or Internet connection back to the library's central SirsiDynix Symphony system.
The SirsiDynix Symphony Anywhere toolbar in the WorkFlows client displays one wizard, the Offline Connect wizard.
How is the satellite server updated?
With a temporary Internet or network connection, the Offline Connect wizard on the SirsiDynix Symphony Anywhere toolbar is used to synchronize the satellite server(s) with the library's central server so that the satellite server is as up-to-date as possible with the central server.
How is the main library server updated with satellite transactions?
The Offline Connect wizard is also used to update the central server with the transactions performed by the satellite servers.
When this wizard is run in synchronization mode, the following processes occur:
| • | Prepare local logs — local log files are prepared for submission to the main server |
| • | Transfer files to main server — local log files are sent to the main server |
| • | Prepare main server logs — main server log files are prepared for submission to satellite server |
| • | Transfer files from main server — main server log files are sent to the satellite server |
| • | Process transactions at main server — transactions from local log files are processed on the main server |
| • | Process transactions from main server — transactions from main server log files are processed on the satellite server |
Only one satellite server is synchronized at a time.
How often should we update the satellite server(s)?
It is recommended that satellite servers be updated nightly to keep the servers up-to-date and to ensure that the update and synchronization process never takes too long.
We haven't updated in over a month. Can we still update our satellite server?
If you have not updated the satellite server (or servers) within the last three weeks, you cannot use the Offline Connect wizard to update. You will need to contact SirsiDynix Customer Support to update these servers.
What policies need to be in place before using a satellite server?
Generally, the policy configuration on the central server will be included in the satellite systems.
A unique Station policy must be created for each satellite user login. When library staff members log in to the satellite server in WorkFlows, a Station policy is used in addition to the login that will indicate the source of the transactions and where they occurred. The Station policies created for the satellite user logins must be of the type “Named.”
You may need to create new User Access policies to control the remote users' access to the various modules and wizards.
You should also create property files on the central server that are associated with the remote user's login so that the library staff members operating the satellite servers have appropriate access and wizard settings. Typically, the remote users will have only staff access to WorkFlows and the satellite server. For instance, you may not want the remote users to be able to create policies or make configuration changes to the system. When the SirsiDynix Symphony Anywhere system is created, the property files on the central server are copied to the satellite servers.
How do we manage user access to updating and sychronizing the satellite server?
User access to the satellite server is controlled by the SirsiDynix Symphony administrator on the main server. The Satellite Group Manager wizard lists the Station policies used by the satellite user logins. Only those station policies registered by the Satellite Group Manager are permitted to synchronize with the central server.
What is the process for maintaining a satellite server?
The process for maintaining a satellite server is as follows.
| • | Satellite servers connect to the central server. |
| • | Log files are retrieved from the satellite servers and sent to the central server. |
| • | Transactions are processed on the central server. |
| • | Files are prepared to return to the satellite servers. |
| • | Files are moved to the satellite servers. |
| • | Transactions are processed on the satellite servers. |
| • | Satellites disconnect from the central server. |
Related topics