Packages

  • package root
    Definition Classes
    root
  • package csw
    Definition Classes
    root
  • package framework

    This project contains the framework for creating components, such as HCDs and Assemblies.

    Framework

    This project contains the framework for creating components, such as HCDs and Assemblies.

    A component is implemented by extending the csw.framework.scaladsl.ComponentHandlers base class. These handlers are executed under an Supervisor Actor: SupervisorBehavior and TLA Actor (Top Level Actor): ComponentBehaviour defined in the framework which handles the lifecycle and supervision of this component.

    Components are controlled by a SupervisorBehavior actor that intercepts common messages (ex. Shutdown, Restart) or lifecycle messages (ex. GoOffline or GoOnline) sent from external entities to determine the state of the component.

    Components that are not in the Running state, do not receive CommandMessage.

    When Component is created using this framework, it guarantees that component (HCD/Assembly) is registered with LocationService only when Component moves to Running state. That means, one component can resolve other component only when its in Running state and ready to accept CommandMessage.

    Important Actors in Framework

    - SupervisorBehavior : Each component created by this framework is supervised by this actor.

    Default strategy of supervisor is to stop child actor but depending on nature of the failure, the supervisor has a choice of the following two options:

    Supervisor changes its csw.command.client.models.framework.SupervisorLifecycleState based on the messages it receives. Decision to handle external messages or not is taken by the supervisor based on its current csw.command.client.models.framework.SupervisorLifecycleState. For complete list of supported messages per csw.command.client.models.framework.SupervisorLifecycleState, see csw-messages project.

    - ComponentBehaviour : Like Supervisor, evey component is associate with this actor which is known as TLA (Top Level Actor) And it also maintains its own state ComponentLifecycleState based on messages it receives.

    Main purpose of this actor is to invoke component specific code written in their corresponding handlers. This is where framework code meets Component specific code.

    - PubSubBehavior : This actor is created by framework which is wrapped into csw.framework.CurrentStatePublisher for easy interaction with this actor and then passed to component handlers so that component can publish their csw.params.core.states.CurrentState.

    If one component (ex. Assembly) is interested in csw.params.core.states.CurrentState published by other component (ex. HCD) then Assembly can subscribe to HCD's current state.

    PubSub actor maintains the list of subscribers and keeps publishing csw.params.core.states.CurrentState to all subscribers.

    - ContainerBehavior : When multiple components needs to be started in container, then this actor is created. Job of this actor is just to logically group multiple components and support csw.command.client.messages.SupervisorContainerCommonMessages. It receives csw.command.client.messages.SupervisorContainerCommonMessages.Shutdown or csw.command.client.messages.SupervisorContainerCommonMessages.Restart message and forwards it to all the components residing in this container.

    deploy package

    - ContainerCmd : ContainerCmd is a helper utility provided by framework to start multiple components in container mode or single component in Standalone mode.

    Example of Container Config File

    Here is an example of a config file for creating a container with the name IRIS_Container that contains one assembly (named Filter) and depends on the services of two HCDs (Instrument_Filter and Disperser). Handler class for assembly is csw.common.components.framework.SampleComponentHandlers. A Supervisor actor will be created to manage the assembly, which includes registering it with the location service, using the given name and prefix. The prefix can be used to distribute parts of the configurations to different HCDs. HCDs register themselves with the Location Service and specify a unique prefix that can be used for this purpose.

    name = "IRIS_Container"
components: [
  {
    name = "Filter"
    componentType = assembly
    componentHandlerClassName = csw.common.components.framework.SampleComponentHandlers
    prefix = tcs.mobie.blue.filter
    locationServiceUsage = RegisterOnly
    connections = [
      {
        name: Instrument_Filter
        componentType: hcd
        connectionType: akka
      },
      {
        name: Disperser
        componentType: hcd
        connectionType: akka
      }
    ]
  },
  {
    name = "Instrument_Filter"
    componentType = hcd
    componentHandlerClassName = csw.common.components.framework.SampleComponentHandlers
    prefix = tcs.mobie.blue.filter
    locationServiceUsage = RegisterOnly
  },
  {
    name = "Disperser"
    componentType: hcd
    componentHandlerClassName: csw.common.components.framework.SampleComponentHandlers
    prefix: tcs.mobie.blue.disperser
    locationServiceUsage = RegisterOnly
  }
]
    Example of Standalone Config File 
    name = "IFS_Detector"
