Presentation is loading. Please wait.

Presentation is loading. Please wait.

Aurea and Aurea 2013 Products

Similar presentations


Presentation on theme: "Aurea and Aurea 2013 Products"— Presentation transcript:

1 Aurea and Aurea 2013 Products
Russian User Group Conference October 23, 2013 Thomas Steinborn Aurea Software

2 Aurea Software – Company & Strategy
Agenda Aurea Software – Company & Strategy Aurea 2013 Technology Products Aurea 2013 Insurance Solutions Customer Case Studies

3 Executive team Leela Kaza, SVP Services Todd Brooks, COO
Scott Brighton Chief Executive Officer Dr. Mohammad Ketabchi Chief Product Officer Eric Levine Chief Marketing Officer Hub Vandervoort Chief Technology Officer Leela Kaza, SVP Services Todd Brooks, COO Patrick McClain, CFO Dan Mohan, SVP Value Assurance Curt Richtermeyer, SVP Sales Melissa Garza, VP Human Resources

4 Aurea Core Philosophy The Typical Model The Aurea Model 1 GROWTH 2
PROFIT 3 CUSTOMER SUCCESS The Aurea Model 1 CUSTOMER SUCCESS 2 PROFIT 3 GROWTH

5 Customer Success 100% CUSTOMER SUCCESS Innovation Insights
Premiere Product Solution Support Customer Success Superior Services Relationships Insights Innovation 100% CUSTOMER SUCCESS Every customer assigned two executive sponsors Twice annual meetings to review achievement & establish goals Establish crisp, meaningful success metrics together Every employee bonus tied to success

6 Aurea Technology Products power Solutions
Aurea Insurance Solution Telecom & Media Solution Software Factory Credit Card Ops Visitor Routing Global Support Aurea Technology Products (Actional, DataXtend SI, Savvion, Sonic)

7 Aurea Software – Company & Strategy
Agenda Aurea Software – Company & Strategy Aurea 2013 Technology Products Aurea 2013 Insurance Solutions Customer Case Studies

8 Aurea 2013 Technology Products
Easier Than Ever Before Sonic: Easier to develop and deploy DXSI: Increase developer and team productivity Actional: Solve problems faster and simply Savvion: Dramatically easier to use – by everyone

9 Easier to develop, deploy and operate; cloud-ready
Deployment requirements modeling, support for location transparency, dramatically improved developer tools Hot-Hot DS’ DS’’ BR’ ESB BR’’ CAA BR Easier to develop and deploy reliable distributed integration solutions Deployment modelling removes 90% of manual steps in deploying integration processes. Support for portable deployments eliminates configuration changes and makes Sonic EC2 ready. Improved development tools increases developer productivity greatly.

10 Deployment requirements modelling
Choose Deployment Pattern ESB Node 1 ESB Node 2 Stand- alone Proc 1 Proc 2 Load Balanced Proc 3 Failover Proc 4 Define Deployment Requirements deployment model Deployment Model Generated Hot-Hot DS’ DS’’ BR’ ESB BR’’ CAA

11 Location transparency
Sonic Clients dynamically discover broker locations sonicrn:///myBroker Brokers auto-configure from the runtime environment; Amazon EC2 aware myHostB BR myHostA No configuration changes at clients or brokers!

12 Dramatically Improved Developer Tools
Everything is no more than 2 Clicks away: Edit Runtime Parameters from the overview page Edit Processing Stages Directly Use Breadcrumbs to jump directly One Click Process Tracking …and more

13 And that’s not all… Full Java 7 support and other new platforms
Top-down Sonic Connect workflows (SOAP and REST) Sonic Connect scalability update Transformation Step as intrinsic process step Predefined Eclipse user libraries New ESB Service usage metrics Centralized management of Flow Control Monitoring Interval New SonicMQ Flow to Disk Metrics Database driver updates

14 Increase Developer and Team Productivity
Broader file support, simpler change and test case management EDI File CSV Custom Easier to develop common data models and manage change Broader support for access to flat file data, multiple open projects and easier management of test cases increase developers productivity. Semantic diff and merge dramatically simplifies change management.

