I used the steps bellow to run my chatbot servlet application inside of a Docker container.

1 – Download WAS Liberty Docker image:

docker pull websphere-liberty

2 – Create a Docker file with the following lines

FROM websphere-liberty
ADD ChatBot.war /opt/ibm/wlp/usr/servers/defaultServer/dropins/
ADD server.xml /opt/ibm/wlp/usr/servers/defaultServer/
ENV LICENSE accept

ChatBot.war is my chatbot application.
To add features and configuration for your server you need to update the server.xml.
Do not forget to put host=”*” on httpEndpoint or you will not access the server from your browser.

The server.xml is listed below

<server description=”new server”>

<!– Enable features –>
<featureManager>
<feature>javaee-7.0</feature>
<feature>localConnector-1.0</feature>
<feature>distributedMap-1.0</feature>
<feature>webCache-1.0</feature>
</featureManager>
<basicRegistry id=”basic” realm=”BasicRealm”>
<!– <user name=”yourUserName” password=”” />  –>
</basicRegistry>
<!– To access this server from a remote client add a host attribute to the following element, e.g. host=”*” –>
<httpEndpoint host=”*” httpPort=”9080″ httpsPort=”9443″ id=”defaultHttpEndpoint”/>
<!– Automatically expand WAR files and EAR files –>
<applicationManager autoExpand=”true”/>
<applicationMonitor updateTrigger=”mbean”/>
<distributedMap id=”watsoncache” jndiName=”services/cache/watsoncache”>
<diskCache/>
</distributedMap>
<keyStore id=”defaultKeyStore” password=”password”/>
<basicRegistry id=”basic” realm=”BasicRealm”>
<user name=”user” password=”password”/>
</basicRegistry>
</server>

3 – execute docker built -t chatbot .
4 – execute docker run -d -p 80:9080 -p 443:9443 chatbot
5 – Open your browser and access your application using localhost.

docker watson WebSphere

Today i publish a Java Web Application to Bluemix, using eclipse tools.

I get the error bellow when access the app:

Caused by: java.net.UnknownServiceException: Unable to find acceptable protocols.
isFallback=false, modes=[ConnectionSpec(cipherSuites=[TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,
TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA,
TLS_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_3DES_EDE_CBC_SHA], tlsVersions=[TLS_1_2, TLS_1_1, TLS_1_0], supportsTlsExtensions=true),
ConnectionSpec(cipherSuites=[TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,
TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA,
TLS_RSA_WITH_3DES_EDE_CBC_SHA], tlsVersions=[TLS_1_0], supportsTlsExtensions=true), ConnectionSpec()], supported protocols=[TLSv1]

The application works on my machine (localhost) using WAS Liberty 16.0.0.3. and the app are using the latest watson java sdk.

I found several people with the same problem. It’s hard to understand why the lastest version of liberty on Bluemix has this problem with watson java sdk.

The solution is to use an old version of the build pack.

I did not find a way to pass parameters on eclipse to set the version of the liberty container.

Steps to solve this problem:

1 – Login to bluemix using the cf tool

2 – package your liberty profile : /wlp/bin/server package localhost –archive=server.zip –include=usr

3 – push the package to bluemix : cf push <application name> -p server.zip  -b liberty-for-java_v3_7-20170118-2046 -m 384M

 

Found the solution on this forum post

https://developer.ibm.com/answers/questions/363393/was-liberty-17001-does-not-work-with-watson-java-s/?sort=votes

WebSphere

To install atop on Centos you need to enable EPEL Repository

## RHEL/CentOS 7 64-Bit ##
# wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-9.noarch.rpm
# rpm -ivh epel-release-7-9.noarch.rpm

Use yum install atop to install on your server.

More information on this link http://www.tecmint.com/how-to-install-atop-to-monitor-logging-activity-of-linux-system-processes/

Linux

WebSphere Portal V8.0.x will be out of service  on April 30 2018.

Its time to plan the migration to 8.5 or 9.0

More information https://www-01.ibm.com/software/support/lifecycleapp/PLCDetail.wss?q45=T239753D93163X19

WebSphere Portal

If you have Basic or Advanced caching enabled in IBM® Web Content Manager, then Web Content Manager caches content artifacts independently of the cache settings that you configured for the Web Content Viewer portlet. To bypass the caching that is set in Web Content Manager, select the option Bypass Web Content Manager Caching.

This setting applies to content artifacts that are rendered in this Web Content Viewer portlet only.

This feature was added on CF11 for Portal/WCM

performance WebSphere Portal WWCM

IBM  today announced it is bringing new capabilities to enterprise social networks for a simpler collaboration across the workforce and employee onboarding experience. The latest version of IBM Connections also integrates with IBM Cloud Object Storage, providing companies an ability to scale their storage needs with their employee’s usage while improving storage costs.

IBM Connections 6.0 has been redesigned to surface the most useful content from the user’s network. This new feature – called Orient Me – leverages a new containerized, API-driven architecture to bring the most relevant information for the user to engage with – providing an interactive experience.

Read the full release news here

Uncategorized

Yesterday i start to setup some new servers and need to install several libraries on Centos 7

Yum is the first option and when i start a command like yum install <anylib> i got several erros and yum was locked.

See this short video and solve the problem.

Linux

WebSphere

One of the tuning activities is to turn on GZIP compression for HTTP requests.

This tuning can save lots of network traffic and your page will load in a short time.

Just put the lines bellow on the httpd.conf and restart the server

LoadModule deflate_module modules/mod_deflate.so

LoadModule headers_module modules/mod_headers.so

#Only the specified MIME types will be compressed.

AddOutputFilterByType DEFLATE application/atom+xml
AddOutputFilterByType DEFLATE application/atomcat+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/json
AddOutputFilterByType DEFLATE application/octet-stream
AddOutputFilterByType DEFLATE application/x-javascript
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/javascript
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/xsl
# Ensures that images and executable binaries are not compressed
SetEnvIfNoCase Request_URI \\.(?:gif|jpe?g|png|exe)$ no-gzip dont-vary
# Ensure that proxies do not deliver the wrong content
Header append Vary User-Agent env=!dont-vary
SetEnvIf Request_URI ^/acce(.*) no-gzip dont-vary

performance portal

Last month i was nominated as IBM Champion for ICS 2017  and now  IBM Champion for Cloud 2017 for the first time.

Thank you to everyone and IBM  who nominated me. It’s an honor.

What is an IBM Champion?

“IBM Champions demonstrate both expertise in, and extraordinary support and advocacy for, IBM communities and solutions.”

Screenshot2014-12-0221.53.15

Uncategorized

Domino

IBM Digital Experience V9.0 offerings provide integration with IBM Cognitive Engagement solutions
and enable hybrid cloud capability to deliver engaging multichannel experiences.
Starting with CF13, combined cumulative fixes apply to both WebSphere Portal version 8.5 and 9.0. The IBM Knowledge Center for Version 9.0 contains installation documentation and documentation on how to migrate your IBM WebSphere Application Server. After you install Version 9, return to the Version 8.5 IBM Knowledge Center for information on how to configure and use WebSphere Portal.

You can purchase an extra license (WebSphere Portal Version 9.0) to integrate WebSphere Portal with Watson Content Hub. The license gives you access to the Asset Picker portlet. Use the portlet to select assets (files, videos, and images) that are stored in the content hub and publish them on your site.
See the announcement letter here

portal