I need to install two server instances with different applications in each.
Is the recommended approach to create both servers with applications in distribution tree?
Is it possible to pack one server instance and applications and create from it two server instances with different applications each during installation?
With the "Install a service" action you can install two service instances of the same executable. However, you cannot select the executable directly in the "Service" property.
Instead, select [Other service executable] from that drop-down, then fill in the "Executable" and "Name" properties. In the "Name" property of the second "Install a service" action choose a different service name than in the first one.
Related
Have an MSI file with multiple Windows Services. Running the MSI file creates an instance of each service. However, I am unable to install another instance of each service (or one of the contained services).
Have tried a few suggestions online but they seem more suited for EXE files. have tried MSINEWINSTANCE but from my understanding, this requires a .mst file which we don't have or know how to create.
Ideally, create each service with a "_#' at the end (where # is instance of the service.
I have three managed servers running on a Weblogic domain. Now I need to configured node manager so that I can stop and start each of the managed servers.
My question is do I need to define a separate 'Machine' and 'Node Manager port' for each of the managed servers? Or can a single 'Machine' and "Node Manager port' combination be used to start/stop multiple managed servers
Thanks in advance
Yes it is possible but the configuration depends on how your Machines are distributed across your hosts on whether you need to use different ports etc. Oracle provides quite a detailed tutorial on this here. The contents of which is too much to replicate into SO.
I recommend you follow the tutorial and then post any specific questions you may have as a new question.
Step 1: Start weblogic server and open weblogic console in browser and login with correct credential.
Step 2: Expand Environment and click on Machine link
Step 3: Click on New to add new machine and give the machine name. Then click on next.
Step 4: Enter Listen Address (server IP) and port on which node manage will run. And then click Finish.
Please use below link for more detail view
https://fi-sm.com/blog/how-to-add-new-server-on-admin-server-in-web-logic-12c-server/
I want to manage the servers in our staging pipeline with Powershell DSC (push model). The servers map to the environments as following
Development: 1 server
Test: 2 servers
UAT: 2 servers
Production: 2 servers
The server(s) within one environment do have the same configuration. But the configuration is different between the environments. I wanted to go with the push model because I do not have to setup a pull server.
Powershell DSC offers the option to manage the configuration via configuration data in a separate file But this comes with the caveat that you need to specify a node name that matches the respective server name. And that means, I need to copy the configuration data for each server in one environment. And when changing the configuration I need to remember that there is a second place where I need to update the configuration value.
Additionally, I do not really care about the server names. If the servers are exchanged tomorrow for new servers, the configuration should be just applied which is relevant to the environment.
What is the best practice approach to manage multiple servers within one environment with the same configuration?
Check the links, I think they cover scenerio
Using A Single DSC Configuration for Multiple Servers
enter link description here
DSC ConfigurationNames with multiple nodes
enter link description here
The mof file that gets produced does not contain the nodename inside it. So as long as you build a generic configuration, you can rename it after the fact at deploy time.
You can create one config for each environment with some generic name. Then enumerate the list of servers and make a copy of the config for each one with that servers name.
You can take it a step further. Have a share where you create a folder for each server that matches the server's name. Then copy the mof for that server into that folder with a name of localhost.mof. You can then run Start-DSCConfiguration -Path \\server\share\$env:computername from that machine as part of my deployment script.
I am using Orchestrator runbook in which there is a ".net run script" which even runs Powershell script, i have to write a Powershellscript which Query the SCCM 2012 for the SW(given as parameter) and install it on the VM (given as parameter). i have already list of Softwares as an application in the Software Library of SCCM 2012.
If you're using Orchestrator a much simpler solution (more in keeping with Orchestrator) would be to install the "System Center Integration Pack for System Center 2012 Configuration Manager" and use the activities defined there:
http://technet.microsoft.com/en-us/library/hh967537.aspxhttp://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=28725
You can either:
Add the machine to an existing collection that already has deployments active for the software you want installing - Use the "Add Collection Rule" activity to add the machine to the correct collection: http://technet.microsoft.com/en-us/library/hh967533
Create a new collection specifically for the machine and deploy applications to the collection using the "Create Collection" and "Deploy Application" activities: http://technet.microsoft.com/en-us/library/hh967526 and http://technet.microsoft.com/en-us/library/hh967531
In my installer i need a number of launchers, to install them as services, based on the user input. Those Launchers are all the same except for an index in their name.
I dont want to create all those launchers manually because that would be impossible to maintain.
Is there a way to copy and modify launchers at installer runtime and then install them as a service?
There is no reason to duplicate a service launcher at runtime. You can use an "Install service" action to install several services with different service names. To do that select "Other service executable" in the "Service" property of that action, then you can select and executable and a (variable) service name as well as variable arguments.
I have a Usecase too, where i want to have this Possibility of Renaming the Launcher an Runtime.
Assume you want to have a Testinfrastructure, where you want not only to test one Instance of your Programm, but several. And you want to use the Launchers from Install4J to start your Application.
Assume you have 5 Services that need to be started to provide the desired Functionality. Now think of having 10 Instances for 10 Customers, you want to test. Further you want to test it not on 10 different Machines, Docker, VM's, or what ever but on one single Machine.
This isn't possible, since you can't rename the Services at Runtime.
Wolfgang, i understand your Problem. Mine is similar.
I played a bit around with the Launcher.exe.
Perhaps there's a Solution for your Case.
Assuming your desired Launchernames are all off the same Length, like:
- Launcher_01.exe
- Launcher_02.exe
- Launcher_03.exe
- Launcher_04.exe
- Launcher_05.exe
You can then generate a Launcher once, with the Name "Launcher_xy.exe".
It's now possible to open up your favorite Hex-Editor an search for "Launcher_xy", rename it to "Launcher_01" and save the Data back to the exe-File. But be aware of not changing the Length of the Name. It won't work, if you'll change the Length.
So if you've changed the Name and afterwards execute
Launcher_xy.exe -install non-interactive
you will get a new Service called "Launcher_01.exe" under Windows-Services.