Command Central 9.6: New and Enhanced Functionality

Command Central 9.
6
New and Enhanced Functionality
Overview
Sergei Pogrebnyak
Director, Research and Development
©2013 Software AG. All rights reserved.

Command Central 9.0
Template-based Provisioning
Product Fix Central Solution

Installation Management Configuration Management
Landscape Management
Command
Web UI Service API Mobile UI
Line
2 | ©2013 Software AG. All rights reserved. For internal use only
Command Central 9.5
• Define templates
• Product, Fixes, Config, Assets
Product Fix Central
• Manage substitution variables Solution
Installation Management Configuration
• Apply templates to targets Management
Command
Line
Command Central 9.6
•  Web UI for:
•  More IS configuration
Product Fix Central Solution
•  Product/Fix Repositories
Installation Management Configuration Management
•  Templates Create & Apply
•  License Management
•  Log Access
Command
Line
What’s new in Command Central 9.6
•  Centralized repository management, including Web UI

•  Save and apply templates from Web UI
•  More IS configurations support including Web UI
•  IS instance management CLI/API
•  Web UI for license reports management
•  Log access from Web UI and CLI/API
•  HTTPS support and other security related enhancements
•  Online HELP combining Web UI, CLI and REST API topics
•  Cloud Factory CLI/API (preview)
•  SPM footprint optimization
Centralized Repository
Management
6©2013
| Software
©2013AG.
Software
All rights
AG.reserved.
All rights For
reserved.
internal
For
use
internal
only use only
Centralized Repository Management
•  Central repositories are used by template-based provisioning

•  Allows to configure access to SAG SDC and Empower in one central
place
•  Supports product and fix repository types
•  Product repos support multiple releases and locations
•  Adds ability to manage and transfer Installer and Update Manager
images to the target nodes
•  Provides Web UI and CLI/API
Centralized Repository Management Web UI
Centralized Repository Management CLI Basics
•  cc list repository products
•  cc add repository products name=<repoName> location=<remote-repo-

url-or-image-file>
•  cc add repository products name=<name-for-this-repo> --input

<local-image-file> description=<description>
•  cc update repository products <repoName> [[location=<installer-

image-file-or-remote-repository-uri>]
[description=<description>]]]
•  cc update repository products -i <config-with-credentials.xml>
•  cc delete repository products <repoName>
Centralized Repository Management Demo
Watch video recording on the TechCommunity web site under

Communities > webMethods > Products > Command Central > Demos
Command Central Demo: Command Central Repository Management
©2013
11 | Software
©2013AG.
Software
All rights
AG.reserved.
All rights For
reserved.
internal
For
use
internal
only use only
•  Cloning/copying of servers
•  Creation of new (project) environments from standard template
•  Composing more complex environment from a set of product-specific
templates
•  Creation of a repro-environment to troubleshoot production issues
•  Fix and configuration promotion from staging to production
•  Elastic scaling (cloud-bursting)
TEMPLATE
PRODUCTS FIXES CONFIG Future:

Information Information Information
about which about which about all INSTANCES
products and fixes are (supported)
versions are installed product
installed configuration ASSETS
Template may contain a subset: 1, 2 or all 3 categories
Template-based Provisioning – 9.5
•  Save template <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<templateMetadata>
•  Products <alias>templateAlias</alias>
•  Fixes <nodeAlias>nodeAlias</nodeAlias>
•  Configuration <overwriteTemplate>true</overwriteTemplate>
<productOption>
•  Apply template <repositoryId>productRepositoryId</repositoryId>
•  Products <type>PRODUCTS</type>
<useLatestVersion>false</useLatestVersion>
•  Fixes </productOption>
•  Configuration <fixesOption>
<repositoryId>fixRepositoryId</repositoryId>
•  No UI, only CLI <useLatestVersion>true</useLatestVersion>
<type>FIXES</type>
</fixesOption>
<configurationOption>
<type>CONFIGURATION</type>
</configurationOption>
</templateMetadata>
Template-based Provisioning – new in 9.6
•  Web UI to create and apply templates

•  Relies on centrally configured repositories
•  Supports automatic image transfer from the central repository to the
target node
•  New simplified CLI/API
Template-based Provisioning Demo

