A recording of the event and the next steps to start your contributions can be found here:
Customer Contributions to Knowledge Presentation
Let's get started!
Today we are pleased to announce another community release for docker support (version 3). As part of this enhancement now applying the patch and upgrade from a previously created container using Docker Orchestration scripts provided by OpenText for TeamSite, LiveSite, and OpenDeploy. We support 16.2 and 16.3 containerization using provided automation scripts. This release marks our third release of docker support for TeamSite, LiveSite, and OpenDeploy.
Please join us on this journey and contribute by engaging on a special focus forum: TeamSite, LiveSite, and OpenDeploy - Docker. To obtain the automation for Docker, log in to MySupport, navigate to Product>OTDN>Web Content Management (TeamSite)>TeamSite, LiveSite, OpenDeploy> Docker Automation>16.3 or Product>OTDN>Web Content Management (TeamSite)>TeamSite, LiveSite, OpenDeploy> Docker Automation>16.2.”
TS 7.4.1 to 7.5 JBOSS connection string issues
We are in the process of installing a 7.5.1 machine. Install is complete, but now we are following our documentation for custom files and scripts and bringing them up in the new environment. One of the issues we've run into is because of the JBOSS upgrade. Since JBOSS has upgraded there are changes to the back end directory structure. The jboss config file js-jboss-ds.xml under /opt/Autonomy/ApplicationContainer/server/default/deploy does not exist anymore. We have a workflow that uses a war package to basically connect to a database and look up offer IDs and display the options to the user so they can select which published DCR to retrieve in the workflow. The database connection was in js-jboss-ds.xml. With the changes I'm assuming the file /opt/Autonomy/ApplicationContainer/standalone/configuration/standalone.xml should now house the database connection string.
My suspecion is that we have some element incorrect in the connection string, but we can't seem to figuire it out. HP support gave it a shot for bit, but finally pulled to plug and urged us to hire HP professional services since this is a "custom code issue".
Basically we have the two files, one is the standalone.xml and the other is the web.xml that exists in WEB-INF in our war package.
I'll post here our connnection string, if any one sees any issue please give a heads up...
connection string in standalone.xml:
<datasource jndi-name="java:jboss/datasources/webstage" pool-name="webstage" enabled="true" use-java-context="true">
<connection-url>jdbc : oracle:thin:@bloecmt-cluster.ii-corpnet.com:1521/webstage</connection-url>
Any pointers would be appreciated, thanks.