This chapter discusses any variations from the instructions specified earlier on installing and uninstalling Configuration Change Console on Windows. All steps for Windows can be followed except for any differences specified here.
The Configuration Change Console Primary Server requires the X-Windows subsystem to be installed for graphics generation on the browser-based interface.
You must install the servers as the root user to ensure that the daemons are configured properly so that the Configuration Change Console server can start when the server starts up. If you install as a non-root user, the installation will work but the server will not be able to start as a daemon.
When running the servers, consider whether your environment blocks the ports you can access for your software based on the user the server will run as. For instance, if your OS is configured to not allow a regular user to run software to use port 80 and 443 and you want these ports to be used for the Configuration Change Console server, then the server must run as root.
In order to generate random numbers that are not predictable, SSL security code relies upon entropy on a machine. Entropy is activity such as mouse movement, disk IO, or network traffic. If entropy is minimal or non-existent, then the random number generator will be slow and security operations may time out. This may disrupt activities such as booting a managed server into a domain using a secure admin channel. This issue generally occurs for a period after startup. Once sufficient entropy has been achieved on a JVM, the random number generator should be satisfied for the lifetime of the installation.
By default, the Configuration Change Console assumes that the server has low entropy, so a setting is enabled to use /dev/urandom as a source of entropy for the Weblogic startup. This weakens the security between the cluster elements in production environments.
If you want to disable /dev/urandom to ensure a more secure environment, edit the following files:
{install_directory}/bea/user_projects/domains/ConfigChangeConsole/adminwrapper.conf
{install_directory}/bea/user_projects/domains/ConfigChangeConsole/wrapper.conf
Comment out the entry in the log file that sets the java.security.egd setting. The following is an example. Note that the number 5 in this line might be different in your installation and should not be changed. The only action required to enable this workaround is to comment out this line:
#wrapper.java.additional.5=-Djava.security.egd=file:///dev/urandom
Turning off this setting will cause the Weblogic server for Configuration Change Console to take a very long time to start. It is also possible that the startup will fail to generate the proper content for SSL communication which will result in the cluster members not being able to communicate with each other.
The alternative to using the java.security.egd setting is to contact your operating system vendor to obtain a patch to ensure that a low entropy server will not block random number generation.
The installer for Linux is named depending on the architecture of the server you are installing on. For instance, server-linux-x86-32bit.bin is used to install on any 32 bit x86 hardware. Ensure that the file server-linux-x86-32bit.part2 is in the same directory as the main installer. It will be required during installation. Both of these files must have the execute bit enabled for the installer to start.
To start installation in Linux, use either of the following:
./server-linux-x86-32bit.bin for graphical installer
./server-linux-x86-32bit.bin -i console for console based installer
The installation of any type of server will result in an init daemon to be configured. The daemon that is created will depend on the name of the server in a similar way as defined for the Windows installation above. You will find the daemon control script under /etc/init.d directory after installation. You can start or stop each server the same way you would with any other daemon process using the following commands:
/etc/init.d/daemonname start
/etc/init.d/daeomonname stop
The value daemonname in this case will start with EMCCC and end with the name of the Configuration Change Console server component, for example EMCCCAdminServer, EMCCCPrimaryServer, EMCCCSecondaryServer1, and so on.If you did not install the server as root, you must start the server manually from the command line. You can do this by opening a shell and changing your directory to the following:
$USER_INSTALL_DIR$/bea/user_projects/domains/ConfigChangeConsole
Run the executable according to the name of the server you installed:
Table 6-1 Server Commands According to Type of Server
| Type | Command |
|---|---|
|
For primary w/o clustering: |
./PrimaryServer -c wrapper.conf |
|
For primary w/clustering: (two services need to be started) |
./PrimaryServer -c wrapper.conf ./AdminServer -c adminwrapper.conf |
|
For Secondary: |
./SecondaryServer1 -c wrapper.conf |
|
For Messaging Broker: |
./MessagingBroker1 -c wrapper.conf |
For the last two, replace the name of the server you gave at installation as the executable in this command.
This section describes how to uninstall the Configuration Change Console Server for the Linux Operating System.
From the command prompt, go to the server uninstaller directory. For example:
cd /root/oracle/ConfigurationChangeConsoleServer/UninstallerData
Run the uninstaller, where ServerName is the name of the Configuration Change Console server component being uninstalled, for example, PrimaryServer, SecondaryServer1, and so on, by typing the following command:
./Uninstall_Oracle_Enterprise_Manager_Configuration_Change_Console_ServerName