Command Central Demo: Command Central Template-based provisioning
Save Installation as Template
Template extracted
SPM IS
from source…
Command
Central
SPM
…and stored
T1
on CC
cc create templates alias=t1 nodeAlias=n1 …
Apply Template
SPM IS
Command
Template sent
Central
to target
SPM IS
T1
cc exec templates apply alias=t1 nodeAlias=n2 …
Installing Products Software
Download
Center
1)  Master Repo = Software AG SDC

2)  Image Repo = Installer images
1
Command
Central
2 SPM IS
T1 I1
cc exec templates apply alias=t1 nodeAlias=n2

options=PRODUCTS productsRepo=pr1
Installing Fixes Empower
1)  Master Repo = Software AG Empower

2)  Image Repo = SUM images
1
Command
Central
2 SPM IS
T1 FR1

options=FIXES fixesRepo=fr1
Applying Configuration
1)  Merge or Replace mode

2)  With or without referenced files
Command
Central
SPM IS
T1 F1

options=CONFIGURATION options=FILES
Apply Template Sequence for Integration Server
0. Create
template
Products Fixes Configuration Files
1. Install
products
and start
Products Fixes Configuration Files
IS
2. Install
fixes and Products Fixes Configuration Files
start IS
3. Apply
config and
files and Products Fixes Configuration Files
restart IS
Template Management CLI
# list available templates
cc list templates
Alias Node Alias Description Principal Created
templateAlias local test Administrator Thu Feb 27 17:34:35 PST 2014
# export template (save as local .zip file)

cc get templates export templateAlias --output templateAlias.zip
# import template from a local .zip file

cc exec templates import --input templateAlias.zip
# delete template
cc delete templates templateAlias
Integration Server Configuration
©2013
29 | Software
©2013AG.
Software
All rights
AG.reserved.
All rights For
reserved.
internal
For
use
internal
only use only
Integration Server Configuration
9.0 9.6
•  Ports •  Resources
•  License keys •  Loggers
•  webMethods Messaging
9.5
•  Global variables
•  JDBC pools* •  ALL configurations Web UI
•  JDBC functional aliases*
•  Keystores*
•  Truststores*
•  JNDI aliases*
•  JMS aliases*
•  SMTP settings*
* Supported only for templates,
•  Extended server settings* comparison, CLI and API
IS Configuration UIs
IS Configuration UIs
Basic Configuration CLI Commands
$ cc list configuration types nodeAlias=devis1

runtimeComponentId=integrationServer-default
ID Display Name Category
COMMON-SYSPROPS System Properties Properties
COMMON-PORTS Port Settings Ports
COMMON-JNDI JNDI Settings JNDI
..
$ cc list configuration instances nodesAlias=devis1 runtimeComponentId=

integrationServer-default
ID Config Type Id Display Name
COMMON-SYSPROPS COMMON-SYSPROPS Extended Settings
COMMON-PORTS-p7777 COMMON-PORTS HTTPListener@7777
..
Example – editing IS Extended Settings
$ cc list configuration instances nodeAlias=devis1

runtimeComponentId=integrationServer-default configurationTypeId=COMMON-
SYSPROPS
COMMON-SYSPROPS COMMON-SYSPROPS Extended Properties
$ cc get configuration data devis1 integrationServer-default COMMON-SYSPROPS -

o ext-settings.properties
$ vi ext-settings.properties
...
watt.new.property=someValue
$ cc put configuration data devis1 integrationServer-default COMMON-SYSPROPS -

i ext-settings.properties
CURRENT
Example – create and delete JNDI aliases
$ cc list configuration instances nodeAlias=devis1

runtimeComponentId=integrationServer-default configurationTypeId=COMMON-JNDI
COMMON-JNDI-DEFAULT_IS_JNDI_PROVIDER COMMON-JNDI DEFAULT_IS_JNDI_PROVIDER
COMMON-JNDI-EventBusJndiProvider COMMON-JNDI EventBusJndiProvider
$ cc get configuration data devis1 integrationServer-default COMMON-JNDI-

DEFAULT-IS_JNDI_PROVIDER --output jndi.xml
$ vi jndi.xml
<JNDISettings><JNDI alias=“newJndiAlias”> .. </JNDISettings>
$ cc create configuration data devis1 integrationServer-default COMMON-JNDI --