componentType = hcd
componentHandlerClassName = csw.common.components.framework.SampleComponentHandlers
prefix = iris.ifs
locationServiceUsage = RegisterOnly
connections = []

    - HostConfig : This is just a helper to create host configuration application. This support starting multiple containers on a given host machine and each container will have single/multiple components.

    Example of Host Config file 
    # This is a host configuration file which contains list of containers to be spawned by host configuration app
containers: [
    {
      # path of individual container configuration file
      configFilePath: "/resources/assemblyContainer.conf"
      # provide 'Remote' if file needs to fetched from config service else
      # provide 'Local' to fetch file from local machine
      configFileLocation: "Local"
    },
    {
      configFilePath: "/resources/hcdStandalone.conf"
      configFileLocation: "Local"
    }
]
    Definition Classes
    csw
  • package scaladsl
    Definition Classes
    framework
  • ComponentHandlers
  • DefaultComponentHandlers
  • RegistrationFactory
c

csw.framework.scaladsl

ComponentHandlers

abstract class ComponentHandlers extends AnyRef

Base class for component handlers which will be used by the component actor

Linear Supertypes
AnyRef, Any
Known Subclasses
JComponentHandlers, JDefaultComponentHandlers, DefaultComponentHandlers
Ordering
  1. Alphabetic
  2. By Inheritance
Inherited
  1. ComponentHandlers
  2. AnyRef
  3. Any
  1. Hide All
  2. Show All
Visibility
  1. Public
  2. Protected

Instance Constructors

  1. new ComponentHandlers(ctx: ActorContext[TopLevelActorMessage], cswCtx: CswContext)

    ctx

    the akka.actor.typed.scaladsl.ActorContext under which the actor instance of the component, which use these handlers, is created

    cswCtx

    provides access to csw services e.g. location, event, alarm, etc

Abstract Value Members

  1. abstract def initialize(): Unit

    The initialize handler is invoked when the component is created.

    The initialize handler is invoked when the component is created. The component can initialize state such as configuration to be fetched from configuration service, location of components or services to be fetched from location service etc. These vary from component to component.

    returns

    when the initialization of component completes

  2. abstract def onDiagnosticMode(startTime: UTCTime, hint: String): Unit

    On receiving a diagnostic data command, the component goes into a diagnostic data mode based on hint at the specified startTime.

    On receiving a diagnostic data command, the component goes into a diagnostic data mode based on hint at the specified startTime. Validation of supported hints need to be handled by the component writer.

    startTime

    represents the time at which the diagnostic mode actions will take effect

    hint

    represents supported diagnostic data mode for a component

  3. abstract def onGoOffline(): Unit

    A component can be notified to run in offline mode in case it is not in use.

    A component can be notified to run in offline mode in case it is not in use. The component can change its behavior if needed as a part of this handler.

  4. abstract def onGoOnline(): Unit

    A component can be notified to run in online mode again in case it was put to run in offline mode.

    A component can be notified to run in online mode again in case it was put to run in offline mode. The component can change its behavior if needed as a part of this handler.

  5. abstract def onLocationTrackingEvent(trackingEvent: TrackingEvent): Unit

    The onLocationTrackingEvent handler can be used to take action on the TrackingEvent for a particular connection.

    The onLocationTrackingEvent handler can be used to take action on the TrackingEvent for a particular connection. This event could be for the connections in ComponentInfo tracked automatically or for the connections tracked explicitly using trackConnection method.

    trackingEvent

    represents a LocationUpdated or LocationRemoved event received for a tracked connection

  6. abstract def onOneway(runId: Id, controlCommand: ControlCommand): Unit

    On receiving a command as Oneway, the onOneway handler is invoked for a component only if the validateCommand handler returns Accepted.

    On receiving a command as Oneway, the onOneway handler is invoked for a component only if the validateCommand handler returns Accepted. In case a command is received as a oneway, command response should not be provided to the sender.

    controlCommand

    represents a command received e.g. Setup, Observe or wait

  7. abstract def onOperationsMode(): Unit

    On receiving a operations mode command, the current diagnostic data mode is halted.

  8. abstract def onShutdown(): Unit

    The onShutdown handler can be used for carrying out the tasks which will allow the component to shutdown gracefully

    The onShutdown handler can be used for carrying out the tasks which will allow the component to shutdown gracefully

    returns

    when the shutdown completes for component

  9. abstract def onSubmit(runId: Id, controlCommand: ControlCommand): SubmitResponse

    On receiving a command as Submit, the onSubmit handler is invoked for a component only if the validateCommand handler returns Accepted.

    On receiving a command as Submit, the onSubmit handler is invoked for a component only if the validateCommand handler returns Accepted. In case a command is received as a submit, command response should be updated in the CommandResponseManager. CommandResponseManager is an actor whose reference commandResponseManager is available in the ComponentHandlers.

    controlCommand

    represents a command received e.g. Setup, Observe or wait

  10. abstract def validateCommand(runId: Id, controlCommand: ControlCommand): ValidateCommandResponse

    The validateCommand is invoked when a command is received by this component.

    The validateCommand is invoked when a command is received by this component. The component is required to validate the ControlCommand received and return a validation result as Accepted or Invalid.

    controlCommand

    represents a command received e.g. Setup, Observe or wait

    returns

    a CommandResponse after validation