15 Flat-file support EDI (including SEF) CSV Custom! ACORD/AL3 [ACORD]
EANCOM HIPAA NCPDP [TELCO] AHM780 EDIFACT HL7 TRADACOMS IATA/Cargo-IMP [CARGO] and IATA/PADIS [IATA] NCPDP/SCRIPT [NCPDP] X12 In the course of developing integration solutions, you may encounter data exchanged in a flat file format that you wish to integrate with your common model. DXSI 2013 supports import and integration with EDI, including EDI extended with SEF. CSV including CSV with nesting or other complexities. And finally, DXSI 2013 supports completely custom flat file formats.

16 Custom flat file 1;Butternut Squash Inc Squash Glove Squash Racquet
Squash Balls 2;Sub Par Golf Golf Balls Golf Shoes 3;Blue Line Hockey Shin Pads Knee Guards Ice Skates Hockey Stick Hockey Puck 4;UFO Frisbee Frisbee Whistle 5;Dark Alley Bowling Bowling Ball Bowling Bag Bowling Shoes When your flat file format does not resemble a published EDI standard, You can start with a generic flat file model (click) Then define the segments along with any delimiters or regular expressions used to match the segments, etc. (click) And then you can use it just like you would any other format in DXSI. The parsed entity will look like any other entity in DXSI, with attributes and relationships that can be easily integrated with your common model.

17 Test Suites Define the test cases to be run together in a suite
Define the order of execution of those tests DXSI 2013 simplifies the management of test cases with the introduction of Test Suites. Test Suites can be used to simulate more complex test scenarios by selecting a set of test cases to execute, and in which order to execute them. In this way, for example, you can test an entire CRUD scenario. Or you can simply group related test cases together. Like existing test case support, these test suites can be integrated with a continuous build solution to ensure the quality of your integration solution.

18 Team Synchronizing Use SVN to collaborate
Resolve conflicts in a familiar way DXSI 2013 makes collaboration and team development much easier with the introduction of source control integration. Building an integration solution is seldom a solo undertaking. Using SVN, you can now share DXSI projects. Teams can use the ‘Team Synchronize’ perspective with DXSI projects and manage updates and conflicts in a familiar way, With a look and feel resembling the DXSI compare editor. Team members can compare their working revision with any other revision in the repository, and again, these comparisons will use DXSI’s compare framework seemlessly.

19 And that’s not all… XSD substitution groups support
XML sample file import (no XSD) Multiple open projects Memory management Sharing of JARs in deployed data services But that’s not all. In every release, we continue to improve some of the basics, including performance and memory footprint. DXSI 2013 also added model support for XSD substitution groups An XML importer for when you have XML with no XSD You can now have more than one DXSI project open at once in the workbench, which is useful if you want to break your project into smaller projects. We include a memory management option in case you are about to open another project that might put you over your memory limits so that you can proactively close any unneeded projects. There is an option for JAR sharing that can reduce the number of jars deployed per service and therefore reduce the overall footprint of your deployment.

20 Create, view, analyze and take fast action
Solve Problems Faster Create, view, analyze and take fast action You may be in a position where You cannot seem to understand the nature of your infrastructure problem areas: Where, when and how are they occurring? And under what circumstances? Is there a particular pattern with which they are occurring? How can you focus your problem resolution efforts to where they matter the most? OR you maybe also faced with a situation where Your customer has just submitted a large order and you have agreed to a one-hour SLA for order confirmation. But you have no idea where the order is? The customer says they have submitted it - but unfortunately you are clueless. Sounds familiar? Well with Aurea Actional 2013, the main theme of the release is – Solve problems faster. Let me quickly show you how.

21 Vasco to build out his slides
At a glance, evaluate distribution of alerts by customer segments Get graphic distributions on how Alerts are fired Create views that matter to you most Examine alarms and warnings as they happen We have introduced Alert Analytics - a completely brand new way to Visualize and Analyze Alerts in Actional (click) - you can easily examine alarms and warnings as they happen in a nice consolidated view (click) – you can easily get graphic distributions on how Alert are fired, through which - you to detect and identify problem patterns, through powerful alert distribution analysis (click) - you can also group Alerts and create views in a meaningful way, where they matter the most, and that make business sense to you. For example, if you want to know which policies are firing the most alerts, to determine either if your policy is configure properly - or you have a real production situation. You can do all that with Alert Analytics.

