AppXtender (CMIS Binding)

From Grooper Wiki
(Redirected from AppEnhancer)

This article is about the current version of Grooper.

Note that some content may still need to be updated.

2025 20232.72

AppXtender is a connection option for cloud CMIS Connections. It allows Grooper to connect to the AppEnhancer (formerly ApplicationXtender) content management system for import and export operations.

About

AppEnhancer is a "content management system that manages, organizes, and stores information from an application or as an extension to an existing application." It is an effective tool used to store documents and field data associated with those documents. AppEnhancer has both onprem and online capabilities. AppEnhancer stores documents in storage locations they call "applications".

The AppXtender binding is used to provide Grooper connectivity to AppEnhancer (formerly ApplicationXtender) applications. "AppXtender" can be selected as a connection option when configuring a CMIS Connection. After configuring the connection, AppEnhancer applications are exposed to Grooper as a CMIS Repository. CMIS Repository nodes are created as children of the CMIS Connection by importing a reference to their source location.

The AppXtender CMIS Repository allows Grooper to "see" documents in the AppEnhancer application. Once a CMIS Repository is created, you can import, export, search, and browse documents from Grooper.

  • The AppXtender binding can be used for import operations via CMIS Import using "Import Descendants" or "Import Query Results".
  • It can be used for export operations via CMIS Export.
    • AppXtender can be used for simpler "unmapped" exports, if you just want to export Grooper documents as files to an AppEnhancer application with no additional metadata fields.
    • AppXtender can also be used for "mapped" exports.
      • AppEnhancer applications allow the platform to store additional document data as fields.
      • Extracted Data Field values in Grooper can be exported to fields in the application along with the document's file.
      • In the CMIS Export setup, a Data Field in Grooper is mapped to a corresponding field in the AppEnhancer application. When the document is exported the value is copied from Grooper and entered into the mapped field in AppEnhancer.

Name Changes

