© 2010 IBM Corporation What’s New in RSA 8.0 Beta 1 – Deployment modeling March, 2010

© 2010 IBM Corporation2 What’s New in Deployment Planning & Automation  Usability enhancements for creating topologies –New Topology wizard provides various templates and samples –Better feedback for figure creation –Simplified link handle for link creation  Diagram enhancements for powerful and aesthetic diagram rendering –Improved rendering customization with Theme and Appearance support –Easier organization and filtering with Layers –Clear, readable layouts even with highly connected diagrams  Codeless Technology Domains  Domain updates for WebSphere, DB2, Portal  Better support for Operational Modeling – deployment unit types  Improved Build Forge discovery

© 2010 IBM Corporation Creating topologies: Creation Wizard  The topology creation wizard can now create a new topology from a template or an archive file.  New users can get a fast start on modeling their topologies by building on these templates and examples.

© 2010 IBM Corporation Creating topologies: Creation Wizard  Archived examples can contain multiple topologies and support files.  Multiple archives can be extracted into the same project.

© 2010 IBM Corporation Creating topologies: Editor Feedback  A blue rectangle highlights when a unit can be contained by another unit when created or moved.  Or to show what is the target of a new or redirected link.  New creation feedback helps guide the addition of new units and links to a topology.

© 2010 IBM Corporation Creating topologies: Single Lollipop  A single lollipop now appears when hovering over a unit.  A context menu controls what type of link is created.

© 2010 IBM Corporation Creating topologies: Hosting Link Creation  When creating hosting links, a new dialog appears to help you create any missing hosting requirement or capability.  You can create a matching requirement or capability or both.  This support is already provided for creating dependency links. No other link type requires a matching requirement and capability to be created.

© 2010 IBM Corporation Creating topologies: Renaming Units  Units can also be renamed by selecting a unit and just typing, however the entire original name is overwritten.  Select the unit, then hover over it to show the rename button  Then click the button to open the name for editing.  A new rename button makes changing a unit name more robust and faster.

© 2010 IBM Corporation Creating topologies: Documentation  A new “Documentation” tab has been added to the property sheets for Diagrams, Units and Links which consolidates all of the “Description” tabs into one location.  In the Diagram Documentation property sheet you can now add a description for the topology or each diagram.

© 2010 IBM Corporation Clarifying diagrams: Diagram Layers  Diagrams can now be broken up into layers.  Hide or show layers to focus on different aspects of a topology.  Units or even just links can belong to a layer.

© 2010 IBM Corporation Clarifying diagrams: Diagram Layouts  There are several new automatic layout formats to help layout different types of diagrams.

© 2010 IBM Corporation Clarifying diagrams: Appearance Property Sheet  Units, Links and the Diagram now have an Appearance property sheet to control all unit and link rendering styles.  Controllable unit styles include color, font, border, transparency, details, title and image. Note that the Unit Style and Unit Details Dialogs have been collapsed into the Property sheet, sunsetting the original actions.

© 2010 IBM Corporation Clarifying diagrams: Appearance Property Sheet  Controllable link styles include color, style, routing and thickness.  For both units and links there are a lot more default colors to choose from.  The Diagram Appearance property sheet controls the color and details of all the units and links in the diagram.

© 2010 IBM Corporation Clarifying diagrams: Appearances  Unit and link style settings can now be saved as an “Appearance” and applied to other units or links. 1) Pick a unit or link whose appearance you want to copy. 2) Use “Add to Appearances” command. 3) Give the appearance a name. 4) Pick one or more units or links to apply the appearance to. 5) Use the “Apply Appearance” command to apply the appearance to the selected units or links.

© 2010 IBM Corporation Clarifying diagrams: Themes  “Themes” are collections of these “ Appearances ”.  When a Theme is applied to a diagram, what Appearance is applied to what unit or link is based on their type.  When a Theme is applied to a diagram, all new units and links will also be created using the Appearances in that Theme. 1) Add one or more unit or link types to the current theme. 2) Assign an Appearance to each of these types. 3) Save the theme under a new name. 4) You can then apply this custom theme to other diagrams.  There are several predefined themes or you can create your own in the “Appearance” tab of the Topology Editor preferences by:

