Tuesday, 17 January 2017

WebSphere Developer Tools - Also does Liberty on Docker

Following my earlier post: -

I did not know ( but do now ) that the WebSphere Developer Tools also supports the WebSphere Liberty Profile on a Docker container: -

which is good to know :-)

WebSphere Developer Tools on macOS - It's been a while

I had a need to tinker with some Java in the context of WebSphere Application Server (WAS) Network Deployment (ND) 8.5.

I'm using a Mac, with WAS ND on Red Hat Enterprise Linux 6.6 on VMware, as well as WebSphere Liberty Profile 8.5.59 on Docker natively on macOS.

 Having downloaded the latest and greatest Eclipse ( Neon ) from here ( actually from IBM Bluemix here ) I then dived across to the WebSphere Developer Tools page here: 

Whilst the plugin does apparently support Neon: -

When I tried to drag/drop this into Eclipse, it didn't want to install ( and I did NOT grab the error message, more fool me ).

However, the Eclipse Market Place plugin DID provide me with the appropriate Neon version of the tools: -

Specifically, this is what I installed

so we're good to go :-)

Tuesday, 10 January 2017

IBM Operational Decision Manager and IBM WebSphere Application Server - Perhaps Not BFFs

I tried / failed to install IBM Operational Decision Manager (ODM) Rules onto a newly installed copy of WebSphere Application Server (WAS) ( aka Fixpack 11 ) today.

This is what I was trying to install: -

/opt/ibm/InstallationManager/eclipse/tools/imcl listAvailablePackages -repositories /mnt/hgfs/Software/Repo/ODM87/Product/DecisionServerRules/,/mnt/hgfs/Software/Repo/ODM87/Product/ProfileTemplateRules


Having run this command: -

/opt/ibm/InstallationManager/eclipse/tools/imcl -input /mnt/hgfs/Software/Repo/ResponseFiles/installODM87.rsp -acceptLicense

I saw this: -

ERROR: The following errors were generated while installing.
  CRIMA1209E ERROR: Validation failed for property user.wodm_was_home.
    ERROR: The product is unable to determine which edition of WebSphere Application Server is installed at the selected location. Base or Network Deployment edition of version or later is required, depending on the features selected.

    Explanation: The product is unable to determine which edition of WebSphere Application Server is installed at the selected location. Base or Network Deployment edition of version or later is required, depending on the features selected.

    User Action: 

I checked, and ensure that WAS *was* installed: -


WVER0010I: Copyright (c) IBM Corporation 2002, 2012; All rights reserved.
WVER0012I: VersionInfo reporter version, dated 2/8/12

IBM WebSphere Product Installation Status Report

Report at date and time January 10, 2017 1:55:15 PM GMT

Product Directory        /opt/ibm/WebSphere/AppServer
Version Directory        /opt/ibm/WebSphere/AppServer/properties/version
DTD Directory            /opt/ibm/WebSphere/AppServer/properties/version/dtd
Log Directory            /home/wasadmin/var/ibm/InstallationManager/logs

Product List
ND                       installed

Installed Product
Name                  IBM WebSphere Application Server Network Deployment
ID                    ND
Build Level           cf111649.01
Build Date            12/6/16
Package               com.ibm.websphere.ND.v85_8.5.5011.20161206_1434
Architecture          x86-64 (64 bit)
Installed Features    IBM 64-bit WebSphere SDK for Java
                      WebSphere Application Server Full Profile
                      EJBDeploy tool for pre-EJB 3.0 modules
                      Embeddable EJB container
                      Stand-alone thin clients and resource adapters

End Installation Status Report

I even tried installing ODM -

/opt/ibm/InstallationManager/eclipse/tools/imcl listAvailablePackages -repositories /mnt/hgfs/Software/Repo/ODM87/Product/DecisionServerRules/,/mnt/hgfs/Software/Repo/ODM87/Product/ProfileTemplateRules,/mnt/hgfs/Software/Repo/ODM87/Fixes/DS/updates,/mnt/hgfs/Software/Repo/ODM87/Fixes/PTDS/updates


but to no avail.

I then switched back to an older version of WAS - - and it just worked: -

/opt/ibm/InstallationManager/eclipse/tools/imcl -input /mnt/hgfs/Software/Repo/ResponseFiles/installODM87.rsp -acceptLicense

Installed com.ibm.websphere.odm.ds.rules.v87_8.7.1001.20151006_2017 to the /opt/ibm/ODM87 directory.
Installed com.ibm.websphere.odm.pt.rules.v87_8.7.1001.20151007_0005 to the /opt/ibm/ODM87 directory.

Interestingly, ODM 8.7.1 on WAS is supported as per the System Requirements document, but I have something that works for me :-)

Interesting, WebSphere Application Server and Java 6

I saw this: -

ERROR: Support for using Java SE 6 with WebSphere Application Server ends in April 2018.

Java SE 8 is the recommended Java SDK because it provides the latest features and security updates. You can continue to use Java SE 6, but no service can be provided after the end of support date, which could expose your environment to security risks.

