//AMIS Technology Blog » configuration

Posts tagged configuration

puppet dashboard overview

Configure FMW servers with Puppet

0

When you have many development servers or cloud servers which runs Oracle software and then you know that configuration management of those servers is very important and must be repeatable. When you configure and install all that software by hand, then you also know that the chance is high that those servers are not exactly the same. This can lead to many configuration issues, tons of documentation pages and days for a new environment is released.

With Puppet of puppetlabs you can automate installations and configuration of all these servers and check the status or read the configuration of the servers. Puppet is open source and it works perfectly with VMware or cloud providers like amazon.  There is also Puppet Enterprise which is free up to 10 nodes.

If you want to learn Puppet you can follow this guide and download the puppet test VirtualBox or VMware image.

On github I made a puppet wls module which can retrieve all the Oracle WebLogic software, domains + weblogic artifacts,  running nodemanager + weblogic servers data and displays these values as facts in the Puppet Dashboard.

Second part of the puppet module are scripts to automatically install the following

More >
Vacatures bij AMIS services

Change the JDeveloper system directory

0

De system directory is where JDeveloper stores the user specific settings, configurations and also (for 11g) the default domain of the embedded weblogic server. It uses the JDEV_USER_HOME environment variable to dettermine the location. If it’s not set is uses a default directory, for 11g on windows XP that’s <user dir>\Application Data\JDeveloper\systemXXX (XXX stands for the exact IDE version, e.g. system11.1.1.3.37.56.60 for 11gPS2, 11.1.1.3.0) and for 10g that’s <JDev install dir>\jdev\system (no version included). Note that the Application Data directory contains a space. And although this doesn’t prevent JDeveloper and the embedded weblogic from proper functioning, it may sometimes leads to an issue, e.g. that diagnostics (adrs) cannot create an image.

To change this directory, just add the JDEV_USER_HOME environment variable and set it to the required directory, that must not contain a space in the name and when you restart JDeveloper it will use that directory. However, you’ll notice that JDeveloper will now consider itself an almost new installation, without your custom configuration and no default weblogic domain but with installed extensions. It should be able to copy More >

Go to Top