ApplicationXtender is now AppEnhancer.

  • Be aware the CMIS Binding's name is still "AppXtender" in Grooper.
  • AppEnhancer may still be referred to as ApplicationXtender, AppXtender or AX by Grooper users and documentation.

    How to create an AppEnhancer connection

    Connections to AppEnhancer (formerly ApplicationXtender) are made by:

    1. Adding a CMIS Connection to the node tree.
    2. Configuring its "Connection Settings", choosing the "AppXtender" binding.
    3. Importing a reference to an application in AppEnhancer by creating a CMIS Repository.

    Click here for an interactive walkthrough

    Create a CMIS Connection

    1. Right-click a Project in the node tree (or a folder in the Project.
    2. Select "Add", then "CMIS Connection..."
    3. Enter a name for the CMIS Connection.
    4. Select "Execute".

    Configure the CMIS Connection for AppEnhancer (formerly ApplicationXtender)

    2. Use the "Connection Settings" dropdown editor to select "AppXtender".
      • The "AppXtender" binding defines settings for Grooper to connect to AppEnhancer.
      • The AppXtender binding has several configurable properties. We will detail those that are required to connect to AppEnhnacer data sources in this tutorial.
    3. Configure the "AX Web Services URL" property.
      Enter your AppEnhancer web services (formerly "AX web services") URL. See below for the most common URL formats.
      • For AppEnhancer: https://{{host_name}}/AppEnhancerServices/AxServicesInterface.asmx
    4. Enter your AppEnhancer data source's name into "Data Source Name".
      • The AppEnhancer data source is the parent repository for AppEnhancer applications.
    5. Enter the username and password for the AppEnhancer user into the "User Name" and "Password" properties.
    6. Save the CMIS Connection.

    Import an AppEnhancer CMIS Repository

    Having saved your connection settings, Grooper has established a connection to your AppEnhancer data source, and you can now import applications in AppEnhancer as storage locations in Grooper. This will create a CMIS Repository node Grooper can use to interact with files an an AppEnhancer application. To do so:

    2. Select the CMIS Connection and press the "List Repositories" button.
      • "CMIS Repositories" and "CMIS Connections" are two different things in Grooper.
      • CMIS Connections only connect Grooper to AppEnhancer.
      • CMIS Repositories represent the files in an AppEnhancer application.
    3. The "List Repositories" button lists available AppEnhancer applications that can be imported into Grooper as CMIS Repositories. Select the application you wish to import.
      • At this time, the value under "Imported" will be "False", and the dot next to it will be red. Once imported, this value will change to "True", and the dot will turn green.
    4. Press the "Import Repository" button to import the application into Grooper.
    5. In the pop-up window, ensure the listed repository is the one you wish import, and press the "Execute" button.
    6. This will add a CMIS Repository node to the CMIS Connection (as its child).
    7. Grooper will use this CMIS Repository node when importing files from or exporting Grooper documents to AppEnhancer applications.
      • The CMIS Connection only initiates the connection from Grooper to an AppEnhancer data source.
      • The CMIS Repository is a node that represents a specific application in AppEnhancer. This node allows Grooper to interoperate with the AppEnhancer application.

    Importing and Exporting with AppXtender

    Importing

    Configuring an Import Behavior

    1. Select the Content Type Node Object (Content Model, Document Type, Content Category) where you want to configure the Import Behavior.
    2. Select the Behaviors property and click "..." to open the Behaviors Editor window.
    3. Click the Add button and select Import Behavior from the dropdown list.
    4. Select the Import Definitions property and click "..." to open the Import Definitions Editor window.
    5. Click the Add button and select CMIS Import from the dropdown list.
    6. Select the CMIS Repository property and click "☰" to access the dropdown list and select the Repository where Grooper will import/map data.
    7. Choose the AppEnhancer Repository.
    8. Choose the Content Type.
    9. Configure Read Mappings and Write Mappings if necessary.
    10. Click OK when finished.
    11. Click OK in the Behaviors Editor window.
    12. Save changes.

    Submitting an Import Job with AppXtender

    1. Click the Imports icon.
    2. Click the Add New Jobs button.
    3. IMPORTANT: You will need to have an Import Watcher service installed and running prior to submitting an Import Job
    4. Add a Description.
    5. Choose an Import Provider, generally either Import Descendants or Import Query Results.
    6. Click through the Node Type Objects until locating the App Enhancer Repository, and select it.
      • If you have chosen Import Query Results, you will need to refine your import by configuring a CMIS Query.
      • For Import Descendants, no refinement is necessary unless you do not wish to pull from the root level of the Repository.
    7. If you wish to process the Batch upon import, configure the Batch Creation propery; otherwise, click Submit.
    8. Grooper will display the details of your Import Job within the list window.
    9. Once the job is complete, you can view the imported Batch by going to the Design page, then Batches --> Test --> Imported Batches and then selecting your Batch.
      • Note, that Grooper automatically names the Batch after the date and time the import job was submitted.
      • If you processed the Batch upon importing, it will be within the Productions Folder.

    Exporting

    Configuring an Export Behavior

    1. Select the Content Type Node Object where you wish to configure the Export Behavior.
    2. Select the Behaviors property and click "..." to open the Behaviors Editor window.
    3. Click the Add button and select Export Behavior from the dropdown list.
    4. Select the Export Definitions property and click "..." to open up the Export Definitions Editor window.
    5. Click the Add button and select CMIS Export from the dropdownlist.
    6. To choose the Repository you will be exporting your Batch contents to, click "☰" to open the dropdown list.
    7. Click through the Node Objects until finding the AppEnhancer Repository and select it.
    8. If you have a specific folder within the Repository where you wish to export the Batch contents, define it with the Target Folder property by clicking "..." and choosing the desired folder within the selection window.
      • If you wish to export your Batch contents to the root folder, leave the Target Folder property unconfigured.
    9. Choose the Object Type.
    10. Configure Read Mappings and/or Write Mappings if necessary.
    11. Click OK when finished.
    12. Click OK on the Behaviors window.
    13. Save changes.

    Earlier Versions of ApplicationXtentder and End of Life Support Schedule

    AppEnhancer 22.2

    Release Date: May 2022 AX rebranded itself and brings tighter internal integration, improved cloud readiness, and enhanced security enhancements.

    ApplicationXtender 20.4

    Release Date: December 2020 This version added several enhancements that significantly reduce manual document processing.

    ApplicationXtender 20.3

    Release Date: July 2020 The biggest changes brought improved cloud readiness, new internal and external integrations, and enhanced user productivity.

    ApplicationXtender 16.6

    Release Date: April 2019 This version incluced cloud readiness, product integration, and enhanced user productivity.

    ApplicationXtender 16.3

    Release Date: December 2017 This was the first version developed by OpenText, with numbering to match the OpenText numbering system. It’s added capabilities help improve information management system functionality.

    ApplicationXtender 8.1 SP1

    Release Date: February 2017 This and previous versions may be functional but did not take advantage of the newer benefits like improved application integration, better resource management and performance improvements.

    ApplicationXtender 8.1

    Release Date: June 2016

    ApplicationXtender 8.0

    Release Date: November 2015

    ApplicationXtender 7 SP1

    Release Date: August 2014

    ApplicationXtender 7.0

    Release Date: January 2014

    ApplicationXtender 6.5

    Release Date: May 2010

    ApplicationXtender 6.0

    Release Date: March 2009

    ApplicationXtender 5.4

    Release Date: December 2007

    ApplicationXtender 5.3

    Release Date: January 2006

    ApplicationXtender 5.2

    Release Date: November 2004

    ApplicationXtender 4.0

    Release Date: February 1999

    ApplicationXtender 3.0

    Release Date: March 1995

    • Retrieved from "https://wiki.grooper.com/index.php?title=AppXtender_(CMIS_Binding)&oldid=28937"