The integration of ILLiad and Aeon via two new web services makes it possible for ILLiad staff to place Aeon requests directly from the ILLiad client and for Aeon staff to respond to the requests directly from the Aeon client.
All of the following steps must be completed in order for this integration to work.
ILLiad WebPlatformConfig Table
First, we will make entries in the WebPlatformConfig table. This table provides ID information that allows ILLiad and Aeon to talk to each other.
These entries will be made in the ILLiad Customization Manager under System | Integration | WebPlatformConfig.
Aeon WebPlatformConfig Table
Next we will do the same in the WebPlatformConfig table in the Aeon Customization Manager.
Again, the table is under System | Integration | WebPlatformConfig.
Now that we have made the needed entries in the WebPlatformConfig tables, we need to enter a WebPlatformConfig Key value. This key tells ILLiad which platform configuration entry to use when trying to talk to its own web platform.
This entry will be made in the ILLiad Customization Manager under System | Web Platform | ILLiadWebPlatformConfig.
External Field Mapping
The last step in integrating ILLiad and Aeon is filling out the ExternalMapping table in the ILLiad Customization Manager. This table identifies how fields will be mapped from ILLiad to Aeon.
This would be best to discuss between the Special Collections and Interlibrary Loan departments to make sure relevant data gets to the best fields in Aeon.
This entry will be made in the ILLiad Customization Manager under System | Integration | ExternalFieldMapping.
External Field Mapping Guidelines
External Field Mapping entries will be different from institution to institution depending on specific needs and policies. These entries will map the fields from an ILLiad request to the ones in Aeon and vice versa.
The following are some example transaction entries that you can use as a template for more entries:
The final step is to restart the IIS and Odyssey Manager services on the the ILLiad server. Atlas-hosted sites will need to contact Atlas support for this restart. Locally hosted sites will need to ask their local server administrator to do this.