I am glad you got things working. As for the future of the livelink connector, I don't believe anyone has looked at the REST api's. For SharePoint we originally thought that going to the REST solution would be a good idea, but some early results indicated that the REST API was missing key functionality we absolutely needed, so there was no point in going that route yet. If you have documentation about Livelink's REST api, I could review this at some point and determine if there's sufficient functionality to consider a migration.
Thanks, Karl On Tue, Sep 30, 2014 at 10:29 AM, Shane Ring <[email protected]> wrote: > Hi Karl, > > Quick update on our issue and solution for connecting Manifold 1.7 with > OpenText 10 SP2. Initially we used an account that authenticated against > OpenText Directory Service (OTDS) which I'm assuming will eventually > supersede the current authentication component call OpenText Content > Directory Services (OCDS). Authenticating against OTDS didn't work, but > once we used OCDS to authenticate Manifold was able to connect to OpenText > and crawl document workspaces as expected. > > On a slightly related note, are there any plans to move to supporting > OpenText, and SharePoint, using the REST APIs offered by each? Especially > for OpenText since the LAPI module seems all but deprecated (correct me if > I'm wrong)? I'm just wondering if anyone has evaluated whether or not those > APIs are mature enough to support the type of functionality that Manifold > requires. > > Thank you for the feedback and assistance! > > -Shane > > On Tue, Sep 9, 2014 at 1:29 PM, Shane Ring <[email protected]> > wrote: > >> Thanks Karl, we'll give that a try and let you know. Definitely >> appreciate the feedback. >> >> Shane >> >> On Tue, Sep 9, 2014 at 4:21 PM, Karl Wright <[email protected]> wrote: >> >>> Also, if you are in a position to compile the connector, you can edit >>> the code for >>> connector/livelink/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/livelink/LLSERVER.java >>> as follows: >>> >>> At about line 122: >>> configuration.add("HTTPS", LLValue.LL_TRUE); >>> >>> ... add: >>> System.out.println("SSL was selected"); >>> >>> Then, refresh the status page and see if this line is ever printed to >>> the console. If not, then it's LAPI that is doing something screwy. >>> >>> Thanks, >>> Karl >>> >>> >>> >>> >>> On Tue, Sep 9, 2014 at 4:03 PM, Karl Wright <[email protected]> wrote: >>> >>>> Hi Shane, >>>> >>>> I did a quick check of the Livelink Authority Connector code, and it >>>> all looks correct: >>>> >>>> >>>>>> >>>> llServer = new >>>> LLSERVER(!serverProtocol.equals("internal"),serverProtocol.equals("https"), >>>> serverName,serverPort,serverUsername,serverPassword, >>>> >>>> serverHTTPCgi,serverHTTPNTLMDomain,serverHTTPNTLMUsername,serverHTTPNTLMPassword, >>>> serverHTTPSKeystore); >>>> <<<<<< >>>> >>>> and >>>> >>>> >>>>>> >>>> public LLSERVER(boolean useHttp, boolean useSSL, String server, int >>>> port, String user, String pwd, >>>> String httpCgiPath, String httpNtlmDomain, String httpNtlmUser, >>>> String httpNtlmPassword, >>>> IKeystoreManager keystoreManager) >>>> throws ManifoldCFException >>>> <<<<<< >>>> >>>> So maybe your version of LAPI requires LLSSL whenever just "http" is >>>> selected as a protocol? >>>> >>>> Anyway, OpenText used to distribute LAPI (which included lapi.jar and >>>> llssl.jar) as a separate product/distributioI I don't knwo what they do >>>> today but that's what they used to do. >>>> >>>> Karl >>>> >>> >>> >> >
