Contents

Popular
 Contents

After the creation of Microservice component following actions can be taken:

Post Creation Action

Description

None

Generate the source code and do nothing else

Build

Generate the source and build the sources

Build and Deploy

Generate the source, build the source and register with Fiorano Enterprise Server

Building the Microservice

To build the component created, execute the command ant in the component directory. This compiles the source files, builds the required archives and creates a file export.zip containing all the files /details required for the components. export.zip can be imported using FSSM or Studio, for details regarding importing of a business component refer the Deploying in Enterprise Server section.

Deploying the Microservice

Deploying the component means registering the component on a Fiorano Enterprise Server. Any component created before it can be used in developing event process(s) has to be registered with the Fiorano Enterprise Server.

Deployment can be done in the command prompt or eStudio as explained in the following sections.

Icon

In the Offline perspective of Fiorano eStudio, deploying just brings the new service to the Micro Service Palette and the Microservice Repository.

Command Prompt

To deploy the developed component,  perform any one of the following ways.

Interactive mode

Open command prompt from the new component directory and follow the below steps:

  1. Execute the following command:

    Windows
    Linux

  2. Type "1" and press Enter.


    Figure 1: Interactive deployment mode options

    Icon

    Other options are meant to perform the following:

    • 2 - Reregister
    • 3 - Deploy to eStudio in the Offline perspective
    • 4 - Unregister
    • Exit - Exit from the interactive mode.

Non-interactive mode

Open command prompt from the new component directory and execute the following command:

A success message appears after registering the required elements required for the build deployment.


Figure 2: Build success message

Icon

In case it throws any error related to the library files, please execute the following command:


Figure 3: deploying using ant -lib command

The details of the enterprise server on which the component should be deployed are specified in build.properties file


Figure 4: Build.properties file content showing details of enterprise server on which component has to be deployed

eStudio

Icon

Before starting with the below steps, ensure that you have imported the service(s)/project(s) to the workspace.

Prerequisite

To set Ant Home, perform the following actions in eStudio:

  1. Navigate through Window > Preferences > Ant > Runtime and click the Ant Home button.
  2. Click antscripts folder present in the Fiorano_Home directory

 
Figure 5: Setting Ant Home

Icon

Failing to perform this activity leads to Build failure; the error description gets displayed in the Console view that appears.


Figure 6: Error in Console view in case Ant home is not set before running the build

 

Steps

To deploy the developed component, perform the following actions:

  1. Open Ant view using any one of the following ways:
    1. Navigating through Window > Show View > Other > Ant > Ant
    2. Click Show View as a Fast View  icon and navigate through Other > Ant > Ant.
  2. In the Ant view, right-click and select Add Buildfiles option.

     
    Figure 7: Adding Build files from Ant view
     
  3. In the Buildfile Selection pop-up, select build.xml node and click OK to add the Build XML files to the Ant view


    Figure 8: Selecting Build.xml node
     
  4. Expand the node with the new service name that appears and do the following as per the perspective:
    • Offline Event Process Development Perspective (perform any one action below)
      1. Double-click deployToStudio node
      2. Click deployToStudio node and click the Run the Selected Target  icon.
    • Online Event Process Development Perspective (perform any one action below)
      1. Double-click register node
      2. Click register node and click the Run the Selected Target  icon.
         

    Figure 9: Deploying/Registering the new component

    A console panel appears, displaying a series of messages to indicate generation of various files. The message saying "Build Successful" confirms the deployment of the service.

     
    Figure 10: Messages appearing in the Console view

Viewing the Microservice

Check the presence of new microservice in eStudio under Microservice Repository and Micro Service Palette.

Icon

Reload the services by clicking the Refresh button present in the Micro Service Palette to see the newly added services. New services appear in the Micro Service Palette as well as Microservice Repository.


Figure 11: New microservice appearing under the Microservice Repository and Micro Service Palette

Unregister and Reregister

Command Prompt

Unregister

 To unregister a custom component that is already registered with the enterprise server, execute the following command from the command line in the component directory.

Unregister

Reregister

To redeploy a component that is already registered with enterprise server in case any changes are made to the component, execute the following command from the command line in the component directory.

Reregister
Icon

The interactive mode as explained in the Command Prompt section above can also be used:

  • Enter the numebr "4" to unregister
  • Enter the number "2" to reregister

eStudio

Unregister

To unregister a custom component that is already registered with the enterprise server, perform any one of the following in Console view:

    1. Double-click unregister node
    2. Click unregister node and click the Run the Selected Target  icon.

Reregister

To redeploy a component that is already registered with enterprise server in case any changes are made to the component, perform any one of the following in Console view:

    1. Double-click register node
    2. Click register node and click the Run the Selected Target  icon.


Figure 12: Unregistering/Reregistering a deployed component

Adaptavist ThemeBuilder EngineAtlassian Confluence