22 Easily identify business transaction issues
Easily locate business transactions by time or key business values and error conditions Easily analyze all associated alerts and audits for the identified transaction Track transaction dependency and errors – even in flight!!! I referred to that customer order earlier that you could not locate: Well, with Actional 2013, you can do exactly that and with great ease too: (click) – You can easily locate business transactions; by time or key business values - or even by error conditions. For example, you could see all the transactions during the last minute, last 30 minutes or last day. How about by error conditions – you can easily identify all the transactions that have generated an “out-of-stock” exception (click) and track call dependencies and error conditions - specific to that particular business transaction – even as they are in the process of occurring (click) How about easily analyzing all associated alerts and audit records for the identified transaction, in one comprehensive web 2.0 style view with no server round-tripping You get all this with Aurea Actional 2013

23 Centrally-defined Interceptor settings
Actional Management Server Actional Agent Also, we have introduced the concept of centrally-defined interceptor settings. What does that mean? (click) As the complexity of your deployment grows, naturally the number of agents (instrument your infrastructure) will also grow. Changing interceptor settings become cumbersome, and time-consuming, especially if they force you to restart the application server. (click) With Aurea Actional 2013, you can push a centrally defined – select - set of interceptor configuration settings, like turning debugging on or off, without you having to visit each agent and modifying the configuration manually and not to mention NOT having to restart the application server. Now it is all done centrally and automatically.

24 Introduced OAuth & REST support in AI
We have introduced oAuth and REST support in Actional Intermediary - Some of you may know - OAuth is a Cloud and Social media friendly open standard for Authorization protocol - It allows clients to access server resources on behalf of resource owners. Without devulging confidential personal authentication information; like username and password. - It is widely used by industry and social media heavyweights like Facebook, Flickr, Google and Paypal. (click) Actional Intermediary takes all the Oauth complexity out of implementing Oauth and makes its deployment as easy as 1, 2, 3. (click) Take the service under management, configure your Oauth security settings, and expose the service to understand Oauth with the proper level of security configured As for REST (otherwise known as REpresentational State Transfer) is proving to be an ideal, mobile-friendly, protocol - that is widely used in distributed systems on the web. Gaining continuous industry traction because its scalable, state-agnostic, cacheable and bandwidth-efficient nature However, it requires and upfront investment to re-engineer substantial system changes to accommodate REST-Based requests, (click) Well with Actional intermediary, you can actually REST, “pun-intended”, while allowing you to expose your services as REST. You can easily take your original service definition, do simple basic mapping of information and automatically generate REST-based Access Points.

25 And that’s not all… Selectable default landing page for AMS
Updated C++ SDK An updated set of Interceptors New LDAP interceptor Many version updates to the existing set But wait – that is not all….With Aurea Actional 2013 You are no longer stuck with Network Overview screen - as the only start-up screen - in the Actional Management Server. You can now select any page you like. We have an updated C++ SDK to instrument your custom and legacy applications over a wide variety of platforms. We have an updated set of interceptors - including a “brand new” LDAP interceptor - that lets you instrument LDAP authentication calls, that can potentially be performance bottlenecks. and finally, we also have many version updates on the existing interceptor set. With that, I pass the control over to Esther, who will tell you all about DXSI – take it away Esther.

26 Dramatically easier to use – by everyone
Faster development, simpler modeling and simulation and easier to use business analytics . Easier to use by all BPM user personas BPM Practitioners: Ability to create dynamic solutions without lengthy requirements gathering Process Analysts: Easy to use web based modeling and simulation for business analysts Operations Managers: Easy to use analytics to make correct business decisions quickly.

27 Easier to manage sophisticated projects
Streamlined for large-scale process design Standard features such as search, auto-complete, tagging, etc. One-Click Deployment and project hierarchies

28 BPM success requires rapid implementation
Powerful tools for UI design Create dynamic applications without coding Optimized for non-technical Doesn’t restrict advanced users

