I have downloaded an iFix from IBM fix central (6.1.0.02.20150520-1015) for Worklight Server and Worklight Studio but I could not locate the below jar files.
Applicationcenterdeploytool.jar
Ibm-java-x86_64-sdk-7.0.-6.0.bin
Json4j.jar
Wlpdevelopers-runtime-8.5.5.2.jar
Can you confirm if the above jar files are also specific to worklight version and will be seen post WL server installation or are they generic files which can used with any WL version which can be used by jenkins build scripts.
Ibm-java-x86_64-sdk-7.0.-6.0.bin - this is IBM's version of Java. This is not bundled with either a GM or iFix or Fix Pack. You're downloading this yourself prior to any installation, if you choose to use it.
Wlpdevelopers-runtime-8.5.5.2.jar - I have no idea what that is. Looks like some WAS or WAS Liberty profile file, which you also install separately from Worklight
Applicationcenterdeploytool.jar - located post-install at install-directory/ApplicationCenter/tools/applicationcenterdeploytool.jar and is the deploy tool of Application Center, used by the ant task scripts.
Json4j.jar - located post-install at install-directory/ApplicationCenter/tools/json4j.jar and is used to handle the JSON file format
Related
I need some information of log4j2 for updating our central versions of Mule CE 3.9.0 and Mule CE 3.9.5 (CE=Community Edition).
What is the best way to protect them and does downloading only jar files from Apache site https://dlcdn.apache.org/logging/log4j/2.12.3/ be useful to patch Mule CE 3.9?
Regards
As a summary you only need to find the vulnerable jars in the mule-server and in the mule flows deployed in the apps folder.
A Java project is a set of java class and libraries with complex dependencies relationship, but easy to replace one of them (manually or automated with maven), so no matter how or where log4j is being used, we just need replace the jar file.
mule community server 3.9.0
In this version, with this command find . -type f -iname "*log4j*" we will get the log4j jars:
As we can see, the version prior to the 2.14.x
log4j-jul-2.8.2.jar
log4j-jcl-2.8.2.jar
log4j-slf4j-impl-2.8.2.jar
log4j-core-2.8.2.jar
log4j-api-2.8.2.jar
log4j-1.2-api-2.8.2.jar
But according to the official maven repository, this version is affected too :(
Just the 2.17.0 is safe to use
Source: https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-core
If this change breaks your mule, just delete the specific vulnerable class:
zip -q -d
log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class
Source: https://www.docker.com/blog/apache-log4j-2-cve-2021-44228/
mule flow or mule app
This is not the server, is the app developed by programmers, packaged as .zip and deployed to the mule apps folder in the server.
In this layer, the app can ignore completely the server configurations and has its own jar versions.
If you don't use maven (rare), you need to search and replace the jar, app by app, similar to the server with find command but in the specific app folder:
/opt/mule_server/apps/my-mule-app
If you use maven, you could find if the jar is used with the pom.xml previewer of Eclipse Ide or with command mvn dependency:tree. Check this:
https://stackoverflow.com/a/68916675/3957754
Remember: If you not use directly this jar, you need to check if mule esb server uses it.
Here some tips from manual to automated pipelines:
mule esb monolithic with manual deployment
In this case you need to fix the server and your apps.
for the server, backup, stop, search the jar on lib folder and replace it with the 2.17 (after vulnerability fix) and start. Test if everything is working
for the mule apps, the process is the same: stop the mule server, go to your mule apps and one by one, search the jar and replace it. Start the mule server and test if everything is working
git repository , maven and one mule app by server
In this case, you don't have a big server with a big mule containing a lot of mule apps/flows. You have one light server for just one mule app.
Just search the dependency in your pom with maven and replace it.
Push your changes and in the next deploy( manual or automated) your mule app will be fixed.
Also note that this approach fix the app, not the server.
git, docker
If you are using docker, the things are easy. Just search the Dockerfile (usually in a git repository). In this file there are a lot of sentences, since the java installation until the star of mule server.
Choose the exact line between the download of mule and the start of server and put a sentence which replace the jar file
Next deploy will pick you new image version and that's all.
automated flow(devops)
Here you are using maven, gi, docker and some ci server. You just need:
update the git repository of your mule app (maven)
update the git repository of your docker image
deploy your fix using the ci server.
With this, you will not need human access to the production servers to fix your java application ( mule)
We just had installed the latest iFix (7.0.0.0-MFPF-Server-IF201611140235) in our app server. Upon checking the version in the MFP Console, it still in the previous version. I've checked the directory /opt/IBM/MobileFirst_Platform_Server/WorklightServer, and found that the .war files not been updated. I've check the installation history and it shows that I successfully installed/updated it. I also noticed that the file worklight-jee-library.jar still in the previous version.
How should I refresh the files? Looks like the installation is not updating the .war files and libraries.
Thanks,
Jonathan
From the comments:
What we did is to manually copy the WAR and JAR files to Tomcat folders (/webapps and/ lib). It is now showing the correct version in the console. We recompile the app using this iFix version (IF201611140235), and deploy the new app WAR file to the server.
We are developing a mobile app using IBM MobileFirst platform.
We compile the code using the command line tool with the command 'mfp build' and deploy it using 'mfp deploy', and we are able to preview the application from the URL mentioned below: http://localhost:xxxxx/worklightconsole/index.html
After doing 'mfp build' I get these 6 files:
mobapp.war
mobAppAdapter.adapter
Dashboard-all.wlapp
Dashboard-common.wlapp
Dashboard-desktopbrowser-1.0.wlapp
Dashboard-ipad-1.2.wlapp
Questions:
Where can I find the 6 files in 'worklight console'? (or)
Which other URL I have to refer to verify whether the files have been deployed correctly or not?
Because when I type in 'mfp build' it deploys the files but we are not sure where its getting deployed. We don't have WAS installed instead 'liberty' is used to our knowledge
The MobileFirst Platform CLI tool contains an embedded WebSphere Liberty profile server inside of it. It is this server and its internal database (during development time(!)), that the artifacts you have mentioned get deployed to.
You create a project ("mfp create").
You then start the server ("mfp start").
You then create your applications, develop them, etc...
Eventually you build and deploy it to the server ("mfp build", "mfp deploy").
The resulting files of the build command are the .adapter and .wlapp files.
These get deployed using the deploy command to the server's database.
You then see these files in the console using "mfp console".
The .war file is your project's runtime, containing metadata required for various server operations. This file is part of the server and handled automatically by the underlying tooling. This is invisible to you during development.
Background
Download and install IntelliJ 12.04 Community Edition
Create project from external source (point to Gradle build script)
Specify JDK 7 as project's SDK
Note: Project is open source at github: Netflix/karyon
Problem
Want to simply war the project. In playing on the commercial version with GAE plugin installed, I was able to specify the Web Application facet, and create the war via the artifact functionality. With the setup described above, the only available facet is Android.
Question
How can I create a self sufficient war (includes all dependencies and hence can be dropped in any container without additional classpath requirements) from within the IDE?
IntelliJ IDEA Community edition doesn't have Java EE support, you need to use some other tool for packaging the war (e.g. Maven).
currently I am having following version of clear case on my local machine.
I downloded plugin "com.rational.clearcase.win32-20081031A" from url: "http://www3.software.ibm.com/ibmdl/pub/software/rationalsdp/clearcase/ccplugin/com.rational.clearcase.win32-20081031A.zip" which include following files in feature and plugin folders.
3.then I installed this plugin from eclipse Help->Software update-> search and install->given here local path of plugin folder which looks like following screen shot 4. It got installed on eclipse;but when I am trying tu connect through it it's giveing me following error.
can you please suggest whats going wrong in it?
That plugin won't work with CCRC (ClearCase Remote Client), only with a full base ClearCase installation.
CCRC comes with its own Eclipse interface, in which you will find all the necessary ClearCase commands.
If you want a CCRC plugin (which is different from the SCM Adaptor you have downloaded), you need to download it from your CCRC server, as I detail in your last question.