Mass deployment of PIP through e.g. group policy? - ocean

Are there any recommendations on how to facilitate mass deployment of Petrel PIP files (plugin packages) using e.g. group policy?
The package content (plugin files) is easy enough, but the user-specific PluginManagerSettings.xml file needs to be handled carefully. The concept doesn't sit very well with clients who expect to be able to customize and repackage MSI files for this purpose.
It would be prudent of Schlumberger to provide some documentation and suggested best practices in this area. If the documentation exists, I apologize, and would appreciate a pointer.

In the Ocean 2012 (in beta test right now) the new PluginManager.exe has the possibility to install uninstall enable and disable plug-ins from pip file via a command line.
Several of these commands may be added to an msi file. This is explained in the 2012 version of the white paper "Plug-in Identity and Deployment" in the Ocean chm help.

Related

How do you programatically find out where NuGet.exe is installled on a given machine?

Assuming that I have a script that will be run on a clean build server with Nuget.exe installed on it, what is the best way to programatically determine the path for where NuGet.exe is installed?
Is there a way to infer its location by going through NuGet.targets, or reading some sort of external config file, or following some sort of convention?
Note: The closest question I've seen so far is this one that points to where NuGet can be downloaded, but I'm not interested in downloading NuGet manually. I need a way to determine where it is installed, but I'm not sure if there's a convention that I can follow to determine where it might be installed.
In general, nuget.exe is not shipped with any product. Most people need to manually download it.
The only exception is for people who install Mono. Mono ships nuget.exe, but that's generally limited to people developing on Linux or Mac. But people who use .NET Core exclusively don't need Mono, even on Linux/Mac, so they won't have it either.
Few developers on Windows install Mono, so chances are you don't have a nuget.exe on your system unless you downloaded it yourself, or someone checked it into a repo that you cloned.

Patching a MuleSoft application

We have MuleSoft applications and they are deployed in Mule Runtime. We need recommendations on patching MuleSoft applications. The patch can be either in MuleSoft Runtime itself or can be in application.
MuleSoft's recommendation on patching a MuleRuntime is available at https://support.mulesoft.com/s/article/How-to-apply-patches-to-Mule-4-x.
Here, the recommendation to patch MuleRunTime is to replace the jars/plug-in. But with this, how can we maintain/know the version of patch that is applied.
What is the recommended way to patch a application which is deployed in MuleRunTime.
Any help/recommendation on this is appreciated. Thanks.
You can look at infrastructure automation tools that auto install your runtime with the correct patches etc like puppet, chef and so many other tools. So that your runtime is always using the correct doenedencies and is repeatable. Which tool depends on your organisation.
Or just as with your code you can version control your runtime or install scripts in git etc.
The Mule runtime will log its own version and the versions of each plugin and applied patch, whenever it starts your app. So check the log from the last time you started and you'll see the current version and patch level.
So trust the recommendations in the help document you cited in the OP. As Ryan says, you can use any dev-ops tools favored in your organization. (If you don't have a favorite, Maven is integrated very nicely with Anypoint Studio and can help with this.)

Can I internalize VSCode Extentions for my company

Sadly we dont have direct access to the internet in my company. We can handle automatically downloading and packaging VSCode itself using our internal chocolatey but but providing extentions is still a big problem. Partly because they install into the user directory.
Is there a way I can either:
a) Internalize vscode extentions, like a setting that points to an internal nuget server (much like the full visual studio gallery)
b) Place extentions on a pc in some system level location. Eg C:\ProgramData\VSCode\Extentions and then we can install extentions for all users on a given computer using chocolatey.
Private extension galleries are not supported as of VSCode 1.13 but we are tracking the feature request here: https://github.com/Microsoft/vscode/issues/21839
You can manually install and share extensions as vsix files though. See https://code.visualstudio.com/docs/editor/extension-gallery#_common-questions for details

Need help to select correct install file and options for BA\PDI

We want to upgrade our Pentaho suite from 4.1 to 5.0 version. Currently we use Analyzer for ad hoc reporting (which is installed on linux box) and Kettle (which is on windows).Plus this time we want to install repository also so that our kettle jobs are shared centrally.
With this requirement I believe I need to install both BA and DI components, since Analyzer comes under BA. But I can see that BA and DI have separate repository.
Can someone help me explaining which install files I should run and what options should I pick ?. I have 3 files pdi-ee-5.0.2-dist.zip, pdi-ee-client-5.0.1-dist.zip and pdi-ee-server-5.0.2-dist.zip
I would also appreciate if someone can provide me with correct link or video to help me with the install\configuration.Right now I am referring to http://infocenter.pentaho.com/help/index.jsp
You don't have to install anything, you just have to unzip the files and have to run appropriate batch file on windows and .sh file in linux.
For pentaho Data integration you have to run "spoon.bat" on windows and "spoon.sh" on linux
For pentaho BA Server you have to run you have to reach down to biserver-ce foler (i am using community addition) for you it may be like biserver-ee and under that you have to run "start-pentaho.bat" in windows and "start-pentaho.sh" in linux.
you can refer this link..

automate setup of IBM RAD and Websphere

In a project we a forced to use IBM RAD and Webspher Application Server (6.1).
Setting up the development environment is currently described in about 10 pages of wiki documentation and takes about a day if you don't do any mistake. The main parts are:
Installing the IBM Installer;
Use it to install RAD
Install a patch to the Installer;
use it to install half a dozen patches to RAD
create a network drive pointing to ...
checkout project source to ...
install WAS
configure the a WAS instance with two jdbc drivers, 6 datasources, a queue ...
I think you get the idea
I'd like to automate that process (or at lest 95% of it) to something like.
start script x.
On prompt enter a directory with at least yGB of memory available.
Get yourself a cup of coffee
start working.
What are the proper tools to get this working? Should I use something like puppet and chef? Or is that overkill and I can just zip the installation directory and change 2 registry entries?
Has anybody experience with this? Any pointers to get started?
You can script the configuration of WAS using wsadmin:
http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=%2Fcom.ibm.websphere.base.doc%2Finfo%2Faes%2Fae%2Fwelc6topscripting.html
It is some effort to learn how to do so but in the end it saves a lot of time. You need to use Jython or Jacl to do so.
WAS profiles can be created headless with a response file. Use manageprofiles.bat in bin directory of WAS to do so.
Regarding RAD installation you can install the IBM Installation Manager version you need to install the patches right away and then install everything in one shot. Add the fixes you need as Repositiories right from the beginning. The fixes will be installed instead of the old versions in this case. You should have the base images and all fixes on the local disk to do so.
The installation of RAD itself can also run in headless mode but I don't have any experience in doing this.
The configuration of the RAD workspace is the next thing you want to automate. This is not so simple to do. The simplest thing you can do is to export the workspace preferences of a workspace that contains all settings to an eclipse preference file (.epf). File -> Export
This is not a complete solution but may help you a bit. Be sure to keep all settings in just one file and import that into a fresh workspace.
Use Notepad++ TextFX plugin to sort the settings in the epf file. You can then figure out which settings you need just by looking at them.
More control over the workspace settings and automated conifiguration requires accessing eclipse internal APIs and some coding.
Regarding the the project sources it depends on the SCM you are using.