The OpenText connector has configuration options for ‘Username’ and ‘Password’. These are used with the ‘api/v1/auth’ endpoint to retrieve a ticket that is used to populate the ‘OTCSTicket’ header for further requests. An example connector configuration task section would be as follows:

[MyTask1]

OpenTextApiUrl=my.contentserver.instance/.../cs

Username=MyUser

Password=P@ssword!

Hello David  Many thanks for your reply.  I'm still unsure where the OTCSTicket goes however..?  In my postman it goes as part of the headers.  Do I add OTCSTicket to the MyTask1 and the populate the value with the retrieved ticket value..?

With the OpenText Connector, you do not need to handle or configure the OTCSTicket anywhere yourself, you only need to configure the username/password of the user you wish to authenticate as. The retrieval/handling of the OTCSTicket is done internally by the connector

Hi David  

That worked as I can now extract the xECM contents into IDOL but with no additional NiFi process I get the following results in Find:-

Any hints please on getting something closer resembling how the content is seen in xECM.  My goal is to be able to show IDOL searching across xECM repo as well as other sources, a "super search" idea if you will.

Many thanks,

Hi David  

That worked as I can now extract the xECM contents into IDOL but with no additional NiFi process I get the following results in Find:-

Any hints please on getting something closer resembling how the content is seen in xECM.  My goal is to be able to show IDOL searching across xECM repo as well as other sources, a "super search" idea if you will.

Many thanks,

Hi David  

Now I can see I was using GetOpenText which syncs data.  If I change to FetchOpenText I need an incoming connection for that and I think this is where I need some hints with please.

Many thanks,