Table of Contents

Search

  1. Preface
  2. Introduction to RulePoint
  3. Managing Your Account
  4. Using RulePoint User Interface
  5. User Management
  6. Topology Management
  7. Managing Hosts and Nodes
  8. Managing Application Services
  9. Managing System Services
  10. High Availability
  11. Managing Deployment
  12. Dashboard
  13. Object Import and Export
  14. Markers
  15. Log Management
  16. Licenses
  17. Error Codes
  18. Glossary

Administrator Guide

Administrator Guide

Deployment Considerations and Best Practices

Deployment Considerations and Best Practices

When you plan to deploy objects from the design time to the run-time environment, consider the following best practices:
  • You can distribute execute permissions for deployment and related functions across multiple users.
  • You can deploy a primary object only when it is valid. A primary object is valid in the design time when all its supporting objects are valid and resolved.
  • When you delete a project, you must undeploy all primary and supporting objects from the run time.
  • When you change a primary object, you can deploy it again only if it is valid.
  • If you update any supporting object, you need to deploy the primary object again.
  • When you undeploy a primary object, all supporting objects that are referred to in the deployed primary object is also undeployed.
  • Decide how much the application service can handle. If you need to process more events, you need to configure more application services. You must add multiple instances of service controllers and event processors and distribute the load across specific services.

0 COMMENTS

We’d like to hear from you!