URL for software and plugins

URL for software and plugins

Softwares

For a better requirements decision, see the compatibility matrix to validate the best configurations according to the component versions you wish to use.

Webclient

Webclient 1.8.8: Download Webclient 1.8.8 (New)  here

Webclient 1.8.7: Download webclient 1.8.7 here

Webclient 1.8.5: Download webclient 1.8.5 here 

Webclient 1.8.3: Download webclient 1.8.3 here

Eclipse

  1. Eclipse 2019:
  2. Eclipse 2020 - 2022
  3. Eclipse 2023
You can Download the Eclipse version you want here
Remember that the Eclipse version you will download need to be compatible with the other softwares you download

Plugins

Plugin 1.8.8

Download plugin 1.8.8 (New) here
This plugin version only works with newest eclipse versions. (2020 or higher)

Plugin 1.8.6

Download plugin 1.8.6 here
This plugin version only works with the oldest eclipse versions (2019 or lower)

Webclient mobile

Download the webclient mobile version here

PlexBuild project

Download  plex build project here


Apache Tomcat 8.5 or higher

Download the tomcat here


Java JDK 8 or higher is required

You can download the jdk 8 here,
 You can download the jdk 11 here,
You can download the jdk 21 here

You can download the version of Java you want but keep in mind that you will need a specific version of Eclipse.

Webclient.properties file

Download the file here


Webclient Group Model

CM WebClient 6.0 Group Model (can be upgraded) Please contact support for more information about the Group models

Compatibility Matrix

Plex
version

Eclipse version

Tomcat versión

Java version

WebClient version

WebClient   plugin


6
7
7.1

Eclipse 2019 or lower

8

8

1.8.3
1.8.5

1.8.6

7.2.1

Eclipse 2019 or lower

8.5
9

8

1.8.3
1.8.5
1.8.7
1.8.8

1.8.6
1.8.8

9

1.8.7
1.8.8

1.8.8

7.2.1
7.3

Eclipse 2020 – Eclipse 2022

8.5
9

8
9

1.8.7
1.8.8

1.8.8

Eclipse 2023 - 2023-06

9

11
17
21

1.8.8
1.8.9
10.1
1.8.8 (Tomcat 10 version)
1.8.9 (Tomcat 10 version)
Eclipse 2024 - 2025
9
1.8
1.8.8
1.8.9
1.8.9
10.1
1.8.8 (Tomcat 10 version)
1.8.9 (Tomcat 10 version)


Encoding Troubleshooting Guide:

 

A discrepancy between encoding options in the workspace and plex projects can cause issues where characters are displayed with a Unicode block of character or broken text. This guide will help you solve the most common issues of encoding. 

The following step “Eclipse .ini” is for Eclipse 2024 or newer. If you’re using Eclipse 2023 or older, skip this step and start with “Eclipse Settings”.

 

Eclipse .ini (For Eclipse 2024 or newer):

A very important detail to keep in mind when using Eclipse 2024 or newer is that the default file encoding changes from Cp1252 to UTF-8 which creates a conflict when Eclipse is trying to read Plex generated files since Plex always uses Cp1252, thus when constructing webclient templates the characters will show broken text.


To verify what encoding Eclipse is using, go to Help -> About Eclipse -> Installation Details -> Configuration tab and look for the following property: 

file.encoding
 

 

 

 

If file.encoding has the value “UTF-8" assigned to it, then it means that Eclipse’s default encoding is set to UTF-8. To make sure Eclipse is using Cp1252 encoding, close Eclipse and open the root directory where it’s installed. Within the root folder, look for a file called “eclipse.ini” and open it with an editor.
 

 

 

Next will be to write the following property right below “-vmargs”:

-Dfile.encoding=Cp1252 

 

 


This will make sure that your Eclipse’s decoding logic aligns with CA Plex’s actual encoding.

Save changes and open Eclipse, go back to Help -> About Eclipse -> Installation Details -> Configuration tab to confirm that the new changes are being applied.
 

 

 

Eclipse Settings:

1)   Go to Window –> Preferences –> General --> Workspace and make sure the Text File Encoding is set to “windows-1252” (If you’re using Eclipse 2024 or newer, “Cp1252”) and Apply changes.

2)   Make sure the projects in the workspace, especially the java project, are using the encoding that was configurated in Preferences. For that right click on the project --> Properties --> Resources and for Text File Encoding select “Inherited from container” and save changes.

 

Obclient.properties Settings: 

Go to obclient.properties and look for the following properties. If you have them enabled, comment on both of them. 

#Environment.Default.PanelResourceEncoding 
#Environment.Default.ResourceFileEncoding
 


This is to ensure encoding configuration in obclient doesn’t clash with the encoding already configurated in the workspace.
 

WebClient.properties Settings:
 
Make sure the following property is set in WebClient.properties: 

webclient.encoding.httpbody=utf-8 

 

Save changes and rebuild the workspace.

 

Using UTF-8 in Eclipse:


CA Plex has the limitation of only generating panels in Cp1252 so trying to use UTF-8 encoding in Eclipse will cause text issues in the workspace and in runtime. While not recommended, if you must keep using UTF-8 in Eclipse, you can also convert your Java source files so that they use UTF-8 encoding instead of Cp1252. That way it corrects the encoding issue without modifying Eclipse’s .ini configuration. But please keep in mind that this method will require you to convert all java source files where the characters might break when creating the templates. 

To verify which encoding option the java source file is using, first open the source file in Notepad++ or VSCode. The editor will display what encoding they’re trying to read the file with. If there’s a mismatch between the file encoding and the editor’s setting, the text from a label will display it in a broken text.

 

​
Change the editor’s encoding setting to windows-1252 since CA Plex always generates panels in that option. 

 

If using windows-1252 displays the text correctly, then it means that you need to convert your java source files to UTF-8. There’s plenty of methods available to convert these files to the target encoding.

You can also use the editor to confirm that the files were converted correctly as the text will be displayed properly when using UTF-8 to read the source file.

Once confirmed they’re using the UTF-8 encoding, make sure the workspace encoding is set to UTF-8 and rebuild the workspace to generate the new web templates.

 

 

 

 

 



    • Related Articles

    • URL for Software and Documentation

      Documents Upgrade Guide Apply New License to MatchPoint Software MatchPoint 7.0 Build 004 (New) Full Installer for client installation steps see MatchPoint Client Installation Process IBM Components for the steps see Manual Installation for IBM ...

    • WebClient 1.8.8: Supports Plex 7.3

      Webclient supports Plex 7.3 you can get the lates version of webclient here You can also take a look to the "URL for software and plugins" article, to check the new Compatibility Matrix

    • CM Meta Analytics Plugins

      The CM Meta Analytics engine supports plugins in its architecture. Plugins are able to contribute functionality such as additional methods to detect input files, and data structures to store additional information. Plugins are automatically loaded at ...

    • Download WebClient Trial Software

      The WebClient Trial Software is a Live Installer application currently in development, which provides one with a self-contained WebClient solution with a trial license.  If you want to find out more about what WebClient can do for you or your ...

    • Recommended Dev Software Installation Notes

      Install CA Plex to standard program directories Install JDK in the standard program directories Create a root dev folder RootDev to contain Plex models, dev workspace, eclipse/spring software, and Tomcat <root-dev> localmodels local models and gen ...