Practical Container Orchestration Course

Last month I attended a course about Container Orchestration in IBM Office, in Ehningen Germany.  What I learned were pretty much basics for the IBM Cloud, the course lasts for a day and I did not expect to get any in depth knowledge.

If you would like to take a look at Docker, Kubernetes, Helm, IBM Public and Private Cloud, this is good place to start. This is a fast-paced course, where you can gather a ton of information and material in order to jump start your knowledge about Containerization and IBM Cloud.  I highly recommend this course for everyone interested in this technology.  Official course description:

https://www-304.ibm.com/events/idr/idrevents/detail.action?meid=25869&ieid=15969&from=find

Advertisements

Share your Domino and Connections Ideas!

You have now a great chance to influence the development of IBM Domino and IBM Connections. Create new, vote and comment ideas for the future releases in the Domino and Connections Product Idea Labs:

https://domino.ideas.aha.io/?sort=popular

https://connections.ideas.aha.io/?sort=popular

 

 

 

JUMP Session: Understanding and Configuring IBM Connections Engagement Center (ICEC)

A Jump Session about Connections Engagement Center (ICEC) will be held at 12th of September. For details and “.ics” file, take a look at the following page:

http://www-01.ibm.com/support/docview.wss?uid=ibm10713447&myns=swglotus&mynp=OCSSYGQH&mync=E&cm_sp=swglotus-_-OCSSYGQH-_-E

If you would like to know what ICEC is all about, than the following video is a good start:

 

 

 

 

Announcing the IBM Domino V10 portfolio beta program: Sign up today

Make sure to sign up and take a look to the Domino V10 beta program.

Official Post

Beta 1: We will form an initial group of beta participants, based on the submissions received and then qualify and approve for beta program enrollment. Beta 1 will begin on June 25th, 2018.

What can be tested in Beta 1:

– Domino (Windows)
– Notes client (Windows)
– Notes, Designer & Admin clients (Windows)

This beta is English-only.

Beta 2: We will extend the initial group of Beta 1 participants as we get further along in the development cycle for Domino V10, by including additional participants at the Beta 2 stage. We expect the Beta 2 phase to begin the second half of July 2018.  Submissions received up to July 15th, for those not included in the Beta 1 group, will be considered for inclusion in the Beta 2 phase.

 What can be tested in Beta 2:

– Domino (Windows and Linux)
– Notes client (Windows and Apple Mac)
– Notes, Designer & Admin clients (Windows)
– Verse on Premises (Windows and Linux)
– DominoDB NPM package for Node.js

The goal of the IBM Domino V10 Portfolio Beta Program is for the community of beta participants to conduct honest, constructive and thoughtful review and testing of the Domino V10 beta software, which includes IBM Domino V10, IBM Notes V10, IBM Sametime V10 and IBM Verse On-Premises V10.

We’re seeking people who meet the following criteria:    

– A business end user, administrator, or developer, who has prior knowledge of Domino, Notes, and Verse.
– Those who bring diverse (role/industry/geography/company size) attributes to the beta team and, thus, ensure we get the right blend of input perspectives.

IBM is looking for participants to:

– Share their use case for the beta in their company.
– Engage in a dialog about Domino V10 and provide timely feedback.
– Be constructive and professional in all written/spoken interaction with program members, IBM and HCL.
– Attend the web conferences and meetings pertaining to the beta program.
– Experience the beta in a non-production environment.
– Be open to the idea of becoming a reference for IBM Domino V10.

IBM Sametime Update and STCore.jar File

Recently I have updated IBM Sametime Community Server from 9.0 HF1 to 9.0.1 FP1.  Before starting the update Process I would usually backup, and replace after upgrade, the following files:

  • vpuserinfo.nsf
  • names.nsf
  • STRunTimeDebugTool.jar
  • Stconfig.nsf
  • sametime.ini

And STCore.jar file, which is not stated in the official documentation, but most of the time in the past I needed to replace this file so that the community Server could be started after the upgrade.

This time, after the upgrade, not all Sametime Services could be started after the upgrade, “ST Presence Subscriptions” and “ST Presence Compatibility” would not start.

In the “STPresenceCompatibility” log file I got the following error:

[ 13:26:45.245 | 04.05.2018 | SEVERE | 13 ] : STThrowableReporterListener : notifyThrowableCaught : a toolkit throwable was caught, preparing for system exit[ 13:26:45.245 | 04.05.2018 | SEVERE | 13 ] : STThrowableReporterListener : notifyThrowableCaught : a toolkit throwable was caught, preparing for system exitjava.lang.NoSuchMethodError: com/ibm/sametime/stjavautils/utils/STUtils.belongToSameServer(Lcom/lotus/sametime/core/types/STId;Lcom/lotus/sametime/core/types/STId;)Z (loaded from file:/D:/IBM/Domino/STCore.jar by sun.misc.Launcher$AppClassLoader@f932dcd2) called from class com.ibm.sametime.buddylist.bc.channelHandler.BcToCommunityEventHandler$BLServiceAvailableListenerImpl (loaded from file:/D:/IBM/Domino/BLBackwardCompatibilitySA.jar by sun.misc.Launcher$AppClassLoader@f932dcd2). at com.ibm.sametime.buddylist.bc.channelHandler.BcToCommunityEventHandler$BLServiceAvailableListenerImpl.handleServicesAvailable(BcToCommunityEventHandler.java:192) at com.ibm.sametime.stjavautils.listener.STServiceAvailableListener.servicesAvailable(STServiceAvailableListener.java:50) at com.lotus.sametime.communityevents.CommunityEventsComp.snapshotServices(Unknown Source) at com.lotus.sametime.communityevents.CommunityEventsComp.processSTEvent(Unknown Source) at com.lotus.sametime.core.comparch.STCompPart$STCompPartSTEventListener.processSTEvent(Unknown Source) at com.lotus.sametime.core.comparch.MessageDispatcher.dispatch(Unknown Source) at com.lotus.sametime.core.comparch.MessageDispatcher.flush(Unknown Source) at com.lotus.sametime.core.comparch.MessageDispatchingThread.run(Unknown Source) at java.lang.Thread.run(Thread.java:785)[ 13:26:45.245 | 04.05.2018 | SEVERE | 13 ] : BLThrowableReporterListenerImpl : handleNotifyThrowableCaught : com/ibm/sametime/stjavautils/utils/STUtils.belongToSameServer(Lcom/lotus/sametime/core/types/STId;Lcom/lotus/sametime/core/types/STId;)Z (loaded from file:/D:/IBM/Domino/STCore.jar by sun.misc.Launcher$AppClassLoader@f932dcd2) called from class com.ibm.sametime.buddylist.bc.channelHandler.BcToCommunityEventHandler$BLServiceAvailableListenerImpl (loaded from file:/D:/IBM/Domino/BLBackwardCompatibilitySA.jar by sun.misc.Launcher$AppClassLoader@f932dcd2).[ 13:26:45.245 | 04.05.2018 | SEVERE | 13 ] : BLShutdownManager : BLShutdownManager : time has come for system exit. EXITING!!! return code: 101

I replaced the backed up “STCore.jar” file with the new one, created by the update process, and all was well. All Sametime Services started and there were no problems.