OpenAthens LA support will end on 31 March 2020

Search

Skip to end of metadata
Go to start of metadata

Our pre-built virtual machine images come already configured with the minimum required specifications to run OpenAthens LA. Using these virtual machine images is the fastest and easiest route to getting OpenAthens LA installed and running. An enterprise class virtualisation platform is recommended.

You may install the components yourself on Red Hat derived systems if you prefer. These instructions assume you are using our images, but will highlight differences when they come up.

What is the runtime?

The Runtime is the part of OpenAthens LA that interfaces with your end-users, and performs authentication, access control and session management.

How to download

Virtual machine images:

Images are available from our service desk on request.

Considerations

The settings on the virtual image represent the minimum recomendations. Depending on your virtual infrastructure, initial deployment may the best time to alter assigned CPUs, RAM and especially hard drive space if you expect to use more (logs and statistics are the main user of space on the runtime).

Via repository:

This is configured by Yum. If you are installing on your own machine, you have probably set up admin users and networking already so can jump ahead to the yum configuration step.

Logging on to the virtual machine for the first time

Once added to your virtual infrastructure and started up you will be able to access the server via the command line. Your virtual infrastructure will give you a view, but you can also SSH from any compatible client once networking is configured.

The first thing you should do is change the default password for the 'maint' user.

Log-in using the following credentials:

Username: maint
Password: password

To change your password to a secure value:

  1. At the prompt type:

    passwd
     
  2. Enter a new password and re-enter to confirm: 

     
  3. Once the password has been updated you should be told that all authentication tokens have been updated successfully
     

Next steps:


  • No labels