following is a paragraph from glassfish 3.1.2.2 administration guide
You can rotate log files manually by using the rotate-log subcommand
in remote mode. The default target of this subcommand is the DAS.
Optionally, you can target a configuration, server, instance, or
cluster.You can rotate log files manually by using the rotate-log
subcommand in remote mode. The default target of this subcommand is
the DAS. Optionally, you can target a configuration, server, instance,
or cluster.
what is the difference between configuration, server, instance and cluster ? i understand cluster is a collection of instances. but what is difference between server and instance and configuration ?
From the Glassfish admin guide:
The default target for these two subcommands is the DAS. However, you
can optionally specify one of the following targets:
Configuration: to target all instances or clusters that share a specific configuration name.
Server: to target only a specific server.
Instance: to target only a specific instance.
Cluster: to target only a specific cluster.
A GlassFish Server instance is a single Virtual Machine for the Java
platform (Java Virtual Machine or JVM machine) on a single node in
which GlassFish Server is running. A node defines the host where the
GlassFish Server instance resides.
and
It is usually sufficient to create a single server instance on a
machine, since GlassFish Server and accompanying JVM are both designed
to scale to multiple processors. However, it can be beneficial to
create multiple instances on one machine for application isolation and
rolling upgrades.
This means you can have multiple instances of glassfish running on a single server, and you can either target a single instance or the whole server.
Related
I am seeking to set up a Release Pipeline in Azure DevOps Services that will deploy
an application to a Unix server, where it then executes some unix commands as part
of the deployment.
Would appreciate some guidance on which pipeline Task(s) I can set up to therefore
achieve the following objectives:
Connect to the Unix server.
Execute the required Unix commands.
By the way, the Agents are currently installed on Windows hosts but we are looking to
extend that to Unix servers in due course, so a solution that fits both setups would
be ideal, even though the former is the priority.
You can check out task SSH Deployment task.
Use this task to run shell commands or a script on a remote machine using SSH. This task enables you to connect to a remote machine using SSH and run commands or a script.
If you need to copy files to the remote linux server. You can check out Copy Files Over SSH task.
You probably need to create a SSH service connection. See steps here to create as service connection.
In the end, due to concerns raised about the install of private keys on the target server which is part of the SSH Deployment setup, we opted for the use of Deployment Groups which has enabled us to set up a persistent connection to our Linux server.
According to documentation many cordapps can be deployed to a single node that lives in /opt/corda. Can I deploy additional nodes on the same VM?
Yes, each node gets its own base directory under /opt. You can have N number of nodes on a single VM. For example:
/opt/PartyA
/opt/PartyB
etc
Each node must have it's own entry in systemctl have the service started.
If all nodes are running the same application you can put all configuration in the same base directory. However, this is more difficult because each node must specify its own configuration -config-file foo.conf, database, certificates, message queue, etc.
How can I deploy and run Corda nodes of spring webserver based "Yo!CorDapp" example (https://github.com/joeldudleyr3/spring-observable-stream), on separate machines?
What are the configuration changes I need to implement in this regard.
As long as you are running each server on the same machine as the node it talks to, there shouldn't be any configuration required.
Simply start the nodes on their separate machines, then start the webserver on each machine, with the application properties modified or overridden to point to that node's RPC port.
Since the nodes are on separate machines, it's even possible to use the same RPC port for all nodes, since the IP address will differ.
We have implemented AppDynamics in Jboss application. We have load balancer and autoscalling which means we will have node registration when new server comes up.
The problem here is Java and Machine Agent. Java Agent can reuse name with prefix (Appd Controlled Node Names) , but machine agent node name need to be provided at configuration level.
We are getting two separate agents listed. One is 100% with Machine Agent and another with Java agent. We need Machine Agent will ping at same line.
https://i.stack.imgur.com/MhpeU.png
The Issue is resolved.
The controller-info of Machine Agent need not to have any Application,Node and Tier name. It should include unique host id which should be same as controller-info of JavaAgent.
Our production AOS server is configured to point to a remote SQL Server instance (per Server Configuration). there is also a local instance of SQL installed that may have been used at one point many moons ago, but definitely not anymore.
Every time we stop the local SQL instance, it also stops the AOS service, which affects production. If I go to services, and look at the properties of the AOS service, the Dependencies tab clearly shows that the service depends on the SQL instance.
We are trying to clean up unused instances of SQL, but I cannot find out where this dependency has been defined, thus can't stop it because it stops the AOS service too. Any idea?
Use sc.exe to configure service.
Example:
sc.exe config "AOS$01" depend= ""
PS: in PowerShell use / (forward slash) instead of empty string.