||
Skip to end of metadata
Go to start of metadata

Generally, it is recommended to add new asset types and lifecycles to ES via the ES Management Console. However, if you need to add a new asset type and lifecycle before server start-up, you need to directly add the asset type and lifecycle via the file system.

Follow the instructions below add an asset type and lifecycle before server start-up.

  1. Add the asset type named device to ES.

    1. Navigate to the <ES_HOME>/repository/resources/rxts directory.

    2. Save the device.rxt file in the above mentioned directory path.

  2. Add the lifecycle named DeviceLifeCycle2 to ES.
    1. Navigate to the <ES_HOME>/repository/deployment/server/jaggeryapps/publisher/extensions/lifecycles directory.

    2. Save the DeviceLifeCycle2.xml file in the above mentioned directory. If you were to create the lifecycle definition from scratch, note that the name of the lifecycle and the name of the XML file defining the lifecycle should be identical. For example when naming the lifecycle definition DeviceLifeCycle2.xml the lifecycle should be named as DeviceLifeCycle2 as shown below.

      When adding a lifecycle to the <ES_HOME>/repository/deployment/server/jaggeryapps/publisher/extensions/lifecycles directory, you need to make sure that the name of the lifecycle and the name of the XML file defining the lifecycle is identical. For example when naming the lifecycle definition DeviceLifeCycle2.xml the lifecycle should be named as DeviceLifeCycle2 as shown below.

      <aspect name="DeviceLifeCycle2" class="org.wso2.jaggery.scxml.aspects.JaggeryTravellingPermissionLifeCycle">
  3. Optionally, attach the lifecycle named DeviceLifeCycle2 to the device asset type. For more information, see steps 1 to 3 in Attaching a Lifecycle to an Asset Type.

  4. Start the ES server.

 

  • No labels