Skip to content

SoftwareAG Command Central basic use of Docker containers for infrastructure setup testing

License

Notifications You must be signed in to change notification settings

jayrgauthier/sagdevops-hello-docker

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 

Repository files navigation

Command Central Docker images

Configuration

Login to Docker Store with your Docker ID, open https://store.docker.com/images/softwareag-commandcentral and accept license agreement to get access to Command Central images.

Login to Docker with your Docker ID from your console and verify you can download the images:

docker login
docker pull store/softwareag/commandcentral:10.1.0.1-server

Starting a default Command Central server

Create a Docker network for the components to communicate

docker network create ccnetwork

You can start new Command Central server by running the container:

docker run --name cc -d -p 8091 --network ccnetwork softwareag/commandcentral:10.1.0.1-server

Run docker port cc command to find out its published port

8091/tcp -> 0.0.0.0:32769

This will start an empty Command Central with the HTTPS port exposed. Open published port in the browser, for example https://0.0.0.0:32769/ to see Command Central login page.

Login with default credentials as Administrator/manage.

NOTE it will take up to a minute for the server to start accepting HTTP requests.

Registering an existing Software AG installation

You can connect any 9.x or 10.x Software AG installation that has a running Software AG Platform Manager (SPM).

Simply point to running SPM host:port:

docker exec cc sagcc add landscape nodes alias=mynode1 url=http://IP:8092 -e OK

Succesfull registration will report 200 OK

Command Central Web UI will show this managed node under Installations tab with all discovered managed instances under Instances tab.

Launching a new empty Software AG installation

For development or testing purposes you can launch an empty Software AG managed installation.

Run Command Central node container on the 'ccnetwork' network:

docker run --name n1 -d -P --network ccnetwork softwareag/commandcentral:10.1.0.1-node

By default node container will auto register itself with Command Central using container's internal id.

After a minute or so the managed node status will change to green (ONLINE).

Using docker-compose files for dev and test environments

Run example init service from docker-compose.yml file:

docker-compose run --rm init

The init service will bring up Command Central container and two test managed nodes.

When it's done running open Command Central Web UI

Command Central will show two nodes:

  • one auto-registered with container id as node alias
  • second one registered with as 'test2'

After a minute or so they both will come online.

Install, patch, configure and use Software AG software on these test nodes. Recycle them when no longer needed:

docker-compose stop test1 test2
docker-compose rm test1 test2

Configuring Command Central

You can automatically configure your Command Central with everything you need to perform provisioning, migration and maintenace of your Software AG landscape.

Please see Command Central project Docker secion for details.

Building Docker images using Command Central Builder

You can build custom images with Software AG software using softwareag/commandcentral:10.1.0.1-builder image and Command Central templates.

Please see Command Central Docker builder project.


Contact us at TECHcommunity if you have any questions.


DISCLAIMER These tools are provided as-is and without warranty or support. They do not constitute part of the Software AG product suite. Users are free to use, fork and modify them, subject to the license agreement. While Software AG welcomes contributions, we cannot guarantee to include every contribution in the master project.

About

SoftwareAG Command Central basic use of Docker containers for infrastructure setup testing

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published