Phi-Technology

From PhiWIKI

Jump to: navigation, search

Contents

White Papers

Manual

PHI RE

HW and SW requirements
EAP configuration

DBMS

Using Oracle
Using Mysql
Using Progress

PATIDOK integration notes

Adjusting Progress Databases and Tables to work with Hibernate
Using SonicMQ as JMS provider for JBOSS
Creating DataAccess for Patidok
Integrating a Patidok applet in a PHI page

PHI DESIGNER

Guidelines for developers - guidelines, how to procedures, tips and tricks for DESIGNERS.

PHI ESB

SOA configuration

PHI BI

PENTHAO BI TOOL SUITE was choosen by PHI to implements BI where it's required.. soon more detail!

DOWNLOADING and assessing

If you are intentioned to download the PHI TECHNOLOGY to assess and evaluate then follow this procedure:

 1. mail to ANDREA CEINER and DAVIDE MAGNI specifying :
   - you role in your organization
   - the business scenario you are thinking of
   - the scope of your interest
 2. you will receive the EULA (End User License Agreement [1]) that must be signed by both parties
 3. you will receive via internet or cd-rom the latest stable version of PHI TECHNOLOGY

CONTRIBUTION TO PHI TECHNOLOGY

When you are in the need to have a new phi-Technology

- widget

- validator

- function

- converter

- plug-in


then follow this simple PROCEDURE (soon available the final PROCEDURE this is only a DRAFT not yet operative any doubt [DAVIDE MAGNI]:

1) Open in this wiki a new phi-technology discussion page

2) send an e-mail to phi-technology-mailinglist to alert about the intention discuss about a new issue, reporting its URL in the body of the message

3) trak the discussion in the same wiki page

4) close the discussion with a CONCLUSION note

5) in case a discussion would open a change request in phi-Technoogy (MANTIS) let's report in the conclusion note the Mantis ticket number (its URL)

CONTRIBUTION TO PHI SOLUTIONS

If you implements in your PHI SOLUTION some interesting features that you'd like to see in one of the next release, you can ask an account to our MANTIS OPEN SOURCE project to upload:

- description

- code

- doubts

- how many customers are using it?

- what are future development

[DAVIDE MAGNI]

Software Development

Of coding conventions, versioning and release management .

Software License

Copyrights on phi-Technology belong to TBS Group ([2]).

Mail to phi.info@italtbs.com for further information.

phi-Technology software licensing is constrained by :

AGREEMENTS

* JavaSIG - HPL 1.0: Health Level-7 Public License for Java.
* RedHat Jboss - GNU Lesser General Public License.
* Apache - http://en.wikipedia.org/wiki/Apache_License 
* OHF Open Healthcare Framework - Eclipse Public License v1: http://www.eclipse.org/legal/epl-v10.html
* Designers - Eclipse Public License v1: http://www.eclipse.org/legal/epl-v10.html

POLICIES

* phi-Technology , as the package including PHI DESIGNER and PHI R.E., is distributed as an open source software, 
  free of charge for development.
* phi-Technology Support Services are granted only in case of subscription with fee.
* phi-Technology is not anymore free of charge when a phi-Solution is sold or used in production 
 (supporting end users in their business processes):
  - in case of sale of a phi-Solution, a royalty to TBS Group SpA has to be paid as a percentage of the sale price.
  - in case of use in production of a phi-Solution self-made by a organization or person, 
    the phi-Technology price has to be paid to TBS Group SpA.
Read further information in the phi-Technology License Agreement:
  C-EULA ==> Community Edition End User License Agreement
  E-EULA ==> Enterprise Edition End User License Agreement

phi-Technology release roadmap

The following section will show you the ROADMAP about phi-Technology development. The Roadmap is planned year-by-year and for each released you can find the detailed features added and bugs solved just clicking on the released link. Each release is delivered first as an EARLY RELEASE that is mainly an internal delivery that is tested before the GENERAL AVAILABILITY distribution.

