Application Extension Kit (AEK) and Connect Layer Extension Kit (CLEK)

The Application Extension Kit (AEK) is a web-based software development framework that enables you to create integration services. AEK enables you to harness device capabilities, such as GPS, NFC touchpoints, and screen rotation. AEK screens can incorporate other services, such as static content services. You can share and browse AEK code in a community repository.

Using AEK requires some experience with HTML and JavaScript, and it is useful to have experience in calling web services, parsing, JSON and XML.

For more information, see AEK (Application Extension Kit), the developers network https://developers.exlibrisgroup.com/campusm/, and the AEK documentation at AEK > Documents/Help > AEK Documentation.

Ex Libris develops and maintains a default set of AEK services and functions that are useful for many institutions.

Additionally, Ex Libris supports the Connect Layer Extension Kit (CLEK) allowing customers to independently install, use and develop their own Connect Layer services. When used in conjunction with customer-developed AEK front-end screens which invoke these services, the CLEK framework allows customers to add new end-to-end integration services to their campusM apps making the most of the campusM platform, and without the need for additional services from Ex Libris; this unlike Ex Libris-developed AEK front-end screens and Ex Libris-developed Connect Layer services which are not available for customer viewing or editing and remain Ex Libris ’ sole intellectual property. More information is available on the developers network https://developers.exlibrisgroup.com/campusm/

Joining the campusM Slack user-group

The campusM Slack user-group is a great place to share information and experiences between campusM institutions. It is also a way to interact directly with campusM staff and development.

Users may self register for Slack at the following link:

https://exlibriscampusm.slack.com/join/signup

Users should sign up using there institutional email account, using the email URL that was registered during implementation.

We are not currently able to allow vendors without an email address associated with a campusM institution, access to the campusM user-group slack.

Configuring Web Service Endpoints

You can configure web service endpoints for use by your integration services (see AEK > Documents/Help > AEK Documentation > Using Web Services).

You configure web service endpoints on the Select web service endpoint to change page (App Settings > Customer Web Services > Web Service Endpoints). This page presents a list of your web services; for information about working with lists, see Working with Lists.

For each endpoint, configure:

• Application server (mandatory) - These are configured during installation. For information about these options, contact Ex Libris customer support.
• Authentication access (mandatory) - These are configured during installation. For information about these options, contact Ex Libris customer support.
• Name / Type (mandatory) - The name or type of the service. Web services are typically given descriptive names with words separated by an underscore, such as course_timetable, exam_timetable, EXLIBRIS_ALMA, or LIBMYINFO.
• Description - The name of this service as it appears in the list in the App Manager.
• Path - The path on the server to the service, if any.
• Timetable color - The color for events of this web service in the end-user's calendar. End-users are able to filter the calendar by color.

Please note: Setting end points for customer-developed end points created using CLEK is very similar to the above, but with some small differences as described here:https://developers.exlibrisgroup.com/campusm/connect-layer-extension-kit-clek/aek-usage-of-clek-services/

campusM slow tiles handling

Clarivate has the automation and system monitoring tools to proactively identify risks and safeguard your campusM live environments and protect end users from any service disruption.

Non-Responsive AEK Tiles Policy

An AEK tile will be considered non-responsive when all of the following conditions are met:

• Average response time from the institution service endpoint is over 5 seconds.

• Timed out/User errors rate is over 1%

When an AEK tile is non-responsive Ex Libris will take the following measures:

• Contact the institution notifying them that the AEK tile is not responsive and provide relevant details including “Avg Response time(s)” and “Timed out/User errors (%)”

• The institution will have 5 business days to confirm and make the adjustment to ensure service responsiveness is correct

• After 5 business days, and if the AEK tile continues to be non-responsive, Ex Libris has the right to remove it from the app (the tile will still be available for testing and deployment through the App Manager)

Critical Non-Responsive AEK Tiles Policy

An AEK tile will be considered critical non-responsive when all of the following conditions are met:

• Average response time from the institution service endpoint is over 10 seconds.

• Timed out/User errors rate is over 10%

When an AEK tile is critical non-responsive Ex Libris will take the following measures:

• Remove the AEK tile from the app (the tile will still be available for testing and deployment through the App Manager)

• Contact the institution notifying them that that the AEK tile is not responsive and provide relevant details including “Avg Response time(s)” and “Timed out/User errors (%)”

• The institution can then make the adjustment to ensure service responsiveness is correct