29 Build solutions faster
Custom Logic without Custom Coding. Improves development accuracy and productivity. Does not limit the potential for highly advanced process design. Traditional Coding Savvion 2013 with GEL com.savvion.sbm.bizlogic.util.Session session = null; com.savvion.common.jst.JSTools jst = new com.savvion.common.gel.JSTools(); Object tmp = null; java.util.List dsList = gel.toList(new String[]{"AmountRequested", "ManagerApproval", "SpecialFlag"}); jst.setDataslots(jst.getDataSlotRealValue(dsList)); jst.setDataslotMetadata(jst.getDataSlotMetadata(dsList)); if ">", "eq", "yes"))) { jst.copy("x", } else { jst.copy("y", }

30 Exchange ideas in real time
Introducing “Process Edge”: Making BPM accessible to the entire organization Business Stakeholder and Business Analyst Collaboration Center 100% Web based – designed for Cloud. Works on iPad and Android tablets. Changes seen in real-time by all logged in users. Detailed Revision History and Comparison Collaboration and Documentation Center Simulation on as-is and to-be scenarios.

31 Agenda Aurea Software – Company & Strategy
Aurea 2013 Technology Products Aurea 2013 Insurance Solutions Customer Case Studies

32 Aurea Insurance Solution suite
Deeply verticalized insurance BPM Creates visibility into operations and enables continuous improvements Supports complex comp. plans Plan can be reconfigured easily Is fast and scales Insurance Process Management (IPM) Distributor Compensation Management (DCM) Insurance Data Exchange Accelerator (IDEA) Simplifies access to insurance information Simplifies change management Provides common insurance data model Our DCM product is a proven mature solution for defining complex compensation plans and executing them at high speeds for large number of producers. DCM is being used by many insurance companies successfully. We want to reduce the time to value of DCM. To calculate compensation, correct and consistent information is required. The information resides in various data sources such as accounting, CRM, data warehouses within insurance companies, as well as in industry registries such as BIG, FINRA and NIPR. Companies spend large amount of time and resources to get up to date accurate data in proper form. Frequent changes of data and regulations make this information access and integration problem harder We have solved this problem. The solution is called IDEA. IDEA enables our customers to quickly access, transform, and use the information required for compensation. Furthermore, our customers are able to quickly adopt to changes in information sources and regulations. We also want to increase the value delivered to our customers. Before an agent sells products and receives compensation, s/he must be on boarded. On boarding involves ensuring that regulations are met and the agent has proper credentials. Furthermore, important information is collected in on boarding phase that is necessary for processing compensation properly. On boarding is not the only process. There are many other processes that need to be performed to ensure that the agent is happy and is productive. Agent administration, training, and compensation dispute resolution are examples of these processes. To ensure that compensation processes are executed efficiently, and are improved continuously, we are delivering IPM, Insurance process management. Lets drill down into this picture a bit more.

33 They come together in a robust solutions suite
Compensation & Compliance Manager Producer Sales and Channel Manager Insurance Process Management (IPM) Insurance Compensation Management (DCM) Insurance Data Exchange (IDEA) NIPR CRM BIG Finance FINRA Here are examples of information sources that are often used in compensation management. Note that the reality is more complex than illustrated in this picture because there are more information sources, information is overlapping and often inconsistent, and it changes constantly. IDEA sits on top of the information hair ball and masks the inconsistencies and complexities from calculating compensation and enables compensation processes to be executed efficiently. As things happen, i.e., compensations are processed, and operations like on boarding and dispute resolutions are performed, additional information such as how many dispute we had last month, how long did it take to resolve them, how many agents we overpaid, etc. are collected which enables varieties of analyses and hence improvements of operations and business metrics. Availability of up to date compensation and operational data enables various persona, including regulation and compensation managers, analysts, sales execs, and finally producers to be more effective and productive.

34 Agenda Aurea Software – Company & Strategy
Aurea 2013 Technology Products Aurea 2013 Insurance Solutions Customer Case Studies

35 British Airways Business Challenge Product Use
Enable critical business processes such as flight and customer management Enables BA to enrich the information and spot real-time customer opportunities to improve the flight experience. Product Use Sonic - for providing integration to over 250 applications. Actional Intermediary for providing a secure gateway to all of BA's downstream systems

36 Scottish Widows Business Challenge Product Use
Business critical integrations between front and back office Ability to release new products to the market every 3-6 months for life and pensions Product Use Use Sonic and Actional to integrate all back-office pension related systems - from portal-based IFA applications through to integration with a large IBM mainframe. Company Description: One of the largest UK pension funds - handling over £3.9 Billion of capital

37 Belgacom Business Challenge Product Use
Improve Operational Efficiency to leverage acquisitions Enhance Time-to-Market for new products Improve Customer Experience and Loyalty Product Use Standardization on Actional, DataXtend SI and Sonic reduced complexity Increased efficiency in the operations department using end-to-end monitoring and centralized logging Company Description: Belgacom is the incumbent Belgian operator in the telecom market. They deliver Fixed &Mobile telephony, Digital TV and fixed/mobile internet to more than 70% of the consumer market. Yearly revenue is +-9Bln USD. They are listed on the BEL-20

38 JPMorgan Business Challenge Product Use
Risk and Portfolio Management Platform needs to conform to regulatory compliance needs Near real time visibility of risk exposure for individual and risk exposure Product Use Sonic to connect the risk calculation platform and the trader desk in real time

39 Kaufland Business Challenge Product Use
Publish price updates up to four times a day to match competitor prices Run localized campaigns with specific regional prices Product Use Sonic to connect the head quarters and the stores for pricing, backordering, etc. Sonic as central messaging hub for all integration needs

40 Thank You!

41 Aurea Sonic 2013 Detailed Feature Review
Product Launch 2013

42 Problems Solved at Design Time

43 Problems in Developing ESB Processes
Problem: Working with the Process Editor typically requires too much nesting and you can loose the tasks’ context. Problem: Request or Response Message Mapping could not be enabled on a step-by-step basis. Solution: Provide this with one click away

44 Processes Editor Improvements: Overview Page
New Look & Feel and Improved Visual Feedback Searchable Palette New Outline View Step Integration with the Properties View

45 Processes Editor Improvements: Processing Stages
All Service Detail Pages Replaced with Single Page Searchable Palette Access any of the Processing Stages with One Click Enable Message Mapping for each Step

46 Processes Editor Improvements: 1-Click Breadcrumb Navigation
Breadcrumb can take you to any other step or processing stage immediately

47 ESB Configurations at Project Level
See all ESB Configurations of the Project at once Open them without having to remember their path This feature enables users to view the ESB Configurations like Services, Processes and Service Types as high level nodes at each project level.  The purpose of the feature is to provide a summary view of the project and in turn allow users to easily open these configurations. The artifacts like service configurations, processes and service types scatter at different locations i.e. in different folders and it becomes little harder for the users to remember the path of these artifacts, go to that path and open the artifacts.

48 Problems working with Process tracking
Problem: Working with process tracking requires opening the process, changing the tracking level, adding it to the tracking view, ... Solution: Provide this with one click away

49 Process Tracking Improvements
New Tracking Enabled Run enables tracking on-demand Automatically adds to ESB Process Tracking view as well

50 Process Tracking Improvements
New Clear All on Run clears view before each scenarios run automatically Preferences to show/hide tracking columns Edit the Tracking Level without opening the process

51 Sonic Connect Problems
Problem: Sonic Connect always requires a separate Project and you first have to define the operations invoked before using it in your process. Why is it so difficult if all I had to do in Sonic 7 was to drag and drop a WSDL? Solution: Provide Top-Down Sonic Connect workflows and other enhancements

52 Top-Down Sonic Connect Workflows
Drag and Drop of a WSDL creates a Sonic Connect Web Service not a V7 one. Create New RESTful or Web Service Client directly from Sonic Connect Step NOTE: other change is that Sonic creates generic restful client only on demand during the creation of SC project

53 Optional Generic RESTful Client
Skip creation of the generic client in new Sonic Connection Project wizard Add it later in the Sonic Connect Editor if you really need it Sonic Connect Project allows users to build Web Services/Clients as well as RESTful Web Services/Clients. But by default the Sonic Connect Project gets created along with the Generic REST Invocation Operation.  It might not be required for all users. The Generic RESTful Service comes handy and very useful in quickly invoking any RESTful Web Service. For any unit testing or experimental purposes, users need not run through the multipage RESTful Web Service Client creation wizards for every RESTful Web Service.  They can just use this generic one to achieve the same, this is the idea behind the Generic RESTful Web Service client.

54 Sonic Connect Scalability Update
Third Party Upgrades Apache Camel 2.10 (was 2.1) Apache CXF 2.6 (was 2.2) Jetty 7.5 (was 6.1) Benefits Improved scalability by avoiding blocking while waiting for response from itinerary (uses asynchronous processing overhaul in Camel and CXF). Java 7 Support

55 Transforming Messages
Problem: The Transformation Service just supports multiple message parts just with custom code and it is always XSLT Solution: Provide an explicit transformation step and generally enhanced graphical mapping

56 Transformation Step replaces Transformation Service
Graphical Message Mapping Support for all message parts and headers

57 New Graphical Mapping Features
New Look & Feel Flattened Message Structure New Transformations Encode and Decode Binary Hex or Base64

58 ESB Service Type Development
Problem: How to write services supporting custom metrics and notifications? Solution: Introduce Sonic Foundation Classes based ESB services as new default.

59 Sonic Foundation Classes
Sonic Foundation Classes (SFC) template is the default for new ESB Services

60 Predefined Eclipse User Libraries
Custom ESB Services or Interceptors projects made portable Projects use Libraries instead of local paths Backed by a single Classpath Variable SONIC_HOME JSDEBasicLibrary for XQService based custom services JSDESFCLibrary for SFC based custom services ESBJUnitLibrary for Junit projects SonicInterceptorLibrary for Sonic interceptors SonicGeneralLibrary are the MQ jars

61 ESB Service Layer Improvements: Concurrent Calls
Separated Number of Listeners from Concurrent Calls Listeners now just define number of JMS sessions Concurrent Calls define how many threads can enter an ESB service instance

62 Problems Solved Moving to Production

63 Deployment Topology and Process Capabilities
Problem: Once done with development how do I move my project to testing and production? Solution: Brand new deployment topology tooling focusing on most used Logical and Physical Deployments

64 Most Used Logical Deployment Patterns
Basic DS BR ESB CAA DS’ DS’’ BR’ BR’’ ESB Hot-Hot DS’ DS’’ BR’ ESB BR’’

65 Most Used Physical Deployments
Box 1 Box 1 Box 2 Box 3 Box 4 ESB ESB ESB ESB ESB BR BR’ BR’ DS BR’’ BR’’ Box 1 BR’ Box 2 BR’ DS’ DS’’ BR’’ BR’’ DS’ DS’’ 1 Box & Basic 2 Boxes & CAA or Hot-Hot 4 Boxes & CAA or Hot-Hot

66 Process and Service Level Topology Tooling
1) Choose a Deployment Pattern 2) Drag and Drop Processes onto Functional Areas Stand- alone Proc 1 Proc 2 Load Balanced Proc 3 Failover Proc 4 Node 1 Node 2

