Need to migrate my SonarQube to a new server (not the remote DB, just the application). Is there any special tool offered by Sonar to do so? is it just a matter of pointing this new installation (if possible) to the old DB?
Sonar v5.2
MySQL 5.x
Thanks!
I do this regularly as the servers I run on are only provisioned for 30 days. You don't specify the operating system, but for windows it's as simple as:
Stop "old" service
Copy folder from old machine to new machine
Install the windows service with the java wrapper
Start the service
In my case I change the DNS alias after the service is running
Related
Platform: Windows Server 2016
I have a server running weblogic 12.2.1.3. Runs great. I have another server that only has oracle DB 19c installed and on that server there are some scripts that refresh the DB from a backup weekly. I'd like to modify db scripts on the DB server to use WLST and remotely reach over to the weblogic server and stop a managed server and start it again later in the script.
What do I need to install on the DB server to run WLST?
You have 3 solutions :
Install WLS on your DB machine
Copy WLS java libs required by WLST. For instance with 12.1.3 :
$ORACLE_HOME/wlserver/modules/features/weblogic.server.merged.jar
$ORACLE_HOME/oracle_common/modules/com.oracle.cie.config-wls_8.1.0.0.jar
$ORACLE_HOME/oracle_common/modules/com.oracle.cie.config_8.1.0.0.jar
$ORACLE_HOME/oracle_common/modules/com.oracle.cie.comdev_7.1.0.0.jar
$ORACLE_HOME/oracle_common/modules/com.oracle.cie.service-table_1.1.0.0.jar
$ORACLE_HOME/oracle_common/modules/com.oracle.cie.dependency_1.1.0.0.jar
$ORACLE_HOME/oracle_common/modules/com.oracle.cie.config-wls-schema_12.1.3.0.jar
$ORACLE_HOME/oracle_common/modules/com.oracle.cie.config-security_8.1.0.0.jar
$ORACLE_HOME/oracle_common/modules/com.oracle.cie.config-owsm_8.1.0.0.jar
$ORACLE_HOME/oracle_common/modules/com.oracle.cie.wizard_7.1.0.0.jar
$ORACLE_HOME/oracle_common/modules/com.oracle.cie.encryption_2.1.0.0.jar
$ORACLE_HOME/wlserver/modules/com.oracle.css.weblogic.security.wls_7.1.0.0.jar
$ORACLE_HOME/wlserver/modules/com.oracle.css.common.security.api_7.1.0.0.jar $ORACLE_HOME/wlserver/modules/com.oracle.css.weblogic.security_7.1.0.0.jar
Use WLS REST Management API to start/stop your managed servers from your DB machine. From my point of view it is the best solution. Read this documentation for details.
The problem statement:
Suppose there are 20 windows machines within a local network. One of the machines serves as the server and hosts the database. Now, the other 19 machines have the access to read from the server machine, but the server machine does not have username and password for any of the other 19 machines.
I have to update a desktop application installed on all the machine. There is a spring-boot application, hosted on the server machine which downloads the build. Now, as soon as I download the build I have to notify all the other 19 machines that build has been downloaded so that they can read and update themselves.
Solution 1: Install a windows service which will poll the server and check if updates are available.
Solution 2: Host a POST web API on the 19 machines and notify them by making a post call. I think installing IIS or Tomcat on every machine is not viable.
Is there any other optimal solution for notifying the client?
Note: We cannot take the RDP and neither have credentials but we can make use of already deployed windows application on the other 19 clients.
Solution 3: If your machines share the same domain, use msi install packages to update software all across domain by using Group Policy. It's common way.
Solution 4: Launch desktop application directly from server shared folder. It works good while server machine is always accessible and application is not too heavy for your LAN.
Here you need some care about writing new application files while it running on client computers. Good way is to keep a different folders for different versions and launch with shortcut pointing to latest one:
v1.3\app files here
v1.4\app files here
v1.4.6\app files here
v1.7\app files here
app.lnk → v1.7\app.exe
client machines launch the application with app.lnk.
Upd: if you update application when nobody works (see 1am…2am), you can omit all of this versioning stuff.
Solution 1: It work as well. You can use NSSM to easily launch your update script or exe-file as a Windows service.
I would use a windows service or a scheduled task (both could be the same application you provide, but with some arguments). It frequently checks if a new version is available (maybe only once a day).
If you only have a short time frame when the new version has to be installed on all machines you could also provide an installation date with the new version. (Maybe the check will be done through a REST api where the client sends the current installed version number and the server answers with an status code 200 and the body is either empty or provides an json object containing the new version number, the due date and the download url.)
Then the client can already download the new version and make it available on the machine, but it triggers the installation only when the due date is reached. This check of the due date can happen more often, cause all informations are already on the client machine and can be done locally.
Can we create multiple servers in the websphere application server profile
Usually the default is server1 gets created , when you create the stand alone instance.
Yes, you can via wsadmin scripting, check details here:
Creating a server using scripting
however by default to configure and install app on that server you will need to use console installed on server1 or scripting, so it is a bit troublesome. That server will also share some configuration settings with server1 e.g. security settings.
If you want more isolation it is usually easier to just create another Application Server profile, from the same WebSphere installation (using Profile Management Tool, or manageprofiles script).
In our project we have installed both the “WebSphere application server” and “WebSphere Process Server” in a single machine. But we are unable to run both the server at a same time.
WebSphere Process Server is mounted on top of WebSphere Application Server, so while we are running the process server the default WebSphere application server instance is starting with the process server. So after that if we try to start the separately installed WebSphere application server, we are getting error that one instance is already running. Please suggest how to avoid this conflict and run both the process and application server in the single machine?
Both are using the same port. We already renamed the server name of the separately installed WebSphere application server with “server2” and Process Server’s application server name is “server1”
Please share your suggestions
You need to create separate profile. You don't have to install WAS first, or install it again, if you don't want. You may use Profile Management Tool from your installation to create new separate profile for WAS (choose Application Server profile type, not Process Server).
If you want complete separation e.g different versions (like vX of WPS and vY of WAS), or different fix pack level, you will need to do full separate WAS install.
Websphere Process Server extends Websphere Application Server (WAS), so you should install WAS first. Websphere Process Server (WPS) install should be made on top. When installation is complete you will be able to create WAS and WPS profiles on this machine. WPS profile always include WAS libraries and can be managed exactly the same way as WAS.
If you want separate servers, you should create two profiles, one for WAS and one for WPS.
You will be able to manage them separately.
I am pretty new to Windows Azure, I want to migrate existing web application that connects to remote Oracle server and run it as a cloud service web role how can I accomplish this while windows azure has no Oracle client installed by default ? or in other words how can I connect from within .net application to a 64Bit Oracle database server without installing oracle client ?
I have worked with Oracle client long time back so some of things below may not be right. But here are some of your options:
You could make use of Oracle client for .Net provided by Microsoft and add those assemblies references in your project. When you publish the project, make sure that Copy Local attribute on those assemblies are marked as true so that those DLLs get packaged along with the rest of your application.
If you're using Oracle provided client for .Net, I remember we had to install that application on our web server. In that case, you could make use of something called Startup Tasks in your webrole and install the package when your role starts. You could either include the installer as part of your package and then install the software using a startup task.