input jndi.xml
$ cc delete configuration data devis1 integrationServer-default COMMON-JNDI-

newJndiAlias
Integration Server Instance
Management
©2013
36 | Software
©2013AG.
Software
All rights
AG.reserved.
All rights For
reserved.
internal
For
use
internal
only use only
Integration Sever Instance Management
•  Integration Server 9.6 supports multiple instances

•  Default instance can be created by the installer
•  Additional instances can be created using IS CLI locally or CC CLI
remotely
•  No CC Web UI yet
•  No CC Templates support yet
•  Integration Server license cannot be supplied during instance creation.
The license file has to be added afterwards using Web UI or CLI
Instance Management CLI
Create new IS instance

$ cc create instances devis1 integrationServer instance.name=i1 primary.port=7777 …
ID Status Started
5 RUNNING Tue Sep 17 15:02:26 BST 2013
Wait for completion

$ cc get jobmanager landscapejobs devis1 5 --expected-values DONE --wait 30
ID Status Started Ended
5 DONE Tue Sep 17 15:02:26 BST 2013 Tue Sep 17 15:02:40 BST 2013
Update IS instance
$ cc update instances devis1 integrationServer-i1 i1 packages.list=pkg1,pkg2
ID Status Started
Delete IS instance
$ cc delete instances devis1 integrationSever-i1
ID Status Started
Log Access
©2013
39 | Software
©2013AG.
Software
All rights
AG.reserved.
All rights For
reserved.
internal
For
use
internal
only use only
Log Access
•  Allows online access to product log files

•  Tail or head log file viewing, limited number of lines
•  Simple and regexp search
•  Full log download in plain text and zip formats
•  Download of multiple logs for a given component or entire managed
node
•  Supported for Integration Server, SPM, CCE, CTP
•  Web UI and CLI
Log Sources Web UI
Log Viewer Web UI
Log Access CLI
Getting list of log file alises

$ cc list diagnostics logs devis1 integrationServer-default
Alias Size Last Updated
server.log 12345 Tue Sep 17 15:02:26 BST 2013
Getting log tail and head

$ cc get diagnostics logs devis1 integrationServer-default server.log tail
$ cc get diagnostics logs devis1 integrationServer-default server.log head lines=100
Search logs
$ cc get diagnostics logs devis1 integrationServer-default server.log full search=ISS.
0014.0002C
$ cc get diagnostics logs devis1 integrationServer-default server.log tail regexp=“^20.*”
Download logs: one, some, all

$ cc get diagnostics logs devis1 integrationSever-default server.log full –o server.log
$ cc get diagnostics logs devis1 integrationSever-default server.log+stats.log export –o
logs.zip
$ cc get diagnostics logs devis1 integrationSever-default export –o is-logs.zip
$ cc get diagnostics logs devis1 export –o node-logs.zip
HTTPS and other Security
Enhancements
©2013
44 | Software
©2013AG.
Software
All rights
AG.reserved.
All rights For
reserved.
internal
For
use
internal
only use only
HTTPS Support
•  Out of the box enablement of HTTPS communication between

•  Client browser and Command Central server
•  CLI tool and Command Central server
•  CCE and 9.6 SPM’s
•  SPM and managed Integration Server (needs HTTPS port on IS)
•  Pre-generated certificates provide better protection against wire-
sniffing comparing to plain HTTP communication
•  For better protection custom certificates should be generated and
configured for each managed host/SPM
•  HTTPS ports and client configuration is supported via CLI and Web UI
•  Custom certificates have to be distributed manually
•  CC CLI client configuration can be stored in ~/.sag/cc.properties file
protected by the OS using restricted file permissions
•  cc.properties file can also store CC CLI password
Use of Out-Of-The-Box HTTPS Demo

Command Central Demo: Command Central out of the box HTTPS support
Generating certificates
•  Follow the process described in the article on TechCommunity web site

under Communities >>> Command Central Articles
How do I generate keystores and certificates for command central
•  Import certificates into client trust stores

•  cceroot.cer and cce*.cer into cli-truststore.jks
•  cceroot.cer and spm*.cer into cce-truststore.jks
•  Copy *.jks files to server, client and target spm nodes
Updating client configuration to use certificates
•  Update HTTPS port on CCE

