There are two application which I am trying to deploy on weblogic with default deployment order (i.e. 100). I want to know which application is deployed first? As per weblogic documentation it will deploy in alphabetical order when the deployment order is same. I want to know what logic it use for alphabetic order. Does it consider only first letter or it checks in-depth. I did few experiment and observed that it rely on first letter only. e.g. I have two wars - abc.war and adc.war. Ideally it should deploy first abc.war then adc.war but it doesn't.
The deployment order can be changed int he deployments tab. You can have the abc.war be set to a higher priority than the adc.war. While deploying, choose the order you would like. As far as I am aware, there is more to it than alphabetical order since I have seen deployments being deployed in non-alphabetical order. By setting the order in the deployments tab, you can control it.
Related
I need to know a way to scale down all the deployments on a kubernetes namespace except for one with a specific string inside the name since it has dependencies. This on an AzureCLI task inside of an azure pipeline. Any ideas?
Something like:
If name contains "randomname" then do not scale up/down the service.
I did try some exceptions but still not working.
You can add a label on the one you want to exclude, and then use queries using labels and selectors to apply operations on the selected set of resources.
My current situation is that I have about 20 different Eclipse product configurations for an RCP-Application, which contain different features. But all configurations share, for example, the same JVM-Args.
The obvious problem here is, that if the JVM-Args change, I have to change them in every single product file.
Now my question: is there a functionality to centralize or generalize identical configurations across multiple product configurations?
What is the recommended way of managing multiple release stages / destinations?
We currently use a combination of stages to release to a staging or production environment for any customer, but this means that we have (customer x 2 environments) = 20 stages right now and the overview page is getting unwieldy fast.
I agree that we should strive to keep as many customers as possible on the same version, but this is not always possible nor wanted.
Is there a better way to manage all these stages?
In your situation,one idea I can think of is trying to use deployment groups to put ten customers' machines into one deployment group, a deployment group is a logical set of deployment target machines that have agents installed on each one. Deployment groups represent the physical environments. So that only two deployment groups are needed for two environments, which should be more convenient.But the trouble with this is that you need to have an agent for each machine.For details on how to operate, you can refer to the document.
You may do it with Multi-configuration. Then the result would be a stage of a customer.
I am on Enterprise Architect 13.5, creating a deployment diagram. I am defining our servers as nodes, and using attributes on them so that I can specify their details, such as Disk Controller = RAID 5 or Disks = 4 x 80 GB.
When dragging instances of these nodes onto a diagram, I can select "Set Run State" on them and set values for all attributes I have defined - just like it is done in the deployment diagram in the EAExample project:
Since our design will have several servers using the same configuration, my plan was to use the "initial value" column in the attribute definition on the node to specify the default configuration so that all instances I create automatically come up with reasonable values, and when the default changes, I would only change the Initial Values on the original node instead of having to go to all instances:
My problem is that even though I define initial values, all instances I create do not show any values when I drag them onto the diagram. Only by setting the Run State on each instance, I can get them to show the values I want:
Is this expected behavior? Btw, I can reproduce the same using classes and instances of them, so this is not merely a deployment diagram issue.
Any ideas are greatly appreciated! I'm also thankful if you can describe a better way to achieve the same result with EA, in case I am doing it wrong.
What you could do is to either write a script to assist with it or even create an add-in to bring in more automation. Scripting is easier to implement but you need to run the script manually (which however can add the values in a batch for newly created diagram objects). Using an add-in could do this on element creation if you hook to EA_OnPostNewElement.
What you need to do is to first get the classifier of the object. Using
Repository.GetElementByID(object.ClassifierID)
will return that. You then can check the attributes of that class and make a list of those with an initial value. Finally you add the run states of the object by assigning object.RunState with a crude string. E.g. for a != 33 it would be
#VAR;Variable=a;Value=33;Op=!=;#ENDVAR;
Just join as many as you need for multiple run states.
I have a real-time workflow for creating unique numbers. This workflow get a numeric field from my custom entity, increase it by 1, and update it for next use.
I want to run this workflow on multiple records.
Running on-demand mode, it works fine,and I have true and unique numbers, but for "Record is Created" mode, it dose not work fine and get repeated numbers.
What I have to do?
This approach wont work, when the workflow runs on demand its running multi-threaded, e.g. two users create two records, two instances of the workflow start. As there is no locking mechanism you end up with duplicated numbers.
I'm guessing this isn't happening when running on demand because you are running as a single user.
You will need to implement a custom auto number approach, such as Auto Number for DynamicsCRM.
Disclaimer: I work for Gap Consulting who produce the tool linked above.