{"id":234,"date":"2019-02-27T23:12:17","date_gmt":"2019-02-27T22:12:17","guid":{"rendered":"http:\/\/blog.xoupix.fr\/?p=234"},"modified":"2019-02-27T23:12:19","modified_gmt":"2019-02-27T22:12:19","slug":"about-opentext-content-server","status":"publish","type":"post","link":"https:\/\/blog.xoupix.fr\/index.php\/2019\/02\/27\/about-opentext-content-server\/","title":{"rendered":"About OpenText Content Server"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">About this page<\/h2>\n\n\n\n<p align=\"justify\">I will use this page to list some issues I encountered while installing \/ configuring OpenText Content Server or some other functionnality provided by OpenText.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Configuring OpenText Content Server with SQL Server<\/h2>\n\n\n\n<p align=\"justify\">When configuring OpenText Content Server to connect to a SQL Server database, and this specific database is not listening on default port, there is some technical difficulties to handle.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The connection string<\/h3>\n\n\n\n<p align=\"justify\">Surprisingly, OpenText Content Server seems to not understant the <em>ServerName<\/em>\\<em>Instance<\/em>,<em>Port<\/em> formalism, native from SQL Server. Each time I tried to connect to SQL Server with this connection String, a &#8220;Could not connect&#8221; error where throwned by the tables creation process&#8230;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The alias<\/h3>\n\n\n\n<p align=\"justify\">The work around to deal with this problem was to create a SQL Server alias, using the SQL Server Configuration Manager. An alias will let you configure a custom String, and redirect it to a custom instance \/ port. I created an alias named <em>ContentServer<\/em> mapped to my instance <em>ServerName<\/em>\\<em>Instance<\/em> and my port <em>Port<\/em>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">In OpenText Content Server configuration wizard<\/h3>\n\n\n\n<p align=\"justify\">Replacing my initial Server name with this simple alias <em>ContentServer <\/em>(I added a specific entry in my host file, mapping ContentServer to my initial SQL server) resolved this issue, tables were created and OpenText Content Server was ready to go !<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Error on OpenText Directory Services while calling opendj initialisation<\/h2>\n\n\n\n<p align=\"justify\">When installing OpenText Directory Services, I dealed with an issue I can&#8217;t explain. While configuring initial opendj installation, I faced a connection exception, to localhost&#8230;  All this issue was, in fact, a unsupported Java Runtime Environment version. <\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The error<\/h3>\n\n\n\n<p align=\"justify\">The only error I can retrieve in opendj logs was &#8220;Unable to connect to the server at localhost on port 4440. In non-interactive mode, if the trustStore related parameters are not used, you must use the &#8216;&#8211;trustAll&#8217; option for remote connection&#8221;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to solve<\/h3>\n\n\n\n<p align=\"justify\">Something was changed in JRE 1.8, about server name resolution. This issue was solved by installing JRE 1.7 instead of JRE 1.8. Maybe setting the server name to localhost instead another name solve the issue ?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>About this page I will use this page to list some issues I encountered while installing \/ configuring OpenText Content Server or some other functionnality provided by OpenText. Configuring OpenText Content Server with SQL Server When configuring OpenText Content Server &hellip; <a href=\"https:\/\/blog.xoupix.fr\/index.php\/2019\/02\/27\/about-opentext-content-server\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-234","post","type-post","status-publish","format-standard","hentry","category-non-classe"],"_links":{"self":[{"href":"https:\/\/blog.xoupix.fr\/index.php\/wp-json\/wp\/v2\/posts\/234","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.xoupix.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.xoupix.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.xoupix.fr\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.xoupix.fr\/index.php\/wp-json\/wp\/v2\/comments?post=234"}],"version-history":[{"count":3,"href":"https:\/\/blog.xoupix.fr\/index.php\/wp-json\/wp\/v2\/posts\/234\/revisions"}],"predecessor-version":[{"id":237,"href":"https:\/\/blog.xoupix.fr\/index.php\/wp-json\/wp\/v2\/posts\/234\/revisions\/237"}],"wp:attachment":[{"href":"https:\/\/blog.xoupix.fr\/index.php\/wp-json\/wp\/v2\/media?parent=234"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.xoupix.fr\/index.php\/wp-json\/wp\/v2\/categories?post=234"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.xoupix.fr\/index.php\/wp-json\/wp\/v2\/tags?post=234"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}