How can we integrate opentext with workfront does any one have any idea?

SnehaKhatkole
SnehaKhatkole Member
edited October 1 in Thrust Services #1

We are trying to access opentext storage service folders and files from workfront document sections for uploading the files from opentext storage to workfront task directly. But we are facing some issues. Does anyone aware about the process of how can we achieve that.

Answers

  • Jacopo
    Jacopo Member
    #2

    Hi Sneha,

    from your description, it's not entirely clear to me which direction the connection is going and which is the leading application between xECM and Workfront. Using out-of-the-box mechanisms, you would need to utilize the REST APIs provided by both systems and write custom code. In the leading application (or the one responsible for initiating the transfer or integration), this code would invoke these APIs.

    For example, in xECM, you would need to create an OScript module to call Workfront's APIs. This requires OScript coding skills, and then you’d have to deploy the code on each node in your architecture, restart the system, and ensure you’ve implemented sufficient error handing, resiliency auditing and logging in OScript for troubleshooting purposes. Quite a lot of code. You could also manage this on the front-end, writing JavaScript to interact with both xECM's and Workfront's APIs, but I would not recommend that approach. The same applies if Workfront is the driver of communication, as you would need to write custom code in Workfront and use xECM's APIs to achieve what you need. Depending on your use case, this could involve several xECM APIs.

    However, if you have AnswerModules' Module Suite available, you can easily create custom APIs on the xECM side for Workfront to consume. You define the interface, which decouples the systems and hides any complexity behind the scenes on xECM from Workfront. Creating APIs with the Module Suite is as simple as creating a Content Script object on xECM and writing a few lines of Groovy code, leveraging existing snippets and having more than 6-7K functions and APIs at your disposal as a foundation.

    If, instead, you want xECM to call Workfront's APIs, once again, with just 4-5 lines of Groovy code inside a Content Script (which you can place in a workflow, associate with a clickable command, a scheduled job, etc.), you can invoke third-party APIs.

    You can even create a brand new connector using the "Module Suite xECM for Everything" functionality, which helps you create a connector based on the same Service Provider Interface Adapters (SPI Adapters), similar to those for SAP, Salesforce, etc., and this can be drafted in about an hour. Here you can find some further information: https://showcase.answermodules.com/resources/news/explore-limitless-integration-extended-ecm-for-everything/

    Jacopo Malnati

  • SnehaKhatkole
    SnehaKhatkole Member
    #3

    We are trying to access OpenText Content Server folders from Workfront by initiating the call from Workfront to OpenText. After providing the base URL and OAuth details, the connection reaches OpenText and prompts for login to the admin center as a tenant. However, after this step, we encounter a server error.

  • SnehaKhatkole
    SnehaKhatkole Member
    #4

    basically our main goal is to access the files and images stored in cms folders in Workfront document section

  • Jacopo
    Jacopo Member
    #5

    Hi Sneha, then it’s a “simple” authentication issue.

    Without the error details, no one will be able to help you, obviously. It’s also worth mentioning that the error could be generic, so you’ll need to investigate both at the network level and in the code. On the code side, you always have the option to debug what’s happening with OScript by using the IDE on the server you’re connecting to.

    Jacopo Malnati

  • jpluimers
    jpluimers E Community Moderator
    #6

    @SnehaKhatkole , just to be clear, are you looking to integrate with Content Server or the cloud based Core Content services like are CMS (Content Metadata Service) and CSS (Content Storage Service)?
    Reading your comments I think you want to use the cloud based content apis.

    For info about the CMS service API have a look at https://developer.opentext.com/services/products/content-metadata-service/apis/content-metadata

    For info about the CSS service API have a look at https://developer.opentext.com/services/products/content-storage-service/apis/content-storage-v3

    For detailed information about authentication have a look at https://developer.opentext.com/services/developertools/developer-admin/documentation/authentication/1

    There also is a detailed tutorial which explains how to build an application by using these services, see https://mimage.opentext.com/ot/2/devx/vscode/latest/vscode-tutorial.pdf

  • SnehaKhatkole
    SnehaKhatkole Member
    #7

    Thank you for ur response

    Are we supposed to do any whitelisting at OpenText end? to allow Workfront to access its api's

  • SnehaKhatkole
    SnehaKhatkole Member
    #8

    On the OpenText developer portal, authentication using the authorization code is failing with an "invalid redirect URI" error, though other methods like password and client credentials are working and getting authorized. Could this be affecting the authentication on the Workfront side? In Workfront, we are also using the OAuth method, where we pass the auth URL, token URL, and client credentials.

    image.png
    image.png

  • jpluimers
    jpluimers E Community Moderator
    #9

    You can add a redirect url to the service client. Adding https://developer.opentext.com/* will allow using any of the service swagger apis.
    Just be aware to remove this redirect url once you don't need it anymore.

    Navigate to you app in the org and use the contect menu 'Manage redirect URLs' to add the url.

    image.png


  • SnehaKhatkole
    SnehaKhatkole Member
    #10

    @jpluimers Thank you for your response. The authorization error on the OpenText API side has been resolved. However, I am still facing the same issues on the Workfront side.

    Do we need to whitelist Workfront URLs anywhere in the OpenText platform, or is a different subscription plan required for it to work with an external application? Currently, I am using the free trial subscription.

  • jpluimers
    jpluimers E Community Moderator
    #11

    Can you share some details of the issue? Any errors?

    What endpoint do you use, what is the request you send and what is the response from the OpenText service?

  • SnehaKhatkole
    SnehaKhatkole Member
    #12

    Sure, API urls which I am using for authentication are :

    https://us.api.opentext.com/tenants/{tenant Id}/oauth2/auth

    https://us.api.opentext.com/tenants/{tenant Id}/oauth2/token

    And the base url is

    https://us.api.opentext.com/cms/instances/folder/cms_folder

    because I want to retrieve the folder present in cms storage.

    Have attached screenshots as well :

    image.png

    image.png

    And the error we are getting when we try to add document via this option is :

    image.png

    500 Internal Server Error

    Same endpoint I am able to access it via postmon.

    image.png

  • jpluimers
    jpluimers E Community Moderator
    edited October 4 #13

    I'm not familiar with the Workfront product.

    The error is given by Workfront if I'm correct. Best to check the logs for that application.
    You proved that the urls and credentials are correct. Next step will be to look at the error in Workfront. It might give you a clue where things go wrong.

  • SnehaKhatkole
    SnehaKhatkole Member
    edited October 9 #14

    Hi @jpluimers I am getting the error when I am trying to authorize from postmon. I provided the same url you mentioned. My authentication is failing and error is :

    error_reason=scope_not_permitted&error_description=Scope+%27read%27+not+configured+on+this+OAuth+client

    do any extra configs we need to do at opentext admin center?

Categories

image
Develop with IM Services
Docs & APIs