Documentation
API
Q&A
Read
AnnouncementsArticlesWebsite tips
Learn
Getting StartedManagerMaestroAnalyticsExchangeWorkspaces
Resources
VideosDownloadsExchange PackagesRelease Notes
Ideas
Contact
Platform
Manager
Maestro
Exchange
Workspaces
Analytics
Springboard

Create a Form Space

   Journey Manager (JM) The transaction engine for the platform. |   System Manager / DevOps |  18.11 This feature was updated in 18.11.

Manager allows administrators to create form spaces using the Journey Manager installer, which also performs string substitutions on the context path and form space name into the portal files. Each WAR file must have a unique context path per Manager environment, such as DEV, UAT, or PROD.

Note

It's not recommended to create a copy of an existing form space WAR file as it can result in deployment issues, if all the required substitutions are not done. If the form space copy has resulted in two WAR files with the same context, the J2EE application server will only deploy one WAR file.

To create a form space:

  1. Run the Journey Manager installer - Avoka-TM-Setup.jar file.
  2. Select Create a Transact Work Space and click Next.
  3. Provide a unique form space name in the Space Name field, which Manager uses as the primary key when the form space is imported.
    Note

    Do not use the ampersand (&) character in the form space name.

  4. Type a unique context path in the Context Path field, which is a part of the URL as per the following pattern: https://{Server Domain Name}/{context path}. It's the base path to access the Web Application Archive WAR file. If the URL is https://creativewave.transactcentral.com/cwf, the context path will be cwf. In this case, the Manager URL will be https://creativewave.transactcentral.com/manager.
    Note

    The context path must be unique per environment. Do not use the ampersand (&) character in the context path.

  5. Provide a meaningful description in the Description field and click Next.
  6. Select the Production servers MUST use secure cookies checkbox. It is selected by default. You can clear this setting for a test form space to run on your own PC. Do not configure test form spaces for clients.
  7. Select the Groovy Services checkbox. It is selected by default. You can clear this setting for a test form space to run on your own PC.
  8. Click Next.
  9. Specify a directory where the installer creates a form space in the Installation Directory field. Default is the C:\avoka-tm-custom-work-space directory on a Windows PC.
    Note

    If you are creating several form spaces, it's recommended to create a unique installation directory, for example, C:\avoka-tm-custom-work-space-cwf.

  10. Click Next.
  11. Click Install to create the form space WAR file in the specified directory.
  12. Locate the form space WAR file in the deploy directory created in your installation directory, for example, C:\avoka-tm-custom-work-space-cwf\deploy\avoke-sf-portal-cwf.war.
  13. Open the readmy.html file, located in the installation directory, for example, C:\avoka-tm-custom-work-space-cwf\readme.html, to check how to use the form space.
  14. Import the form space into Manager.

Next, learn how to configure form space properties.