Concrete Value Members

  1. final def !=(arg0: Any): Boolean
    Definition Classes
    AnyRef → Any
  2. final def ##: Int
    Definition Classes
    AnyRef → Any
  3. final def ==(arg0: Any): Boolean
    Definition Classes
    AnyRef → Any
  4. final def asInstanceOf[T0]: T0
    Definition Classes
    Any
  5. def clone(): AnyRef
    Attributes
    protected[lang]
    Definition Classes
    AnyRef
    Annotations
    @throws(classOf[java.lang.CloneNotSupportedException]) @native() @IntrinsicCandidate()
  6. final def eq(arg0: AnyRef): Boolean
    Definition Classes
    AnyRef
  7. def equals(arg0: AnyRef): Boolean
    Definition Classes
    AnyRef → Any
  8. final def getClass(): Class[_ <: AnyRef]
    Definition Classes
    AnyRef → Any
    Annotations
    @native() @IntrinsicCandidate()
  9. def hashCode(): Int
    Definition Classes
    AnyRef → Any
    Annotations
    @native() @IntrinsicCandidate()
  10. final def isInstanceOf[T0]: Boolean
    Definition Classes
    Any
  11. var isOnline: Boolean

    A component can access this flag, which can be used to determine if the component is in the online or offline state.

  12. final def ne(arg0: AnyRef): Boolean
    Definition Classes
    AnyRef
  13. final def notify(): Unit
    Definition Classes
    AnyRef
    Annotations
    @native() @IntrinsicCandidate()
  14. final def notifyAll(): Unit
    Definition Classes
    AnyRef
    Annotations
    @native() @IntrinsicCandidate()
  15. final def synchronized[T0](arg0: => T0): T0
    Definition Classes
    AnyRef
  16. def toString(): String
    Definition Classes
    AnyRef → Any
  17. def trackConnection(connection: Connection): Unit

    Track any connection.

    Track any connection. The handlers for received events are defined in onLocationTrackingEvent() method

    connection

    to be tracked for location updates

  18. final def wait(arg0: Long, arg1: Int): Unit
    Definition Classes
    AnyRef
    Annotations
    @throws(classOf[java.lang.InterruptedException])
  19. final def wait(arg0: Long): Unit
    Definition Classes
    AnyRef
    Annotations
    @throws(classOf[java.lang.InterruptedException]) @native()
  20. final def wait(): Unit
    Definition Classes
    AnyRef
    Annotations
    @throws(classOf[java.lang.InterruptedException])

Deprecated Value Members

  1. def finalize(): Unit
    Attributes
    protected[lang]
    Definition Classes
    AnyRef
    Annotations
    @throws(classOf[java.lang.Throwable]) @Deprecated
    Deprecated

Inherited from AnyRef

Inherited from Any

Ungrouped