arungahlot / cibmwebsphereappserver Goto Github PK

#cIBMWebSphereAppServer

PowerShell CmdLets and Class-Based DSC resources to manage IBM WebSphere Application Server (WAS) on Windows Environments.

To get started using this module just type the command below and the module will be downloaded from PowerShell Gallery

PS> Install-Module -Name cIBMWebSphereAppServer

• cIBMWebSphereAppServer installs IBM WebSphere Application Server on target machine.
• cIBMWebSphereAppServerFixpack applies a Websphere Fixpack on the target machine
• cIBMWebSphereAppServerProfile creates a WebSphere profile.
• cIBMWebSphereJVMSettings manages the JVM settings of a WebSphere server.

• Ensure: (Required) Ensures that WAS is Present or Absent on the machine.
• Version: (Key) The version of WAS to install
• WASEdition: (Key) The edition of WAS to install. Options: BASE, ND, EXPRESS, DEVELOPER, LIBERTY
• InstallationDirectory: Installation path. Default: C:\IBM\WebSphere\AppServer.
• PlusJava7: Boolean Determines whether or not the IBM Java 7 SDK gets installed
• IMSharedLocation: Location of the IBM Installation Manager cache. Default: C:\IBM\IMShared
• InstallMediaConfig: (Optional) Path to the clixml export of the IBMProductMedia object that contains media configuration.
• ResponseFileTemplate: (Optional) Path to the response file template to use for the installation.
• SourcePath: UNC or local file path to the directory where the IBM installation media resides.
• SourcePathCredential: (Optional) Credential to be used to map sourcepath if a remote share is being specified.

Note InstallMediaConfig and ResponseFileTemplate are useful parameters when there's no built-in support for the WAS edition you need to install or when you have special requirements based on how your media is setup or maybe you have unique response file template needs. If you create your own Response File template it is expected that the template has the variables: sharedLocation and wasInstallLocation. See sample response file template before when planning to roll out your own.

• Ensure: (Required) Ensures that WAS fixpack is Present or Absent on the machine.
• Version: (Key) The version of WAS fixpack to install
• WASEdition: (Key) The edition of WAS. Options: BASE, ND, EXPRESS, DEVELOPER, LIBERTY
• WebSphereInstallationDirectory: Directory where AppServer is installed. Default: C:\IBM\WebSphere\AppServer.
• SourcePath: array UNC or local file path to the fixpack zip-files. Supports multiple file paths.
• SourcePathCredential: (Optional) Credential to be used to map sourcepath if a remote share is being specified.

• Ensure: (Required) Ensures that WAS profile is Present or Absent on the machine.
• ProfileName: (Key) The name of the profile
• ProfilePath: (Optional) Location of profile. If not specified it'll be added to the AppServer\profiles directory.
• NodeName: (Required) Name of the WebSphere Node for the server
• CellName: (Optional) Should only be used for Dmgr.
• HostName: FQDN of the host in the target machine.
• TemplatePath: (Optional) full path to the template to be used for creating this profile
• AdminCredential: (Optional) Credential to be used to create the profiles (if applicable)
• EnableSecurity: Determines whether or not the profile should have security enable. Default is true
• ServerName: The name of the application server if the profile type is not Management or Dmgr
• ProfileType: The type of profile (maps to profiles withing the profileTemplates directory)
• DmgrHost: If not management profile, the hostname of the Dmgr
• DmgrPort: If not management profile, the SOAP port of the Dmgr. Default: 8879

• Ensure: (Required) Ensures that WAS profile is Present or Absent on the machine.
• ProfileName: (Required) The name of the profile
• NodeName: (Required) The name of the WebSphere Node that the server belongs to
• CellName: (Required) The name of the WebSphere Cell that the server belongs to
• ServerName: (Key) The name of the application server
• MinHeapSize: The minimum JVM heap size in MB. Default 1024MB
• MaxHeapSize: The maximum JVM heap size in MB. Default 2048MB
• VerboseGC: Enable verbose garbage collection (useful to help monitor memory usage)
• WebSphereAdministratorCredential: (Required) Credential to be used to apply changes

• cIBMInstallationManager DSC Resource/CmdLets for IBM Installation Manager
• 7-Zip needs to be installed on the target machine. You can add 7-Zip to your DSC configuration by using the Package DSC Resource or by leveraging the x7Zip DSC Module

