Oracle 12c SOA Suite: Administration via Enterprise Manager

After

• Configuring the database via RCU
• Installation of the infrastructure software
• Installation of the SOA Suite software
• Configuring the SOA Suite Weblogic Server

i want to present some screenshots of the web console of the SOA Suite:

http://localhost:7001/em

But first the servers have to be started:

cd /home/oracle/Oracle/Middleware/Oracle_Home/user_projects/domains/base_domain/bin
nohup ./startNodeManager.sh &
nohup ./startWeblogic.sh &

Now the login is available:

 

 But there the soa_server1 is still down:

 So let's start this one:

nohup ./startManagedWebLogic.sh soa_server1 http://192.168.178.49:7001

 

The icon left to "base_domain" (beneath the oracle logo at the top) is the menu:

 

If you navigate to "soa-infra(soa_server1) you get this frame:

Oracle SOA Suite 12c: Tokens - To avoid substituting values: define global token variables

Inside the Enterprise Manager (URL: http://yourhost:7001/em) you can configure SOA Suite profiles:

 

Choose "Token Configurations"

 ???

To list the tokens click on "Modify Configuration file":

 To add a token click on the green plus:

 Do not forget to save your changes:

 

To use the bulk append you have to create a file like this one:

    2000
    weblogic

Choose your file "text.xml":

 and click on "Append":

Java 10 released: java with some enhancements for running inside docker

After the release of Java 9 in october 2017 with its new features

• JShell with its special commands
• the new folder structure 
• and many more

Oracle released Java 10:

 A short summary of the new feature can be found
at https://blogs.oracle.com/java-platform-group/introducing-java-se-10
or you can take a look a the release notes:
http://www.oracle.com/technetwork/java/javase/10-relnote-issues-4108729.html#NewFeature

My favourites are:

• JEP 307 Parallel Full GC for G1  Improves G1 worst-case latencies by making the full GC parallel. The G1 garbage collector is designed to avoid full collections, but when the concurrent collections can't reclaim memory fast enough a fall back full GC will occur. The old implementation of the full GC for G1 used a single threaded mark-sweep-compact algorithm. With JEP 307 the full GC has been parallelized and now use the same amount of parallel worker threads as the young and mixed collections.
  
  See JDK-8172890

and the docker enhancements:

• JDK-8146115 Improve docker container detection and resource configuration usage

The JVM has been modified to be aware that it is running in a Docker container and will extract container specific configuration information instead of querying the operating system. The information being extracted is the number of CPUs and total memory that have been allocated to the container. The total number of CPUs available to the Java process is calculated from any specified cpu sets, cpu shares or cpu quotas. This support is only available on Linux-based platforms. This new support is enabled by default and can be disabled in the command line with the JVM option:

-XX:-UseContainerSupport

In addition, this change adds a JVM option that provides the ability to specify the number of CPUs that the JVM will use:

-XX:ActiveProcessorCount=count

This count overrides any other automatic CPU detection logic in the JVM.

• JDK-8186248 Allow more flexibility in selecting Heap % of available RAM

Three new JVM options have been added to allow Docker container users to gain more fine grained control over the amount of system memory that will be used for the Java Heap:

-XX:InitialRAMPercentage
-XX:MaxRAMPercentage
-XX:MinRAMPercentage

These options replace the deprecated Fraction forms (-XX:InitialRAMFraction, -XX:MaxRAMFraction, and -XX:MinRAMFraction).

• JDK-8179498 attach in Linux should be relative to /proc/pid/root and namespace aware

This bug fix corrects the attach mechanism when trying to attach from a host process to a Java process that is running in a Docker container.

Related posts:

• Docker on Ubuntu 
• Running through a tutorial / investigating the processes
• Creating a small linux for my docker cluster (Alpine Linux) 
• How to build a docker swarm 
• Creating a minimal webserver container and deploying it to docker swarm
• Setting up a tomcat with docker  
• Running a swarm with multiple managers 
• Mysql inside a docker container - persistency with docker volumes 
• How to change the configuration of a standard docker container(e.g. changing tomcats memory settings)

Oracle VM Server x86: Discovering a server/node + setting up a repository, server pool and networking

Let's put the things together:

• after setting up a Oracle VM node
• and configuring Oracle VM Manager

The Oracle VM Manager has to discover the node. Inside the web GUI (https://yourhost:7002/ovm/console)  clickt on the right icon:

Then give your password and the ip(s):

And then you can see the node details (if the connections does not fail):

The next step is to create a repository. To achieve this, you have to add a additional hdd on the oracle VM server/node, without mounting this on the server/node.
Then disover the local storage:

After "rescan phyiscal disks" it is possible to create a repository:

Still something missing: a server pool:

 Attention: Uncheck the "Clustered Server Pool" option:

And last but not least: networking...

Check, that your network is available for "Virtual Machine"

 

 Next posting i will show the creation of a virtual machine...