67 Topology Improvements
3) Generate an SDM Model Generated Artefacts: Service Instances Entry, Exit, Fault and RME endpoints ESB Connections ESB Containers MF Containers Brokers Clusters Queues/Topics

68 Problems Solved Operating Sonic

69 Continuously Improve Operations
Problem: How do I tune a Sonic ESB deployment? Solution: Let the services report on current and average usage.

70 ESB Service Layer Improvements: New Metrics
New Metrics for ESB Services RefreshIntervalMaxActive Usage AverageUsage Both for Listeners and Concurrent Calls The following metrics measure usage of JMS listener threads: esb.service.listeners.RefreshIntervalMaxActive   - Measures the highest number of listeners active within the refresh interval. esb.service.listeners.Usage - Percentage metric measuring the used capacity over the refresh interval. esb.service.listeners.AverageUsage   - Measures the average percent usage over the collection interval. The following metrics measure concurrent requests (which includes both JMS requests and intra-container requests): esb.service.concurrency.RefreshIntervalMax  - Measures the highest number of concurrent service requests active within the refresh interval. esb.service.concurrency.Usage  - Percentage metric measuring the used capacity over the refresh interval. esb.service.concurrency.AverageUsage   - Measures the average percent usage over the collection interval.

71 ESB Service Layer Improvements: Sub-component status reporting
Offline ESB Services will render containers yellow