•  Update client Browser
•  Update CCE CLI SSL configuration
•  Update HTTPS port on SPM’s
•  Update CCE client SSL configuration
Other usage notes
•  It is recommended to perform HTTPS/SSL channel re-configuration

while you’re connecting to SPM over HTTP!
•  Switch CCE ‘local’ SPM connection to HTTP port if HTTPS is currently used
•  Connect to all remote SPM nodes using HTTP
•  Configure HTTPS port for CCE – verify in Browser
•  Configure HTTPS port for a remote SPM – verify in Browser
•  Configure CCE SSL settings and try to connect to remote SPM using SSL
•  If OK, repeat for others SPM nodes
•  Use can use custom certificates for HTTPS communication with 9.0
and 9.5 nodes as well!
•  9.0 SPM’s have to be restarted from OS level (shell scripts or Windows Svc)
•  9.5 SPM’s have to be restarted from Web UI or CLI
•  9.6 SPM’s restart HTTPS listener automatically!
HTTPS Setup using Custom Certificates Demo

Command Central Demo: Command Central support for HTTPS configuration

using custom certificates
Security Enhancements
•  Out of the box configuration for private user, group and roles internal
user store for CCE and SPM profiles
•  Easy to change default passwords
•  No impact on other products using shared internal stores, e.g. CentraSite
•  Additional default users and groups
•  Support for per-SPM connection credentials

•  No longer all SPM’s must have the same set of credentials
•  Can be configured from CLI and Web UI
License Reports Management
Web UI
©2013
56 | Software
©2013AG.
Software
All rights
AG.reserved.
All rights For
reserved.
internal
For
use
internal
only use only
License Reports Web UI
•  License Reports UI can be accessed via Licenses View menu

•  Allows to create new license reports on demand
•  The generated report can be downloaded as PDF, XML or JSON
•  The reports are archived and the list can be filtered and sorted
•  Previously generated reports can be downloaded at any time
•  Older reports can be deleted
License Reports Web UI
Cloud Factory (preview)
©2013
59 | Software
©2013AG.
Software
All rights
AG.reserved.
All rights For
reserved.
internal
For
use
internal
only use only
Cloud Factory CLI (feature preview)
•  Ability to manage virtual machine instances and images using Cloud

Factory Services API
•  Support for VMware and EC2
•  Account configuration using CLI and Web UI
•  CLI commands for launching new VMs, start/stop and destroying a VM
instances
•  No Web UI yet for image and instance management
Cloud Factory Account Configuration
Cloud Factory Account Configuration
Cloud Factory CLI
Set CFS endpoint URL (NOTE: no /cce at the end)

$ export CC_SERVER=https://localhost:8091
List of available accounts

$ cc list cfs accounts
List of available images

$ cc list cfs images <accountName>
List of available instances

$ cc list cfs instances <accountName>
Launch new instances

$ cc create cfs instances <accountName> <imageId> type=<type>
Start or stop instance

$ cc exec cfs instances <accountName> <instanceId> start
$ cc exec cfs instances <accountName> <instanceId> stop
Delete instance
$ cc delete cfs instances <accountName> <instanceId>
Online Help
©2013
64 | Software
©2013AG.
Software
All rights
AG.reserved.
All rights For
reserved.
internal
For
use
internal
only use only
Online Help
•  New combined online help for Web UI, CLI references an REST API
•  New mobile friendly responsive layout
•  Restful topic links and better search
•  Hosted by Command Central server
•  Accessible from the Help menu
Online Help
Miscellaneous
©2013
67 | Software
©2013AG.
Software
All rights
AG.reserved.
All rights For
reserved.
internal
For
use
internal
only use only
Miscellaneous
•  Optimized SPM footprint

•  Default max memory set to 128 MB
•  Optimized resource settings (e.g. lower thread counts)
•  New optional plugin-in for NERV
•  Out of the box registration of ‘local’ node
•  Tested scalability with 1000 managed nodes

•  CLI is fully functional
•  Web UI is functional but a bit sluggish (expected)

Command Central 9.6: New and Enhanced Functionality

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Command Central 9.6: New and Enhanced Functionality

