Skip to main content
Home

Search form

Menu

Search form

  • SkyVault 2.0 overview
  • SkyVault 2.0 video tutorials
  • Getting Started guides
  • Using SkyVault
  • Admin QuickStart
  • Starting and stopping SkyVault
  • Admin Console Quick Guide
  • Using the SkyVault Admin Tools
  • Managing transformations
  • Setting up SkyVault authentication and security
  • Setting up clustering
  • Setting up Enterprise to Cloud Sync
  • Creating and managing workflows
  • Backing up and restoring
  • Using the Bulk Import tool
  • Managing content stores
  • Migrating
  • Setting up SkyVault multi-tenancy
  • Setting up replication jobs
  • Monitoring SkyVault
    • JMX monitoring and management extensions
      • Coexistence with other MBeans
      • Activating the Oracle JMX agent and local JMX connectivity
    • Scheduled jobs
  • Auditing SkyVault
  • For Developers
  • Copyright
  • Disclaimer
  • You are here

    SkyVault 2.0 » Administering » Monitoring SkyVault » JMX monitoring and management extensions

    Coexistence with other MBeans

    If there is an MBean server already running on the Java Virtual Machine (JVM) that SkyVault is running on, SkyVault will export its MBeans to that server. Otherwise, SkyVault will start up its own MBean server. This means that, for example, on Tomcat, the SkyVault beans will compliment those provided by the application server and will be navigable in the same context with a suitable JMX client.
    Parent topic: JMX monitoring and management extensions

    © 2017 TBS-LLC. All Rights Reserved.    Follow @twitter