. . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Dealing with Multiple Persistence Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 This action assumes standard Java EE bootstrapping. The Java EE server auto-detects persistence units (in effect, META-INF/persistence.xml files in application jars) and persistence-unit-ref entries descriptor (for example, web.xml) and defines environment naming context locations for those persistence units. In such a scenario, the entire persistence unit deployment, including the weaving (byte-code transformation)

This assumes standard Java EE 5 bootstrapping, with the Java EE server autodetecting persistence units (i.e. META-INF/persistence.xml files in application jars) and persistence-unit-ref entries in the deployment descriptor (e.g. web.xml) defining environment naming context locations for those persistence units. In such a scenario, the entire persistence unit deployment, including the weaving (byte-code transformation) JtaTransactionManager). Note that, in case of multiple persistence units used in the same application, the bean names of such a JNDI-retrieved persistence units should match the persistence unit names that the application

This assumes standard Java EE 5 bootstrapping, with the Java EE server autodetecting persistence units (i.e. META-INF/persistence.xml files in application jars) and persistence-unit-ref entries in the deployment descriptor (e.g. web.xml) defining environment naming context locations for those persistence units. In such a scenario, the entire persistence unit deployment, including the weaving (byte-code transformation) JtaTransactionManager). Note that, in case of multiple persistence units used in the same application, the bean names of such a JNDI-retrieved persistence units should match the persistence unit names that the application

resulting RAR file into your application server's deployment directory! NOTE: Such RAR deployment units are usually self-contained; they do not expose components to the 'outside' world, not even to other This assumes standard Java EE 5 bootstrapping, with the Java EE server autodetecting persistence units (i.e. META-INF/persistence.xml files in application jars) and persistence-unit-ref entries in the deployment descriptor (e.g. web.xml) defining environment naming context locations for those persistence units. In such a scenario, the entire persistence unit deployment, including the weaving (byte-code transformation)

resulting RAR file into your application server's deployment directory! NOTE: Such RAR deployment units are usually self-contained; they do not expose components to the 'outside' world, not even to other This assumes standard Java EE 5 bootstrapping, with the Java EE server autodetecting persistence units (i.e. META-INF/persistence.xml files in application jars) and persistence-unit-ref entries in the deployment descriptor (e.g. web.xml) defining environment naming context locations for those persistence units. In such a scenario, the entire persistence unit deployment, including the weaving (byte-code transformation)

resulting RAR file into your application server's deployment directory! NOTE: Such RAR deployment units are usually self-contained; they do not expose components to the 'outside' world, not even to other This assumes standard Java EE 5 bootstrapping, with the Java EE server autodetecting persistence units (i.e. META-INF/persistence.xml files in application jars) and persistence-unit-ref entries in the deployment descriptor (e.g. web.xml) defining environment naming context locations for those persistence units. In such a scenario, the entire persistence unit deployment, including the weaving (byte-code transformation)

resulting RAR file into your application server's deployment directory! NOTE: Such RAR deployment units are usually self-contained; they do not expose components to the 'outside' world, not even to other This assumes standard Java EE 5 bootstrapping, with the Java EE server autodetecting persistence units (i.e. META-INF/persistence.xml files in application jars) and persistence-unit-ref entries in the deployment descriptor (e.g. web.xml) defining environment naming context locations for those persistence units. In such a scenario, the entire persistence unit deployment, including the weaving (byte-code transformation)

resulting RAR file into your application server's deployment directory! NOTE: Such RAR deployment units are usually self-contained; they do not expose components to the 'outside' world, not even to other This assumes standard Java EE 5 bootstrapping, with the Java EE server autodetecting persistence units (i.e. META-INF/persistence.xml files in application jars) and persistence-unit-ref entries in the deployment descriptor (e.g. web.xml) defining environment naming context locations for those persistence units. In such a scenario, the entire persistence unit deployment, including the weaving (byte-code transformation)

resulting RAR file into your application server's deployment directory! NOTE: Such RAR deployment units are usually self-contained; they do not expose components to the 'outside' world, not even to other This assumes standard Java EE 5 bootstrapping, with the Java EE server autodetecting persistence units (i.e. META-INF/persistence.xml files in application jars) and persistence-unit-ref entries in the deployment descriptor (e.g. web.xml) defining environment naming context locations for those persistence units. In such a scenario, the entire persistence unit deployment, including the weaving (byte-code transformation)

specified in any of the following form: 500, PT0.5S and 500ms. You can also use any of the supported units. These are: ns for nanoseconds us for microseconds ms for milliseconds s for seconds m for minutes size threshold of 256 bytes can be specified as 256 or 256B. You can also use any of the supported units. These are: B for bytes KB for kilobytes MB for megabytes GB for gigabytes TB for terabytes The strictly required, but improves the Datadog experience by sending meter descriptions, types, and base units to Datadog. management.metrics.export.datadog.batch-size=10000 # Number of measurements per request