Installation & Upgrade & De Installation
Last updated
Last updated
This paragraph describes the installation.
In the following of this chapter, %DMK_HOME%, %WEBLOGIC_BASE do not exist in the environment and their values must be replaced in the commands listed. After the installation has completed those environment variables will be available.
This paragraph describes all necessary steps which must be completed before you start the DMK installation.
DMK is developed on Windows PowerShell. Therefore PowerShell must be installed previously:
PowerShell installation requires for Windows 2003 Server
.Net framework 2.0 which is available from the Microsoft Download Center.
PowerShell 1.0 which is available from the Microsoft Technology Center.
PowerShell is pre-installed on Windows 2008 Server and must be activated using the following procedure
Click “Start Menu” → Select “Server Manager” → When the Server Manager appears, select on the left the panel “Features” → On the right click “Add Features” → Scroll down and check the checkbox “Windows PowerShell” → Click “Next” → Click “Install” → Finish
Change for all Windows platform the PowerShell execution policy to permit the execution of scripts as follows
\
If you encounter any difficulties due to lack of privileges, try to launch PowerShell as administrator (right click¬ run as administrator) or using Windows PowerShell Modules launch icon.
Parts of the DMK are developed in PERL. Therefore, PERL must be installed previously:
Strawberry PERL 5-24.0.1-64bit is included in the zip file and needs to be installed. The installation steps are described in the next chapter.
Based on the dbi services WebLogic OFA (Oracle Flexible Architecture) best practices extract the archive under %WEBLOGIC_BASE%\local, as explained below:
Typically, on Linux/Unix, %WEBLOGIC_BASE% match:
In the following of this documentation, %DMK_HOME% is %WEBLOGIC_BASE %\local\dmk During the installation phase, those do not exist and their values must be replaced in the commands listed.
Double click on the strawberry-perl-5-24.0.1-64bit package installer and provide the following path to install the software:
This is one of the most important installation step, once extracted the “default” configuration file is available under %DMK_HOME%\etc.
During the installation, the “default” configuration file %DMK_HOME%\etc\dmk.conf.win is renamed to dmk.conf. This mechanism avoids any configuration loss in case of upgrades.
Adapt the following variables:
WEBLOGIC_BASE
Set it as explained in the OFA document. Default value is “D:\app\weblogic”
WEBLOGIC_CNF
Set it to point to the weblogic domains description file. Default value is: “D:\app\weblogic\local\etc\weblogic_domains.conf”
MW_CONFIG_HOME
Set it as explained in the OFA document. Default value is: “E:\app\weblogic\config”
The WEBLOGIC_CNF environment variable declaration does not accept any variable references.
Each WebLogic domain has to be declared in the CONFIG FILE. This file is named “weblogic_domains.conf” and has to be located in the ““%WEBLOGIC_BASE%\local\etc” directory.
To initialize the DMK copy the sample “weblogic_domain.conf” file available in the DMK templates distribution.
Add one row for each existing WebLogic Domain or for each WebLogic Domain created using the Fusion Middleware domain configuration tool. A directory having the WebLogic Domain name as name has to be created for each domain. This directory must contain the specific domain properties file. A WebLogic Domain sample definition file is provided in “%DMK_HOME%\templates\etc\sample_domain” directory.
Copy the PowerShell profile file from the DMK template to the user:
Notes:
has to be replace by the username who will be used to start the DMK. Remember that this user must have the administrator rights on the Windows Server.
If the WindowsPowerShell directory does not exist, create it.
Open a file explorer and list the files in %DMK_HOME%\bin Edit the startDMK.cmd file to make sure the path to the setWLS.cmd; the drive letter might have to be updated depending on the installation choices. Once done Right click on startDMK.cmd and use run as Administrator
Don’t be afraid, the installation is automated without questioning.
dbi services recommend to perform a backup of your DMK package before upgrading. The upgrade process is similar to the installation except that the prerequisites are already fulfilled: Extract the software as explained in paragraph 3.1.2 Software extraction Install DMK as explained in paragraph 3.1.4 Install
That’s it!
Upgrades don’t modify the “%DMK_HOME%\etc\dmk.conf” file, Please review the “%DMK_HOME%\etc\dmk.conf.win” file newly introduced aliases or variables.
This paragraph describes the de-installation of the DMK toolkit.
Open a file explorer and delete all the files in %DMK_HOME% The strawberry PERL directory can be deleted too.
Do not forget to remove the profile from your environment and logout to complete to de-installation.