Enviado por

Direitos autorais:

Formatos disponíveis

Command Central 9.

©2013 Software AG. All rights reserved.

Product Fix Central Solution

• Centralized repository management, including Web UI

• Central repositories are used by template-based provisioning

• cc list repository products

• cc add repository products name=<repoName> location=<remote-repo-

• cc add repository products name=<name-for-this-repo> --input

• cc update repository products <repoName> [[location=<installer-

• cc update repository products -i <config-with-credentials.xml>

• cc delete repository products <repoName>

Watch video recording on the TechCommunity web site under

Command Central Demo: Command Central Repository Management

PRODUCTS FIXES CONFIG Future:

Template may contain a subset: 1, 2 or all 3 categories

• Web UI to create and apply templates

Watch video recording on the TechCommunity web site under

Command Central Demo: Command Central Template-based provisioning

cc create templates alias=t1 nodeAlias=n1 …

cc exec templates apply alias=t1 nodeAlias=n2 …

1) Master Repo = Software AG SDC

cc exec templates apply alias=t1 nodeAlias=n2

1) Master Repo = Software AG Empower

cc exec templates apply alias=t1 nodeAlias=n2

1) Merge or Replace mode

cc exec templates apply alias=t1 nodeAlias=n2

# export template (save as local .zip file)

# import template from a local .zip file

$ cc list configuration types nodeAlias=devis1

$ cc list configuration instances nodesAlias=devis1 runtimeComponentId=

$ cc list configuration instances nodeAlias=devis1

$ cc get configuration data devis1 integrationServer-default COMMON-SYSPROPS -

$ cc put configuration data devis1 integrationServer-default COMMON-SYSPROPS -

$ cc list configuration instances nodeAlias=devis1

$ cc get configuration data devis1 integrationServer-default COMMON-JNDI-

$ cc create configuration data devis1 integrationServer-default COMMON-JNDI --

$ cc delete configuration data devis1 integrationServer-default COMMON-JNDI-

• Integration Server 9.6 supports multiple instances

Create new IS instance

Wait for completion

• Allows online access to product log files

Getting list of log file alises

Getting log tail and head

$ cc get diagnostics logs devis1 integrationServer-default server.log tail regexp=“^20.*”

Download logs: one, some, all

• Out of the box enablement of HTTPS communication between

Watch video recording on the TechCommunity web site under

• Follow the process described in the article on TechCommunity web site

How do I generate keystores and certificates for command central

• Import certificates into client trust stores

• Copy *.jks files to server, client and target spm nodes

• Update HTTPS port on CCE

• It is recommended to perform HTTPS/SSL channel re-configuration

Watch video recording on the TechCommunity web site under

Command Central Demo: Command Central support for HTTPS configuration

• Support for per-SPM connection credentials

• License Reports UI can be accessed via Licenses View menu

• Ability to manage virtual machine instances and images using Cloud

Set CFS endpoint URL (NOTE: no /cce at the end)

List of available accounts

List of available images

List of available instances

Launch new instances

•  Centralized repository management, including Web UI

•  Central repositories are used by template-based provisioning

•  cc list repository products

•  cc add repository products name=<repoName> location=<remote-repo-

•  cc add repository products name=<name-for-this-repo> --input

•  cc update repository products <repoName> [[location=<installer-

•  cc update repository products -i <config-with-credentials.xml>

•  cc delete repository products <repoName>

•  Web UI to create and apply templates

1)  Master Repo = Software AG SDC

1)  Master Repo = Software AG Empower

1)  Merge or Replace mode

•  Integration Server 9.6 supports multiple instances

•  Allows online access to product log files

•  Out of the box enablement of HTTPS communication between

•  Follow the process described in the article on TechCommunity web site

•  Import certificates into client trust stores

•  Copy *.jks files to server, client and target spm nodes

•  Update HTTPS port on CCE

•  It is recommended to perform HTTPS/SSL channel re-configuration

•  Support for per-SPM connection credentials

•  License Reports UI can be accessed via Licenses View menu

•  Ability to manage virtual machine instances and images using Cloud

•  Optimized SPM footprint

•  Out of the box registration of ‘local’ node

•  Tested scalability with 1000 managed nodes