At present one of our ACI (SonarQube 7.7 community edition) is running with Azure SQL Server DB. Now I need to map existing Azure SQL Server database to a new ACI (SonarQube 7.9.6 community edition). I had done but ACI is not running properly and some times events/logs are not stored, and I even tired with to stop & deleted ACI (SonarQube 7.7 community edition) as well.
At our end my main priority is need to upgrade SonarQube version 7.7 to 7.9.X or newer.
Is it possible to upgrade the sonarqube image in the same ACI?
Yes, it is possible to upgrade the sonarqube and here ate the steps to upgrade the Snoarqube.
Download and unzip the SnorQube distribution.
If you're using third-party plugins, manually install plugins that are compatible with your version of SonarQube.
Update the contents of sonar.properties and wrapper.conf files
Stop your old server and start your new server.
Browse to http://yourSonarQubeServerURL/setup and reanalyze your projects to get fresh data.
Here are the links which can give you complete information regarding SonarQube upgradation.
Before you Upgrade.
Upgrade Guide.
Related
After installing MobileFirst Platform , It give No run time is there.
My configuration was given below:
1. WebSphere Application Server 8.5
2. Oracle 11g Enterprise edition
3. Mobile-first platform 7.1
Please help me to create Run-time in Mobile first Console.
From where I will download sample war file (for ex: project.war) for creating run-time environment.
You have only mentioned "after installing IBM MobileFirst" and not exactly the steps followed. Configuring IBM MobileFirst Platform has two phases:
a) Installing the application binaries into the filesystem using Installation Manager.
b) Deploying MFP admin services and runtime in to an Application server using Server configuration tool or ANT scripts. The runtime war file needs to be created using IBM MFP Studio.
If you have not performed phase 2 or only installed admin services and not the runtime, go through the information in these links:
Using server configuration tool
Using ANT scripts to deploy
To get you started with various MFP 7.1 projects , you refer and use any of the sample applications available at MFP 7.1 Getting started tutorials.
Once you have any of these sample projects loaded or a new project created in MFP studio, you can build the server side artefacts (adapters, application wlapps and runtime war) within the MFP studio or using ANT scripts:
Refer this link for further details and steps- Deploy projects.
I need to deploy an application to Worklight 6.2, but the latest IDE i have only targets for MobileFirst 7.1. I am trying to manually edit the meta/dployment.data file(pasted below). I updated the platform.version to 6.2 manually. Can someone help me with:
If someone can share a sample .wlapp archive targetted for WL 6.2, specifically iOSNative app with authentication disabled.
Or if someone can help me plug the right values into below file. Mainly this value "app.authenticity.obscuredata=23.507-9.852-31.807"
This is the content of XYZ.wlapp/meta/deployment.data file
#Deployment data.
#Tue Mar 01 14:06:35 PST 2016
app.build.time=1456869995617
app.displayname=RLReplen
platform.version=6.2.0.01.20141027-1531
app.target.category=UNDEFINED
app.ios.bundle.id=com.pr.RLReplen
app.version=1.0
app.environment=iOSnative
app.license.type=APPLICATION
app.description=A native iOS applicatio
app.native=true
app.authenticity.obscuredata=23.507-9.852-31.807
app.id=RLReplen
This is not possible, as explained in your previous question.
If you need the Studio for 6.2, then do not install Studio from Eclipse marketplace, as from there you get only the latest studio - 7.1. The latest is simply not backwards compatible, nor can it be as the product has changed significantly. You also cannot take a 7.1 project and open it in Studio 6.2 and expect it to work... or start altering it.
You need to create a new 6.2 project using Studio 6.2, and copy your implementation into it.
Please go to IBM Fix Central, download Studio for your build level (6.2), and install it manually into your Eclipse. And use that.
Only 6.2 studio will produce 6.2 server compatible projects, applications, adapters and any other artifacts.
I'm using Anypoint Studio 5.4.2 to develop Mule ESB flows targeted for Mule ESB Community Edition. I've hit a specific bug that is fixed in Mule ESB 3.7.3 - the Enterprise Edition runtime 3.7.3 is installed in Studio by default, but I want to use the Community Edition. I have checked the update site, but only 3.7.0 is available for Community Edition.
I did download the Mule ESB sources, and I'm able to build 3.7.3 community edition standalone server - that will be fine for deployment. I would like to build a Studio plugin so that I can have the 3.7.3 CE for running and testing within Studio. I have read the build instructions and browsed the source code tree, but I don't find anything pertinent - nothing interesting in the first 10 pages of Google results either.
Am I barking up the right tree here? If so, where can I find some documentation, or at least pointers, on how to get this working?
Thanks
these links might help you.
Basically, you need to change the packaging of your Mule CE project from .zip into .war so you could deploy it to tomcat.
https://docs.mulesoft.com/mule-user-guide/v/3.7/deploying-mule-as-a-service-to-tomcat
You should also be aware of the differences between CE and EE.
http://forums.mulesoft.com/questions/1261/anypoint-studio-esb-community-edition-how-does-it-work.html
I am using Anypoint Studio 5.4.2 with Enterprise Edition of 3.7.2. After looking into how server runs in studio, I believe that runtime is installed as plugin at path -
..\AnypointStudio5\plugins\org.mule.tooling.server.3.7.2.ee_5.3.2.201511052018\mule
Mule core jar along with other modules are at -
\org.mule.tooling.server.3.7.2.ee_5.3.2.201511052018\mule\lib\mule
You can take a look at similar structure in your studio and see if you can replace any jar that you have fixed.
If you want to find path of mule-core-*.jar path in studio, press CTRL+T and search for class MuleServer and check the jar path.
Edit: OR
If you have found any bug and fixed it, then you can report bug and contribute to get it fixed officially -
https://github.com/mulesoft/mule#contribute
I know that there is a separation of the lifecycle of the MFP Studio and MFP Server. What happens if the development team updated the Studio with a fix? In other words, is it supported to deploy a runtime for example v6.3.0.00.20150214-1702 to a MFP Server v6.3.0.00.20141127-1357?
The scenario you've described it a supported scenario. The MFP Server should be able to host a .war file generated from a newer MFP Studio build of the same major version (6.3, and I believe support from this scenario exists starting 6.1 or 6.2).
Of course, if you encounter a problem you should probably open a PMR on that. :)
I have downloaded the IBM Worklight Enterprise Server, trying to install Worklight server with Apache Tomcat and deploy my worklight application in my remote server.
It is mentioned in the readme file, that I need "IBM installation Manager" to install the "IBM Worklight Server".
I downloaded the IBM installation Manager and followed the steps in the readme file and installed the Worklight server in my local machine.
Installed Apache Tomcat in my remote machine and copied the worklight- jee-library.jar to the $TOMCAT_HOME/lib directory.
Is this the right way to install IBM Worklight server ?, or is there any other way to install "IBM Worklight Enterprise Server" in my remote machine from the command line ?
I am stuck at this place
Any help would be greatly appreciated.
Thanks
Suren
No, it is not the right way. Specifically, you should not copy anything into Tomcat. The installation does it for you.
The steps to follow are
Install the IBM Installation Manager version 1.5.2 and onward (available on the web). This is a one time step.
Download the Worklight server package from IBM
Point the IBM Installation Manager to the Worklight server package (File - Preferences in main screen).
Start the installation.
The installation will ask you for a path to Tomcat and will install everything that is needed inside Tomcat.
If your server does not have a GUI, the steps 3 and 4 are replaced by the so-called silent installation.
Quite often you won't have access to the server GUI but you can simply redirect the X display output to your desktop and launch IM. Ie. if you are running Linux export DISPLAY=xxx.xxx.xx:0.0
If you are running Windows just use Exceed.