SDK on the BO platform - installation, updates, security

[Former Member]

Hi everybody,

i´ve some pretty important questions regarding SDK Extensions and their installation on a BO platform. I´m really interested in your thoughts and opinions and hope for your answers.

1) Could SDK components force a BOE server crash?
Currently, i would say 'no'. From my point of view the sdk component runs completely on the client and only the properties are managed by the server. So as i understand, it´s not possible at all to force a server crash by the component due to the whole sdk-architecture. The only thing a bad designed component could do is to crash the client. Am i right or is there anything i haven´t considered?

And what do you think of sdk regarding security?

2) Installing SDK Extensions on the BI platform without restarting the server?

Is it possible to install a sdk component on the BO platform without doing a server restart? Restarting the server for every deployment might be a real problem in big environments with thousands of users and a guaranteed uptime.

3) SDK extensions and BOE platform updates

What do you think about SDKs in reference to regular BO platform updates? Is there any risk in using sdk components? I´ve heard of concerns, that platform updates might lead to non-working components (e.g. due to interface changes etc.) and a high risk of maintenance efforts. How do you see this point/risks?

I look forward to reading your answers and points of view. Thanks so far!

King regards,

Sebastian

[former_member186440 · Accepted solution]

Hi Sebastian,

my experience is

1) Can components crash the server?

with faulty javaScript this will not happen, a however faulty ztl can do this, as it causes Java classes to be generated. Maybe it just crashes the session though, not the whole service. With a faulty xml descriptor I am not sure, maybe the xml validator makes that part safe.

2) Server restart necessary?

You only need to restart the APS Service in the CMC for Design Studio, no other parts of the server.

3) BO platform update

I expect the SDK to maintain a high degree of forward compatibility. The API design is very well thought out and generic. Therefore this risk is very small in my opinion.

Best Regards

Jörg

[Former Member · Accepted solution]

Hi Jörg,

many thanks for your response. I think your remarks correspond with my opinions. Due to the fact that the ztl with its clear focus (setting & getting properties) might be the only trouble item makes the SDK more applicable and very safe. From my point of view, the risk that anything is bad coded in the ztl is managable and excludable.

@all: If anybody else disagrees with Jörg´s and my views, please feel free to post it here. I´m really thankful and open for your minds and hints.

Best regards,

Sebastian