1. Getting Started User Guide
  2. Service Extensions
  3. Simple Sub Domain Service

3.1 Simple Sub Domain Service

This topic provides the systematic instructions to perform the basic operations on the selected records.

This is one of the primary use cases in OBX. To generate the simple sub-domain service, follow the below steps:

  1. Navigate to same extension_home folder using cmder.
  2. Use the command obx service new -c.

    Figure 3-3 OBX Service new -c


    Description of Figure 3-3 follows
    Description of "Figure 3-3 OBX Service new -c"

  3. Once this command is fired, this will take you to next section where it will prompt other set of questions. Answer them accordingly to your setup and requirement.

    Figure 3-4 OBX UI


    Description of Figure 3-4 follows
    Description of "Figure 3-4 OBX UI"

  4. Once all the questions are answered and path of XDL is given, it will generate a folder inside the extension_home folder.

    Figure 3-5 OBX Customer Service


    Description of Figure 3-5 follows
    Description of "Figure 3-5 OBX Customer Service"

  5. Select the option based on your requirement for question Do you want to create UI component for this service? (Y/n).
  6. For building the service go into the service folder from cmder and run the command gradle clean build.
  7. This will build the service and we can find the war of the service getting created inside the build/libs directory.

    Figure 3-6 Lib's Directory


    Description of Figure 3-6 follows
    Description of "Figure 3-6 Lib's Directory"

  8. Use this service and deploy it in your environment.

Note:

  • DB scripts for the service will be generated inside the folder: \extension_home\obxcustomerservice\src\main\resources\db
  • Compile the Entity script in the entity schema created for extensions only.
  • Service created as part of extension should be deployed in separate domain and should not be mixed or co-deployed with any other product specific services.
  • Before compiling CONFIG_SCRIPT.sql in verify the entries manually and change it according to your setup.
  • Also, verify PLATO_TABLE_SCRIPT.sql before executing it in the schema it may contain some dummy values.

Parent topic: Service Extensions