• New DSC Resource for managing JVM settings cIBMWebSphereJVMSettings
• Fixes various bugs in profile managment and property-based config cmdlets

• Minor fixes
• New CmdLets: Start-WebSphereServer, Stop-WebSphereServer, Stop-AllWebSphereServers, Start-WebSphereNodeAgent, Stop-WebSphereNodeAgent, Test-WebSphereServerService, Test-WebSphereServerServiceExists

• IBM Java 7 installation support via new DSC property PlusJava7

• New DSC Resource for creating WebSphere profiles (including Dmgr support) cIBMWebSphereAppServerProfile
• New CmdLets: New-IBMWebSphereProfile, Invoke-ManageProfiles, Start-WebSphereDmgr, Stop-WebSphereDmgr

• New DSC Resource for installing fixpacks cIBMWebSphereAppServerFixpack
• Adds wsadmin cmdlets (includes IBM's wsadminlib.py which can be added as a module dependency to wsadmin jython scripts)
• Adds Property-Based Config cmdlets
• Depends on cIBMInstallationManager v1.0.4 or above
• New CmdLets: Install-IBMWebSphereAppServerFixpack, Invoke-WsAdmin, Set-WsAdminTempDir, Get-WsAdminTempDir, Import-IBMWebSpherePropertyBasedConfig, Export-IBMWebSpherePropertyBasedConfig, Test-IBMWebSpherePropertyBasedConfig, Get-IBMWebSpherePropertyBasedConfig

• Adds topology cmdlets and cmdlet to create windows services for WAS servers

• Initial release with the following resources
  • cIBMWebSphereAppServer

The table below outlines the tests that various WAS editions/versions have been verify to date. As more configurations are tested there should be a corresponding entry for Media Configs and Response File Templates. Could use help on this, pull requests welcome :-)

The installation depents on media files that have already been downloaded. In order to get the media files please check your IBM Passport Advantage site.

The table below shows the currently supported (i.e. tested) media files.

This configuration will install 7-Zip using the DSC Package Resource, install/update IBM Installation Manager and finally install IBM WebSphere Application Server Network Deployment edition

Note: This requires the following DSC modules:

• xPsDesiredStateConfiguration
• cIBMInstallationManager

Configuration WASND
{
    Import-DscResource -ModuleName 'PSDesiredStateConfiguration'
    Import-DSCResource -ModuleName 'cIBMInstallationManager'
    Import-DSCResource -ModuleName 'cIBMWebSphereAppServer'
    Package SevenZip {
        Ensure = 'Present'
        Name = '7-Zip 9.20 (x64 edition)'
        ProductId = '23170F69-40C1-2702-0920-000001000000'
        Path = 'C:\Media\7z920-x64.msi'
    }
    cIBMInstallationManager IIMInstall
    {
        Ensure = 'Present'
        InstallationDirectory = 'C:\IBM\IIM'
        Version = '1.8.3'
        SourcePath = 'C:\Media\agent.installer.win32.win32.x86_1.8.3000.20150606_0047.zip'
        DependsOn= '[Package]SevenZip'
    }
    cIBMWebSphereAppServer WASNDInstall
    {
        Ensure = 'Present'
        WASEdition = 'ND'
        InstallationDirectory = 'C:\IBM\WebSphere\AppServer'
        Version = '8.5.5'
        SourcePath = 'C:\Media\WASND855\'
        DependsOn= '[cIBMInstallationManager]IIMInstall'
    }
    cIBMWebSphereAppServerFixpack WASFixpackInstall
    {
        Ensure = 'Present'
        WASEdition = 'ND'
        WebSphereInstallationDirectory = 'C:\IBM\WebSphere\AppServer'
        Version = '8.5.5.6'
        SourcePath = @('C:\Media\WAS855_FP\8.5.5-WS-WAS-FP0000006-part1.zip', 'C:\Media\WAS855_FP\8.5.5-WS-WAS-FP0000006-part2.zip')
        DependsOn= '[cIBMWebSphereAppServer]WASNDInstall'
    }
}
WASND
Start-DscConfiguration -Wait -Force -Verbose WASND