- VMware vRealize Orchestrator Cookbook Second Edition
- VMware vRealize Orchestrator Cookbook Second Edition
- Credits
- About the Author
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Installing and Configuring Orchestrator
- 2. Optimizing Orchestrator Configuration
- Introduction
- Tuning the appliance
- Tuning Java
- Configuring the Kerberos authentication
- Configuring access to the local filesystem
- Configuring the Orchestrator service SSL certificate
- Orchestrator log files
- Redirecting Orchestrator logs to an external server
- Backup and recovery
- Control Center titbits
- 3. Distributed Design
- Introduction
- Building an Orchestrator cluster
- Load-balancing Orchestrator
- Upgrading a cluster
- Managing remote Orchestrators
- Synchronizing Orchestrator elements between Orchestrator servers
- 4. Programming Skills
- Introduction
- Version control
- Changing elements in a workflow
- Importing and exporting Orchestrator elements
- Working with packages
- Workflow auto documentation
- Resuming failed workflows
- Using the workflow debugging function
- Undelete workflows and actions
- Scheduling workflows
- Sync presentation settings
- Locking elements
- 5. Visual Programming
- 6. Advanced Programming
- Introduction
- JavaScript complex variables
- Working with JSON
- JavaScript special statements
- Turning strings into objects
- Working with the API
- Creating actions
- Waiting tasks
- Sending and waiting for custom events
- Using asynchronous workflows
- Scripting with workflow tokens
- Working with user interactions
- 7. Interacting with Orchestrator
- Introduction
- User management
- User preferences
- Using Orchestrator though the vSphere Web Client
- Accessing Orchestrator REST API
- Accessing the Control Center via the REST plugin
- Running Orchestrator workflows using PowerShell
- Using PHP to access the REST API
- 8. Better Workflows and Optimized Working
- 9. Essential Plugins
- 10. Built-in Plugins
- Introduction
- Working with XML
- Working with SQL (JDBC)
- Working with SQL (SQL plugin)
- Working with PowerShell
- Working with SOAP
- Working with Active Directory
- Working with SNMP
- Working with AMQP
- 11. Additional Plugins
- 12. Working with vSphere
- 13. Working with vRealize Automation
- Introduction
- Working with the vRA-integrated Orchestrator
- Automating a vRA instance in Orchestrator
- Configuring an external Orchestrator in vRA
- Adding Orchestrator as an infrastructure endpoint
- Adding an Orchestrator endpoint
- Integrating Orchestrator workflows as XaaS Blueprints
- Managing AD users with vRA
- Using the Event Manager to start workflows
This recipe shows how to increase the Java heap size so that Orchestrator performs better by making better use of the allocated memory resources.
First of all, we need more virtual memory allocated to the VM on which Orchestrator is running.
You also need SSH access to the appliance.
This how-to is for vCO 5.5 and higher, for versions 5.1 and lower please see kb.vmware.com/kb/2007423:
- Log in to the Linux operating system of your Orchestrator.
- Stop the Orchestrator service with
service vco-server stop. - Make a backup of the file with
cp /usr/lib/vco/app-server/bin/setenv.sh /usr/lib/vco/app-server/bin/setenv.sh.bak. - Type
vi /usr/lib/vco/app-server/bin/setenv.sh. - The
vicommand opens up and displays the contents of the file. - Move the cursor to the line that starts with
MEM_OPTS="-Xmx2048m. - Press I and remove
2048. Enter your desired heap size in MB. - Press Esc and then type
:qwto exit and save. If you want to exitviwithout saving, enter:q!instead. - Start the Orchestrator service with
service vco-server start.
If you are increasing the virtual memory assigned to the VM, you will also need to increase the Java heap size, as it doesn't automatically adjust itself.
The Orchestrator service (vco-server) is a Java process that is set by default to a heap size set to 2 GB. Before going ahead and increasing the Java heap size, it's probably a good idea to check how many resources the Java process actually takes.
You need to balance the amount of memory that you give to the Orchestrator Java process with the rest of the memory usage of the system. This is especially important if you are running Orchestrator together with vRealize Automation. You can easily end up with programs competing for memory, which will slow the whole system down. Don't forget that the Linux system needs some memory too.
The new Control Center now contains a collection of Java metrics. To access them, click on Runtime Metrics and then on Generic. These metrics are also stored every five minutes in /var/log/vco/app-server/metrics.log.
In regards to the Java heap size, you can find a lot of answers here.
The most important metrics in regards to the Java Heap are:
|
JVM metric |
Value in |
Explanation |
|
|
Number |
The number of times the Concurrent Mark-Sweep garbage collector has run. |
|
|
Number |
The amount of time the Concurrent Mark-Sweep garbage collector has run. |
|
|
KB |
The current amount of system memory allocated to the JVM. |
|
|
KB |
The amount of allocated heap memory currently in use. |
|
|
KB |
The current amount of system memory allocated to non-heap storage. This memory is used by Java to store loaded classes and other meta-data. |
The recipe Working with the vRA integrated Orchestrator in Chapter 13, Working with vRealize Automation.
-
No Comment