Interface SystemAdminSession

All Superinterfaces:
AutoCloseable, Closeable, OsidSession, OsidSession
All Known Subinterfaces:
SystemBatchAdminSession

public interface SystemAdminSession extends OsidSession

This session creates, updates, and deletes Systems . The data for create and update is provided by the consumer via the form object. OsidForms are requested for each create or update and may not be reused.

Create and update operations differ in their usage. To create a System , a SystemForm is requested using getSystemFormForCreate() specifying the desired record Types or none if no record Types are needed. The returned SystemForm will indicate that it is to be used with a create operation and can be used to examine metdata or validate data prior to creation. Once the SystemForm is submiited to a create operation, it cannot be reused with another create operation unless the first operation was unsuccessful. Each SystemForm corresponds to an attempted transaction.

For updates, SystemForms are requested to the System Id that is to be updated using getSystemFormForUpdate() . Similarly, the SystemForm has metadata about the data that can be updated and it can perform validation before submitting the update. The SystemForm can only be used once for a successful update and cannot be reused.

The delete operations delete Systems .

This session includes an Id aliasing mechanism to assign an external Id to an internally assigned Id.

  • Method Details

    • canCreateSystems

      boolean canCreateSystems()
      Tests if this user can create Systems . A return of true does not guarantee successful authorization. A return of false indicates that it is known creating a System . will result in a PERMISSION_DENIED . This is intended as a hint to an application that may not wish to offer create operations to unauthorized users.
      Returns:
      false if System creation is not authorized, true otherwise
      Compliance:
      mandatory - This method must be implemented.
    • canCreateSystemWithRecordTypes

      boolean canCreateSystemWithRecordTypes(Type[] systemRecordTypes)
      Tests if this user can create a single System using the desired record types. While ControlManager.getSystemRecordTypes() can be used to examine which records are supported, this method tests which record(s) are required for creating a specific System . Providing an empty array tests if a System can be created with no records.
      Parameters:
      systemRecordTypes - array of system record types
      Returns:
      true if System creation using the specified record Types is supported, false otherwise
      Throws:
      NullArgumentException - systemRecordTypes is null
      Compliance:
      mandatory - This method must be implemented.
    • getSystemFormForCreate

      SystemForm getSystemFormForCreate(Type[] systemRecordTypes) throws OperationFailedException, PermissionDeniedException
      Gets the system form for creating new systems. A new form should be requested for each create transaction.
      Parameters:
      systemRecordTypes - array of system record types
      Returns:
      the system form
      Throws:
      NullArgumentException - systemRecordTypes is null
      OperationFailedException - unable to complete request
      PermissionDeniedException - authorization failure
      UnsupportedException - unable to get form for requested record types
      Compliance:
      mandatory - This method must be implemented.
    • createSystem

      Creates a new System .
      Parameters:
      systemForm - the form for this System
      Returns:
      the new System
      Throws:
      IllegalStateException - systemForm already used in a create transaction
      InvalidArgumentException - one or more of the form elements is invalid
      NullArgumentException - systemForm is null
      OperationFailedException - unable to complete request
      PermissionDeniedException - authorization failure
      UnsupportedException - systemForm did not originate from getSystemFormForCreate()
      Compliance:
      mandatory - This method must be implemented.
    • canUpdateSystems

      boolean canUpdateSystems()
      Tests if this user can update Systems . A return of true does not guarantee successful authorization. A return of false indicates that it is known updating a System will result in a PERMISSION_DENIED . This is intended as a hint to an application that may not wish to offer update operations to unauthorized users.
      Returns:
      false if System modification is not authorized, true otherwise
      Compliance:
      mandatory - This method must be implemented.
    • getSystemFormForUpdate

      Gets the system form for updating an existing system. A new system form should be requested for each update transaction.
      Parameters:
      systemId - the Id of the System
      Returns:
      the system form
      Throws:
      NotFoundException - systemId is not found
      NullArgumentException - systemId is null
      OperationFailedException - unable to complete request
      PermissionDeniedException - authorization failure
      Compliance:
      mandatory - This method must be implemented.
    • updateSystem

      void updateSystem(SystemForm systemForm) throws OperationFailedException, PermissionDeniedException
      Updates an existing system
      Parameters:
      systemForm - the form containing the elements to be updated
      Throws:
      IllegalStateException - systemForm already used in an update transaction
      InvalidArgumentException - the form contains an invalid value
      NullArgumentException - systemForm is null
      OperationFailedException - unable to complete request
      PermissionDeniedException - authorization failure
      UnsupportedException - systemForm did not originate from getSystemFormForUpdate()
      Compliance:
      mandatory - This method must be implemented.
    • canDeleteSystems

      boolean canDeleteSystems()
      Tests if this user can delete Systems . A return of true does not guarantee successful authorization. A return of false indicates that it is known deleting a System will result in a PERMISSION_DENIED . This is intended as a hint to an application that may not wish to offer delete operations to unauthorized users.
      Returns:
      false if System deletion is not authorized, true otherwise
      Compliance:
      mandatory - This method must be implemented.
    • deleteSystem

      Deletes a System .
      Parameters:
      systemId - the Id of the System to remove
      Throws:
      NotFoundException - systemId not found
      NullArgumentException - systemId is null
      OperationFailedException - unable to complete request
      PermissionDeniedException - authorization failure
      Compliance:
      mandatory - This method must be implemented.
    • canManageSystemAliases

      boolean canManageSystemAliases()
      Tests if this user can manage Id aliases for Systems . A return of true does not guarantee successful authorization. A return of false indicates that it is known changing an alias will result in a PERMISSION_DENIED . This is intended as a hint to an application that may opt not to offer alias operations to an unauthorized user.
      Returns:
      false if System aliasing is not authorized, true otherwise
      Compliance:
      mandatory - This method must be implemented.
    • aliasSystem

      Adds an Id to a System for the purpose of creating compatibility. The primary Id of the System is determined by the provider. The new Id performs as an alias to the primary Id .
      Parameters:
      systemId - the Id of a System
      aliasId - the alias Id
      Throws:
      AlreadyExistsException - aliasId is already assigned
      NotFoundException - systemId not found
      NullArgumentException - systemId or aliasId is null
      OperationFailedException - unable to complete request
      PermissionDeniedException - authorization failure
      Compliance:
      mandatory - This method must be implemented.