© 2010 IBM Corporation Clarifying diagrams: Themes  Another way to create your a custom Appearance and Theme is from the “Appearance” property sheet: –You can then apply that Theme to any other diagram. 1) After setting up a unit or link’s appearance, click on this button to open this dialog. 2) Clicking OK in this dialog will: a) Create or overwrite an appearance b) Create a custom theme if not already created. c) Add the Appearance to the theme using the type of the currently selected unit or

© 2010 IBM Corporation Clarifying diagrams: Clarifying Links  Several new features help improve link clarity in a highly connected diagram.  A new Clarify Line action helps clarify the links in a large diagram by using color and link routing.  Connections to inner tree items now make the tree item taller to help differentiate each connection.  Links are routed to avoid overlapping each other.  Links are routed underneath units but are draw faded to make following the link easier.  The effect is that highly connected diagrams appear as clearly as circuit diagrams.

© 2010 IBM Corporation Dynamic Domain Creation – Overview  Mechanism to enable codeless, or “dynamic” domain content –Custom units and capabilities defined in a basic metamodel (Ecore) –Domain content serialized with strong XML types seamlessly into existing topologies –Dynamic domain types behave as other “static” types in code  Dynamic types are made available throughout the tool –Dynamic domain units available from the palette –Dynamic domain capabilities available from capability and requirements dialogs –Palette entries can be customized (icon, label, etc.)

© 2010 IBM Corporation Dynamic Domain Creation through Ecore  Create Ecore file with Unit and Capability definition –Use the default Ecore editor –Import from XSD (recommended)  Import dynamic domain ecore files into workspace –Can have multiple dynamic domain ecore files in the same project

© 2010 IBM Corporation Dynamic Domain Creation through Ecore  Open Palette and view dynamic domain units –“Custom Domains” palette drawer –Custom stack for each dynamic domain namespace

© 2010 IBM Corporation Dynamic Domain Creation through Ecore  Validations run on dynamic domain units as with other units  Linkages can be created between dynamic domain units as with other units

© 2010 IBM Corporation Domain Enhancements – WebSphere Datasources  Added Derby Datasource 5.0  Added Derby JDBC Provider  Added Oracle Datasource 5.0  Added Oracle JDBC Provider

© 2010 IBM Corporation Domain Enhancements – WebSphere Datasources, cont.  Datasource enhancements –Added JDBC Connection Pool capability to all WebSphere datasources –Added J2EE Resource Properties to all WebSphere datasources and JDBC providers Configuration units hosted on providers, datasources –Added other attributes as required by automated deployment scenarios

© 2010 IBM Corporation Domain Enhancements – WebSphere User and User Registries  Added support for a WebSphere User –Configuration unit hosted on a WebSphere User Registry  Added support for WebSphere User Registries –Configuration unit hosted on WebSphere Node or Cell –Can have member (operating system) Users –Subtypes: LDAP and Custom

© 2010 IBM Corporation Operational Modeling – Support for Deployment Unit types  Operational Modeling uses the idea of a “Deployment Unit” to represent an “aspect of a Component” for deployment  By modeling the Deployment Unit type, we provide more flexibility to users performing OM  Deployment Unit types leverage standard UML classes with stereotypes

© 2010 IBM Corporation Operational Modeling – Support for Deployment Unit types  Stereotype properties enable users to record standard Non-Functional Requirements (NFRs) about the Deployment Unit  Recorded NFRs are synchronized with deployed instances in the Topology

© 2010 IBM Corporation Operational Modeling – Support for Deployment Unit types  Drag UML components as supported in RSA 7.5, but new functionality also brings along deployment units

© 2010 IBM Corporation Operational Modeling – Support for Deployment Unit types  Validations and resolutions keeps the Topology in sync with the UML model

© 2010 IBM Corporation Enhanced Build Forge Parameter Discovery  Existing integration enables discovery of Build Forge libraries and their parameters  Limited parameter discovery in RSA  Enhanced support identifies more forms of embedded parameters  Includes discovery of “out” parameters that are set during execution

© 2010 IBM Corporation Enhanced Build Forge Parameter Discovery  Open Discover Automation Definition wizard to show exiting libraries on a Build Forge Server:

© 2010 IBM Corporation Enhanced Build Forge Parameter Discovery  Parsed parameters displayed in editable view for client augmentation  Results are added to the new Automation Signature