
In this playground we will show you how easy it is to manage your WebLogic domain set-up with Puppet. How you can add and manage WebLogic’s servers.
The playground system contains a pre-installed puppet agent. There is no server available, so to run Puppet, you have to use the puppet apply
command. The playground text will guide you with this.
On the playground system, you will find an WebLogic domain with the name MYDOMAIN
. We have created it using the wls_profile
module. The playground will guide you in your customisations.
Under this text, you see the working area. You can inspect the system and issue any command you like in the terminal. In the editor window, you can see the Puppet production environment. You can edit anything you wish. The documentation tab shows the documentation for the wls_profile
module.
This system will self destruct in about one hour. So please don’t use it to build or create anything you wish to keep!
Add managed server(s) to your domainAfter you have installed your software and created your primary domain, most of the time, you need to have some specific WebLogic servers. You can do this by adding some data to your hiera data. In the editor tab, go to the directory Now uncomment this data:
This data tells Puppet to ensure that the server First Puppet runPuppet runs will read this data and make sure the servers are available with the specified properties. Puppet will detect that the servers is unknown and create it since we will apply Puppet for the first time with this data.
To inspect if the server was created, type the following command. This is the information Puppet provides you about the servers it manages. Because Puppet fetches all available information about all servers, this command can take up a significant amount of time.
Somewhere in the middle of the output, you’ll see:
So Puppet created the server. Second Puppet runOne of the essential features of Puppet is that it is idempotent. Idempotent means it will not apply changes a second time. So if we rerun Puppet, it should see that the servers already exists with the specified properties and do nothing. Let’s verify that and rerun Puppet:
We still see the message at the top that Puppet manages the servers. To check if any new servers were created, type the puppet resource command one more time.
The output is the same as it was after the first run, so Puppet didn’t create any new server. Add cluster(s) to your domainAfter setting up the server, you also migt need a WebLogic cluster. You can do this by adding some data to your hiera data. In the editor tab, go to the directory Now uncomment this data:
This data tells Puppet to ensure that the server First Puppet runPuppet runs will read this data and make sure the cluster is available with the specified properties. Puppet will detect that the cluster is unknown and create it since we will apply Puppet for the first time with this data.
Let’s inspect the Puppet output. Somewhere near the top, you’ll see:
This is the information Puppet provides you about the WebLogic clusters it manages. When you look at the Puppet output, somewhere near the end, you will see this:
So Puppet created the cluster. Second Puppet runOne of the essential features of Puppet is that it is idempotent. Idempotent means it will not apply changes a second time. So if we rerun Puppet, it should see that the cluster already exists with the specified properties and do nothing. Let’s verify that and rerun Puppet:
We have no longer have the creation message, just as we expected. Inspecting the WebLogic clustersJust like with the
Because Puppet fetches all available information about all servers, this command can take up a significant amount of time. Add datasources to your domainAfter you have installed your software and created your primary domain, most of the time, you need to have a WebLogic cluster. You can do this by adding some data to your hiera data. In the editor tab, go to the directory Now uncomment this data:
This data tells Puppet to ensure that the datasource First Puppet runPuppet runs will read this data and make sure the datasource is available with the specified properties. Puppet will detect that the datasource is unknown and create it since we will apply Puppet for the first time with this data.
Let’s inspect the Puppet output. Somewhere near the top, you’ll see:
This is the information Puppet provides you about the datasources it manages. When you look at the Puppet output, somewhere near the end, you will see this:
So Puppet created the datasource. Second Puppet runOne of the essential features of Puppet is that it is idempotent. Idempotent means it will not apply changes a second time. So if we rerun Puppet, it should see that the datasource already exists with the specified properties and do nothing. Let’s verify that and rerun Puppet:
We still see the message at the top that Puppet manages the datasource, but we no longer have the creation message, just as we expected. Inspecting the datasourcesJust like with the
Because Puppet fetches all available information about all servers, this command can take up a significant amount of time. Add JMS resources to your domainAfter you have installed your software and created your primary domain, often, you need to have WebLogic JMS modules, queues and topics. You can do this by adding some data to your hiera data. In the editor tab, go to the directory Now uncomment this data:
This data tells Puppet to ensure that the module First Puppet runPuppet runs will read this data and make sure the WebLogic JMS configuration is available with the specified properties. Puppet will detect that the WebLogic modules, queues and topics are unknown and create them since we will apply Puppet for the first time with this data.
Let’s inspect the Puppet output. Somewhere near the bottom, you’ll see:
So Puppet created the WebLogic JMS module, the queue and the topic. Second Puppet runOne of the essential features of Puppet is that it is idempotent. Idempotent means it will not apply changes a second time. So if we rerun Puppet, it should see that the wls_jms already exists with the specified properties and do nothing. Let’s verify that and rerun Puppet:
We still see the message at the top that Puppet manages the WebLogic JMS co nfiguration, but we no longer have the creation message, just as we expected. Inspecting the WebLogic JMS configurationJust like with the
Because Puppet fetches all available information about all servers, this command can take up a significant amount of time. Add WebLogic users and groups to your domainMost of the time, you need to setup groups and users in your domain. You can do this by adding some data to your hiera data. In the editor tab, go to the directory Now uncomment this data:
This data tells Puppet to ensure that the groups First Puppet runPuppet runs will read this data and make sure the groups and users are available with the specified properties. Puppet will detect that the groups and users are unknown and create it since we will apply Puppet for the first time with this data.
Let’s inspect the Puppet output. Somewhere near the top, you’ll see:
This is the information Puppet provides you about the groups and users it manages. When you look at the Puppet output, somewhere near the end, you will see this:
So Puppet created the groups and users. Second Puppet runOne of the essential features of Puppet is that it is idempotent. Idempotent means it will not apply changes a second time. So if we rerun Puppet, it should see that the groups and users already exist with the specified properties and do nothing. Let’s verify that and rerun Puppet:
We still see the message at the top that Puppet manages the groups and users, but we no longer have the creation message, just as we expected. Inspecting the WebLogic users and groupsJust like with the
Because Puppet fetches all available information about all servers, this command can take up a significant amount of time. You like it?Do you like what you see here and want to test this on your own infrastructure? No problem. You can sign up for a free trial. If you have any questions, don’t hesitate to contact us. |
![]() ![]() |