Posts Tagged ‘BMC Remedy Architecture’

Webinar: Is a SaaS-based or on-premise ITSM solution right for you?

June 28th, 2011

 

Is a SaaS-based or on-premise ITSM solution right for you?

SaaS isn’t for everyone. It may not even be for you. Although we’d love to bend your ear on the benefits of moving your IT service desk to the cloud, the bottom line is that there is no one size fits all approach.

SaaS vs. on-premise – choosing the model that’s right for you is a great webinar that guides you to the best delivery model for your business needs. It steers you through the myriad of people, process, technology, and financial considerations that are essential to making an informed (and successful) decision.

View this webinar today and learn:

  • Why company size doesn’t matter in making the SaaS vs. on-premise decision
  • The pros and cons of outsourced, managed, SaaS, and onsite delivery models
  • If you choose SaaS, how do you get started?
  • What to look for in an ITSM vendor, SaaS and on-premise

Webinar:
SaaS vs. on-premise – choosing the model that’s right for you

Recorded: Tuesday, June 7, 2011

Featured Speaker:
Chris Williams, BMC Software

Register here

BMC Remedy Architecture in 5 min

June 14th, 2010

This is continuation to the previous post http://remediesforremedy.com/2009/08/remedy-101-bmc-ar-system-remedy-architecture/

 Remedy Architecture:

 1.Presentation Layer-

 As I said we have Remedy Administrator Tool/Developer Studio(Remedy IDE), we handle all the Form/Workflow creations in this-(Admin/Development activities),

 Form creation would be a kind of drag and drop as you do it in VB, wherein we have Form Object listed aside like Character/Text Field,Drop Down,Integer Fields,Borders,Labels……

 Once you design our Form Structure through drag and drop, the same structure would be saved/represented in the DEF File format in the Remedy Server.We don have to code as you do in Java for creating Forms here.(using Admin Tool/Developer Studio Remedy IDE’s-connecting to Remedy Server, through simple click and drag method to create Forms).

 

2.Business Layer-

 To define Business Layer, in Remedy IDE itself we have seperate Windows to create ARSystem Objects(Active Links,Filters and Escalations) through which again a simple drag and drop with your logical operators to build the Remedy Workflows.

 Again this will be represented in the DEF File, which Remedy Server can interpret and execute it.

 

3.Database Layer-

 The data which is being shown in the Presentation Layer and the operations which are being performed in the Business Layer will ultimately goes to the Relational Database(like Oracle,DB2,My SQL).

 The End user will be interacting with the Remedy User(thick client)-exe, or through Browser(thin client), the Remedy Forms and Workflows which you designed in the Remedy IDE will be viewed in these two client tools,

 On performing actions in the User Tools by the End User, there will be an API communication from these Client to the Remedy Server and through which the Forms will be loaded and the Workflows will be executed in the Client and Server Environment.

 There is no coding of any programming languages required to create Standalone Applications(Set of Forms and Workflows) on Remedy Platform-All you need to know is to understand the Remedy Workflows and Tools.

 With this platform, BMC has powered ITSM applications to automate the Service Management(you can go through ITIL to understand what is being done in the Incident and Problem framework, but through this platform you can build any kind of ticketing/enterprise applications(as mentioned earlier) which you may want to represent in the Web with out core programming.

 Thanks to Ashwanth for this detailed explanation on BMCDN.

%d bloggers like this: