Submitted by Anonymous (not verified) on Sun, 02/24/2013 - 00:00
Forums
IceBreak

Niels,

Thanks for the presentation last night.

I have some questions, apologies if these were covered after I left the call.

1. What IBM LPP pre-reqs are required for Portfolio? Are the requirements the same in the development environment and the deployment environment?

2. When you import a file or library in to Portfolio will it recognise any referential constraints already defined and use these to make the associations between the tables?

3. When an application is created are any programs generated or is Portfolio just using SQL?

4. When Portfolio is updating multiple tables, I assume using SQL, does the SQL statement use commitment control?

5. I remember you showed us the forms designer to change the layout of the portals and the fields within them. Can the forms also be customized to change colours, add logos etc.?

Thanks,

Glenn

Niels Liisberg

Sun, 02/24/2013 - 00:00

Permalink

Hi Glenn,

My answers to your questions:

1. What IBM LPP pre-reqs are required for Portfolio? Are the requirements the same in the development environment and the deployment environment?

The short answer is no. That is - you dont need SQL compiler nor RPG or other development tools to do basic table manipulation. However, if you like to wrap your existing applications you will need RPG, SQL or to create IceBreak applications which is the simplest way to integrate existing applications. Also you can run PHP , CGI and java inside Portfolio as wrapped applications which requires nothing more by portfolio.

2. When you import a file or library in to Portfolio will it recognise any referential constraints already defined and use these to make the associations between the tables?

In the current version - no. But it will. Right now we have focus on bringing legacy applications to the web and these have typical no fancy DBM features like DB associations.

3. When an application is created are any programs generated or is Portfolio just using SQL?

Yes and no. The default templates are 100% dynamic and need no compilers. You can however select the client/server template which uses a good generator to produce the server side and client side code which again need to be compiled (server side).

Also when it comes to adding business roules / logic you need to make a "proxy" that executes the validations etc. Server side this is RPG or COBOL or even C++.

4. When Portfolio is updating multiple tables, I assume using SQL, does the SQL statement use commitment control?

Great question! For the time beeing the answer is no. The type of transactions are very monolitich so we dont need commit and the typical application we are tergeting will have no commitment controle. However, I see that as an option in future reases, where relatons are updated and comitted

5. I remember you showed us the forms designer to change the layout of the portals and the fields within them. Can the forms also be customised to change colours, add logos etc.?

I only showed the top of the iceberg. The designer has a lot more to offer. You can add new database fields, add behaviours, validation and server side / client side logic which can be reused in any other forms. Adding new components, change colurs, sizes, rearange the portal content, move components from one portlet to another, and promote a portlet as tab or as a new application.

I will make a new webinar on how to use the forms designer very soon.

And thanks for your time.

Regards,

Niels Liisberg

Niels,

Thanks for the replies.

Looks like there's a whole lot more for me to learn about Portfolio.

Glenn

Hi Glenn,

As soon I am back from vacation, I will prepare an "into detail" demo for you guys... And for some good reasons 1) to let you know the product better, 2) if we are missing anything....

Regards,

Niels Liisberg