2011

 Image:Releaseroadmap2011.png

PHI 1.6.5 ==> ver. 1.6 Plan & WBS:

  • RICH-FACES rebuilding
  • Performance improvement thanks to changing on configuration and layout v1
  • PHI-DESIGNER: catalog explorer search feature, automatic documentation from process v1

PHI 1.7 ==> ver. 1.7 Plan & WBS:

  • Performance improvement thanks to changing on configuration and layout v2
  • HISTORY RIM-DB thanks to ENVERS v1

PHI 1.7.1.GA ==> ver. 1.7 Plan & WBS:

  • Versioned Catalogs in Dictionary Manager
  • Versioned dictionary import/export

2012

PHI-TECHNOLOGY (DESIGNER and RE)

some feature are discussed here: PHI_2.0

The development go PHI 2.0 are based on the SURVEY RESULT where the red circle are the main point that was developed in the platform R-Evolution.

Image:ROADMAP20.gif

PHI 2.0.M1 Designer renewing

  • DESIGNER on Eclipse 3.7
  • DESIGNER Eclipse-Update-site
  • JBPM designer upgrade
  • Better integration with eclipse
  • PHI-Solution project incorporates: MIF, PROCESS, RULES, BACKEND
  • DEPLOY with ANT during development
  • Dictionary Manager on WEB and embeddable in a phi-solution

PHI 2.0.M2 Model renewing

  • RIM renewing

PHI 2.0.M3 Designer Wizard

  • PHI-TECH MAVEN management
  • Observation wizard improvement
  • New basic solution wizard

PHI 2.0.M4

  • PHI-RE UPGRADE JBoss

PHI-ESB

 Image:ROADMAP2012BIS.jpg

PHIESB 2.0 ==> download the PDF version :

  • SPRING 3.1 PHIESB-CONSOLE REWRITING
  • IHE PIX-PDQ PROFILE IMPLEMENTATION
  • PIX PDQ CONSOLE
  • QUEUE STATE MONITORING
  • ATNA ESB SERVICES
  • ATNA VIEWER INTEGRATED in PHIESB CONSOLE
  • PHIESB MIGRATION TO JBOSS SOA 5.2

PHIESB 2.1 :

  • CLUSTERED MESSAGE GROUPING AND ORDERING.

2013

PHI-TECHNOLOGY (DESIGNER and RE)

RoadMap for 2013 of phi Technology Designer and runtime consists in release 2.1, 2.2 and 2.3 as described in the picture below. Release 2.4 is planned but still not closed.

 Image:RoadmapDesignerRe_2013.png

PHI-ESB 2.2

 Image:ROADMAP2013.jpg

PHIESB 2.2 ==> download the PDF version :

PHIESB 2.2 M1

  • PHI MESSAGE upgrade to PHI 2.0 DataModel and features enhancement

PHIESB 2.2 M2

  • Obtaining Certification for IHE Profile (PIX/PDQ transaction and audit trail).

PHIESB 2.2 M3

  • Designer plugin to map from V2, V3, Customer Data (the model to import can be derived from xsd, xml, java class) to PHI 2.0 DATA MODEL.

PHIESB 2.2 M4

  • Notification services based on rule engine to recognized critical event (e.g: notify supervisor every time invalid codes are sent for prescription)
  • Porting of XDS.b profile to PHI 2.0 DataModel on SOA infrastructure compliant with IHE ATNA Requirement (this activity depends on customer new project).

PHIESB 2.2 M5 Following REDHAT innovation process with testing and release of frameworks (PHIESB and PHI) compliant to latest application server JBOSS 7.x (JBOSS 6 EAP) to achieve:

  • Lightweight deployment (given by new as deployment and compliance with OSGI specification);
  • Minimize server downtime for maintanance,
  • Improve automatic testing

PHIESB 2.2 M6

  • RESTEASY service development from designer (input class generation, mapping to PHI object management).
Personal tools