1 / 80

V611 e-Biz Impact 5.3 Technical Session: Migration

V611 e-Biz Impact 5.3 Technical Session: Migration. Aisha El-Zorba Product Manager e-Business Division Email: aishael@sybase.com. e-Biz Impact. Sybase e-Business Platform. Sybase e-Business Platform Comprehensive, Modular, Integrated and Open. Enabling Your Customers. Empowering

skyla
Download Presentation

V611 e-Biz Impact 5.3 Technical Session: Migration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. V611e-Biz Impact 5.3 Technical Session: Migration • Aisha El-Zorba • Product Manager • e-Business Division • Email: aishael@sybase.com

  2. e-Biz Impact Sybase e-Business Platform

  3. Sybase e-Business PlatformComprehensive,Modular, Integrated and Open Enabling Your Customers Empowering Your Enterprise Enriching B2B Interactions Trding Partners Customers Enterprise Access Power Designer Enterprise Portal - Web & Mobile Access Integrate Process Server Biz Tracker Integration Server Application Adapters Web Services Develop Transact Java IDE Application Server Business Intelligence Replication Database Metadata Repository - Configuration Security - Install - Management SYBASE e-Business Platform

  4. Power Designer Enterprise Portal - Web & Mobile Access, Openbiz Process Server Biz Tracker Integration Server Application Adapters Web Services Java IDE Application Server Business Intelligence Replication Database Metadata Repository - Configuration Security - Install - Management SYBASE e-Business Platform Sybase e-Business PlatformSupport for Web Services • Simple Web Services • Defined as: UDDI, WSDL, SOAP • Supported through • EAServer • PowerDesigner • Collaborative Web Services • Defined as: B2B, RosettaNet, ebXML • Supported through: • Web Services Integrator • OpenBiz

  5. Sybase e-Business Platform Access Power Designer Enterprise Portal - Web & Mobile Access Integrate Process Server Biz Tracker Integration Server Application Adapters Web Services Develop Transact Java IDE Application Server Business Intelligence Replication Database Metadata Repository - Configuration Security - Install - Management SYBASE e-Business Platform

  6. e-Biz Impact e-Biz Impact 5.3 New Architecture

  7. e-Biz Impact Architecture

  8. e-Biz Impact Manager • Also referred to as a Cluster • Coordinates the activity of Controllers and must include at least one Controller • Starts and Stops the Controllers contained within the Cluster

  9. e-Biz Impact Instances • An instance of e-Biz Impact is one Impact Manager with one or more Controller • You can have multiple instances of e-Biz Impact running on the same server • Bridge technology allows you to bridge instances of e-Biz Impact to another instance of e-Biz Impact

  10. e-Biz Impact Controllers • Contains and manages these e-Biz Impact applications: • SFM • ODL • multisrv • Custom • These are applications of a local controller • Each controller is a process and each application within a controller is a thread

  11. e-Biz Impact Applications • ODL Applications • Acquisition AIMs • Delivery AIMs • multisrv • Multiple instances of a single ODL application to be run simultaneously • Custom • User-defined applications such as C-based AIMs • Appear on the e-Biz Impact monitor after you define an application group for the custom application

  12. Cluster and Application Example Cluster Applications

  13. e-Biz Impact e-Biz Impact 5.3 Feature list

  14. e-Biz Impact Features • Same functionality as Impact 4.x • Animation AIMs are available via a bridge from e-Biz Impact to Impact 4.x • Component-Based Architecture • BSM is replaced by Impact Manager • Impact Manager • Enables multiple, parallel “clusters” of e-Biz Impact to run separate instances on the same server • Facilitates distributed processing on systems that support multi-processing Continued …

  15. e-Biz Impact Features • Bridge components allow cluster-to-cluster communication via DFCs • Allows communication between multiple instances of e-Biz Impact running in separate clusters • Enables e-Biz Impact to run in parallel and exchange data with existing installations of Impact 4.x • Enables e-Biz Impact to communicate with Impact 4.x Animation AIMs • Component-Based Architecture allows for Hot Plugging support • Individual applications can be started and stopped without bringing down other applications Continued …

  16. e-Biz Impact Features • New Monitoring GUI • Secure and centralized command and control facilities • Do not need to use DCE • MMC (Microsoft Management Console) based snap-in • Logfile Maintenance accessible through Global Console • New Security GUI • Define authentication and authorization levels for access to e-Biz Impact • Authorization for specific actions can be assigned Continued …

  17. e-Biz Impact Features • Command and Control Utility • A new command-line utility to access the security database to authorize user permissions • This utility can also stop, pause and restart activity in the Impact Manager at several levels, including clusters and applications • New Configuration GUI • Provides centralized configuration for all of e-Biz Impact • Multiple configuration files and manual configuration is eliminated Continued …

  18. e-Biz Impact Features • E-Mail Notification Enhancements • SMTP e-mail notification has been added for alert notification • Simplifies configuration and administration of alerts • Updated IDE Tools • IDE (Integrated Development Environment) tools now support additional ODL objects and methods • Supports NDO (New Era Data Object) data structures and XML data structures Continued …

  19. e-Biz Impact Features • Interoperability • Compatible with other New Era of Networks / Sybase products including: • BizTracker • Process Server • Clinical Gateway • HIPAA and EDI Adapters Continued …

  20. e-Biz Impact Features • Expanded Data Structure Support – NDO support • NDO (New Era Data Object) is a structured “tree” data format that preservers metadata associated with source messages • e-Biz Impact supports end-to-end NDO support which enables this type of data manipulation: • Tree-to-tree • Tree-to-stream • Stream-to-tree • Ensures compatibility with other products and with XML data sources Continued …

  21. e-Biz Impact Features • XML Support • NDO messages can be serialized into XML data format • Ensures compatibility with XML-enabled applications • Open Transport (OT) Support • Support for New Era of Networks Open Transport ensures compatibility with message transports • Compatible message transports including: • MQSeries • MSMQ Continued …

  22. e-Biz Impact Features • Database Libraries integrated with ODL • Support for new database libraries remove the requirement for Openlink or Roguewave • DFC Message Size Increased • Message length supported by Distributed Function Calls (DFCs) is increased • 64K size limit is removed • Upper limit is only dependent on available system resources Continued …

  23. e-Biz Impact What’s different ?

  24. e-Biz Impact Differences • BSM is replaced by the e-Biz Impact Manager • BSM-based applications msgsrv and v2sfm work the same but internal logic is different • msgsrv is replaced by an ODL server application • v2sfm is replaced by an SFM application

  25. Animation AIMs • Animation AIMs are supported under BSM of Impact 4.x • Bridge components provided with e-Biz Impact will link e-Biz Impact with Impact 4.x • Bridge components allow you to maintain Impact 4.x installations while migrating to e-Biz Impact

  26. DFC Changes • 64 KB message size limit removed - Negates the need for DFC file objects or FileMover • File objects no longer supported in DFC - Still supported in ODL • Explode and combine functions are not supported • If bsmtab application reads: • A: appname…msgsrv project.prf – d then you do not need to make changes, if the –d is included • If you are using file objects within route_recx calls to SFM - You must remove the argument from the call • If you are receiving file objects in the servproc call from SFM - You must remove the file object argument from the function

  27. ODL Object Changes • Major changes include: • Combine Object • Explode Object • Removal of clfile limitation • Changes to how e-Biz Impact starts (protomain eliminated) • fret • Sets the return value and output wire format for a DFC call • Production pair calls are now obsolete. Function entry method for DFC should now be used.

  28. e-Biz Impact Authorization Tool

  29. Why Authorization? What benefits? • Implement security policies to prevent unauthorized access to the impact server • Customize access on objects and authorize execution of commands to guarantee a maximum level of security • Standard MMC Snap-in. Easy to learn. .

  30. Authorization Tool, What is it? An MMC Snap-In User Interface An authorization database

  31. What does it do • Add/Remove/Rename security entities • Build security roles for authorizing users to execute commands against objects. • Control the referential integrity of the security entities in the authorization database.

  32. Login to the authorization database Only security administrators can access and configure the security policies in the authorization database

  33. Define groups A group entity manages a user defined number of commands. You may choose to define group names by using functional areas such as Monitoring, Web modules etc or technical areas such as AIMs management etc.

  34. Add commands to group A group comprises commands. Add commands into groups to easily manage your commands. There are only predefined sets of commands that can be executed against your impact server. Example of commands: ResubmitTransaction, Shutdown, etc.

  35. Define objects An Object is an entity that is intended to replicate your application infrastructure. Example of object: Manager, POController, POCheckSFM, POSubmitSFM, etc. Each object has a type that can be chosen between SFM, CONTROLLER or MANAGER.

  36. Define roles A role is an entity intended to define a security policy. A role authorize commands within a group to be executed on a user defined object. Example of role: Standard Web User role can execute the acceptTransaction command defined in the WebGroup against the POSubmitSFM object.

  37. Associate an object and a group to a role While defining a role, you will be prompted to select an Object and a group. By doing so, you build a security policy that authorize a role to execute commands defined in the group against the selected object. Example of role: PORole role can execute the acceptTransaction command defined in the EngineGroup against the POEngine SFM object.

  38. Define users A user is granted access the Impact server and assigned roles. Example: A web client interfaces can use a standard Webuser to access the Impact server

  39. Assign roles to a user You may assign roles to a user to authorize him executing commands against objects. Example: A Webuser is assigned with Standard Web User role

  40. e-Biz Impact e-Biz Impact Global Consol

  41. What benefits? • Remote control of multiple Impact Server execution • Repair invalid transactions and destinations • Control of impact servers only granted for authorized users • Performance analysis allows implementation of optimization and tuning strategies of Impact servers • Standard MMC Snap-in. Easy to learn. • Compliant with SNMP standards .

  42. Background • Global Console Snap-in is the evolution of the character based TDM console • Global Console monitors multiple Impact servers through SNMP

  43. What is the Global Console GUI An MMC Snap-In User Interface

  44. What does it do • Add/Remove/Rename CNMP monitoring agents • Connect/Disconnect agents to Impact servers. • Execute administrative CNC commands against the various server components (Managers/Controllers/Applications) • CNC Commands must be authorized for the logged-in user.

  45. Define an Agent All Users can define an agent. An Agent monitors an Impact cluster through SNMP The agent properties must specify a Host name.

  46. Work with an agent From the agent node, you may connect to a Host. Once connected, the agent will monitor the Impact server by representing the data he receives from the server MIB through SNMP MIB: Management Information Base SNMP: Simple Network Management Protocol

  47. Agent displays Impact server structure Once connected, the agent will display the Impact server structure.

  48. Login to a manager A user must login in order to execute commands on the various objects in the the Impact server bus. Only authorized users can login.

  49. Execute CNC commands A user can execute a Command by selecting it from the context menu. CNC: Command and control

  50. Accessing Views SFM, AIMs and Destinations applications offer several views. Each one of those views appears in the MMC Result view.

More Related