72 Flow Control Monitoring
Problem: How do I find out if a messaging producer is blocked? Solution: SonicMQ will turn on flow control monitoring by default and without requiring restarts.

73 Default Flow Control Monitor Interval for JMS Clients
Changed the default from 0 seconds to 60 seconds Broker or Cluster-wide setting Changes are applied dynamically to all subsequent connections This new functionality is only available to JMS clients using the SonicMQ 2013 client libraries and connecting to a SonicMQ 2013 broker. The Monitor Interval for older clients continues to default to 0.

74 Monitoring Interval Information per Client
To find out the Monitoring Interval in effect use the JMS Connection View Actual Value available on a per connection basis

75 Blocked Producers despite Flow to Disk?
Even with unlimited Flow to Disk a client can run into flow control ~500,000 messages New Metric FlowToDiskMemorySize showing current usage New Alert for high and low thresholds A few customers have run into flow control despite Flow To Disk being enabled due to the broker hitting the MAX_FTD_MEMORY_SIZE limit. There's a small amount of heap-usage associated with each message that's flowed to disk. This memory is tracked and flow control kicks in if it reaches MAX_FTD_MEMORY_SIZE. The default value of 32Mb typically allows for ~500,000 messages. Without a heap dump it's not currently possible to tell whether the MAX_FTD_MEMORY_SIZE has been hit, or to monitor whether a system is approaching this limit. A new metric, broker.bytes.FlowToDiskMemorySize, and an associated alert will be provided to expose this memory usage.