You must specify the default Java SDK version on the 'user.wasjava' property. 

To install the Java 8 SDK, specify '-properties user.wasjava=java8'. 

To install the Java 6 SDK, specify '-properties user.wasjava=java6'. 

whilst trying to install the latest WebSphere Application Server (WAS) version ( 8.5.5 Fixpack 11 aka ) today, via this command: -

/opt/ibm/InstallationManager/eclipse/tools/imcl -input /mnt/hgfs/Software/Repo/ResponseFiles/installWAS855.rsp -acceptLicense

Given that I was using a response file, it was easy enough to fix, by adding an additional data.key to installWAS855.rsp: -

<profile id='IBM WebSphere Application Server V8.5' installLocation='/opt/ibm/WebSphere/AppServer'>
<data key='eclipseLocation' value='/opt/ibm/WebSphere/AppServer'/>
<data key='user.import.profile' value='false'/>
<data key='cic.selector.os' value='linux'/>
<data key='cic.selector.arch' value='x86'/>
<data key='cic.selector.ws' value='gtk'/>
<data key='cic.selector.nl' value='en'/>
<data key='user.wasjava' value='java6'/>

Now I see this: -

Installed com.ibm.websphere.ND.v85_8.5.5011.20161206_1434 to the /opt/ibm/WebSphere/AppServer directory.
WARNING: Your default Java SDK is Java SE 6. After April 2018, service for Java SE 6 can no longer be provided, which could expose your environment to security risks.

To stay current and reduce the risk of security exposures, update to Java SE 8 using one of the following options:
- Install WebSphere Application Server or later with Java SE 8.
- Install the optional IBM WebSphere SDK, Java Technology Edition, Version 8 package to an existing package group that contains WebSphere Application Server Version 8.5.
- Migrate to WebSphere Application Server traditional Version 9.   

Alternatively, to use Java SE 7, install the optional IBM WebSphere SDK, Java Technology Edition, Version 7 or 7.1 package to the package group that contains WebSphere Application Server Version 8.5.

Note that I'm explicitly choosing to use Java6, other Java versions are available :-)

More background from this: -


WebSphere Application Server v8.5 traditional

Starting in version, you must install either Java SE 6 or Java SE 8 as the version of Java SE contained in the /java and /java64 directories in WebSphere Application Server and used by default during server and node configuration. For existing installations that are being updated, your current Java level remains the same. For example, if you previously installed version with Java SE 6, and you update to version, your Java version remains Java SE 6. For information about how to migrate to Java SE 8, see Migrating to Java Platform, Standard Edition 7 or 8.
You can install Java SE 8 by using the GUI, the command line or by using response files. To install Java SE 8 using the command line or response files, you must specify the Java version by using the user.wasjava property.
  • To install Java SE 8, specify -properties user.wasjava=java8.
  • To install Java SE 6, specify -properties user.wasjava=java6.


Synology NAS - Where's my Unzip command gorn ?

I hit a wee snag earlier today, whilst attempting to unpack some IBM software on my NAS.

Being a command-line junkie, I'd SSH'd into the box: -

and was attempting to use the unzip command, as per this example: -

unzip ../../IIM18/agent.installer.linux.gtk.x86_64_1.8.5001.20161016_1705.zip

which, alas, returned: -

-sh: unzip: command not found

Thankfully, the Synology forum came to my rescue, with this: -

which led me to the fact that Synology have replaced zip with 7Zip, as per this: -

which 7z


so I now need to do this: -

7z x ../../IIM18/agent.installer.linux.gtk.x86_64_1.8.5001.20161016_1705.zip 

to unpack my file, and I'm good to go.

Thankfully, they've left tar alone, so I can still do this: -

tar xvf ../../ODM87/Product/DEC_SVR_RU_WIN_32_64_BITS_V8.7_ML.tar

which is nice :-)

For the record, this is what I'm running on the NAS: -

uname -a

Linux DiskStation 3.2.40 #8451 SMP Fri Dec 9 10:49:00 CST 2016 armv7l GNU/Linux synology_armadaxp_ds414

cat /etc/VERSION 


IBM BPM 8.5.7 - Key Assist ( or how do I do XXX ? )

I'm not sure if it's a mild case of CDO ( surely the letters ODC aren't in order ! ), but I was struggling to align some elements in a Business Process Definition.

Thus, I was looking for the zoom controls, and stumbled across Key Assis

This is, of course, a feature of Eclipse, and I've written about similar capabilities in IBM Notes

Anyway, here's the Key Assist panes for Process Designer ( I'm using 8.5.7 on Windows 7 )

For the record, the zoom controls are right there :-)

IBM BPM 8.5.7 - Web Process Designer - On YouTube

On YouTube here: -

Intro to IBM BPM 8.5.7 - Intro, build from scratch, process modeling, variables, playbacks, snapshots, default UI, new web based process editor.

We will build a Mortgage Approval process application that can run in IBM BPM. We'll take an iterative approach to building the solution. It's all done in a web browser, connected to IBM BPM in an IBM cloud.