76 Seamless Operations Problem: How do I seamlessly run Sonic on physical hardware, virtualized environments or in the cloud without manual interventions? Solution: Make it agnostic to location and network changes.

77 Location Transparency in Configurations
If you want to move a broker to a new machine you have to change at least three things Broker Acceptor JNDI Clients ESB Clients Many times there are many more places to change In future you will not have to change them at all

78 Location Transparency in Client Configurations
New Discovery Protocol sonicrn:///<routing node name> [?acceptor=MY_ACCEPTOR] Routing Nodes can be either clusters or brokers URL resolves dynamically to all MY_ACCEPTOR of the given routing node Supported Client Configurations JNDI Connection Factories ESB Connection Configurations If acceptor= is not specified it returns URLs for all acceptors Also support optional URL field ?visibility=all|external|internal

79 Discovery Protocol ‘sonicrn’ and JMS Clients
Location Changes of broker peers are fully transparent to CA clients Zero-Downtime of the clients Seamless failover Client caches resolved URLs Update only on change

80 Location Transparency in Broker Configurations
Dynamic Host Binding auto-configures Brokers and Cluster from the runtime environment Auto-Configured Broker Configurations Acceptors Interbroker Acceptors Replication Connections

81 Broker Dynamic Host Binding
Turn it on at Broker or Cluster Level Acceptor now takes hostname from target machine Replication Connections too take hostname from target machine

82 Amazon EC2 Integration Amazon EC2 meta data APIs used to retrieve public and private hostnames Broker Acceptors and Replication Connections listen to the private hostname Both Public and private hostnames are reported to clients in sonicrn:// resolved URLs sonicrn:///<routing node name>[?acceptor=MY_ACCEPTOR [&visibility=all|external|internal]] By default you'll see both the public and private ones.  In other words the client will be given all the possible available URL's to try.  If you want only the public IP's you can do this:   sonicrn:///MyNode?visibility=external You can also limit the URL's to those for a specific acceptor:   sonicrn:///MyNode?acceptor=SSL_ACCEPTOR And these can be combined:   sonicrn:///MyNode?visibility=external&acceptor=SSL_ACCEPTOR

83 Miscellaneous Items DataDirect Driver update to 5.1 and rebranding
New classnames are com.aurea.sonic Java 7 is default XML Server tools and BPEL Server are removed

84


Download ppt "Aurea and Aurea 2013 Products"

Similar presentations


Ads by Google