E-Priority Portal (PHP)

E-Priority
Version 1.0

Version Control Versio n 1.0 Date 25/03/2012 Comment/Changes Completed By Abdul Hakim Mohamad

Project Team Project Roles Business Owner Project Manager Functional Consultant Technical Consultant Signoff Name/Title Action Signatory Date Name/Department/Email E-Outsource Asia Lau Wee Boon Comment

Action Types: Approve, Review, Information, Action Required, Other (please specify)

Purpose of document

Table of Contents 1 2 3 4 5 6 7 8 9 Introduction ....................................................................................................... 4 SAP and PHP integration.................................................................................... 4 PHP Development, Staging, Production Environment. ........................................ 5 Bug fixed, new development guide. ...................................................................... 6 Releasing updated file to staging/production from development. .......................... 6 IP Configuration. ................................................................................................ 7 User (Testing). .................................................................................................... 7 Functions............................................................................................................ 7 File Upload ......................................................................................................... 7

Introduction

PHP is a two tier technology acts as a server side scripting language that will deal with the data before present it to user in the presentation layer (browser). Theoretically PHP can be used strictly as a presentation layer technology, but mostly it will be used for both presentation logic and business logic.

SAP and PHP integration.

To connect from PHP to SAP function module, it will need PHP SAPRFC extension developed by Eduard Koucky. Since SAP will deal all business logic from its function module, PHP will only be used for presentation layer. PHP will take data retrieved from SAP RFC enabled function module and display the data to the user. PHP also used to take data from presentation layer and send to SAPRFC to do business logic.

PHP Development, Staging, Production Environment.

In hosted software development, the environment refers to a server tier designated to a specific stage in a release process. The purpose of these environments is to improve the development, testing and release processes in client-server applications.

i)

Development

This is where the software is developed its the working environment for individual developers or small teams. The purpose of this environment is for the developer to work on local host, separate from the rest of the team, allowing them to make various changes without worrying that it may alter the work of the other members of the team. Before they start the development, they should copy the source code from Staging or QA server to their own PC/Laptop.

ii)

Staging (QA Test)

It is used to assemble, test and review the application before it goes into production. Usually the staging environment tries to simulate as much as possible the production environment (hardware and software-wise). Normally, before releasing an update version of the application on the production environment, the update must be tested on the staging environment. This environment can also be used as a demonstration/training environment.

iii) Productions It is the live environment, where the final application goes out to the world and becomes active.

To release updated or new source code to production environment, you may copy the new changes into the file directory where it should belong. The directory should be same as in development and QA environment. The updated file should only be released after all testing is done in staging. For more practical, you may use version control using Subversion(SVN). Read here for info on subversion. Productions Step

Production

Staging

Development (Local PC)

Development/Bug fixes Step 4 Bug fixed, new development guide.

Before started a new development or fixed existing file, developer should start by put a comment on top of the page. This is to makes sure the other developer to know the purpose of the file. If it's a bug fix, please put a data and reason for change in the comment section. The comment may looks like this: /* // // // // */ //------------------------------------------------------------------------------------------------Author : Developer Name Purpose : File Purpose. Date : Creation Date

Releasing updated file to staging/production from development.

Before releasing from development to staging or production, for all existing file should be saved before release new file into staging server. It was to makes sure the original version is will not overwrite by a new file. Existing file should be kept for backup if any of the new changes needs to roll back to the old version.

IP Configuration.

E-Priory can be access locally through this address 192.168.1.179. (Unifibiz) Type 192.168.1.179 to browser address, it will redirect to the system login page. Before you start using inside the browser, makes sure XAMPP is running inside server/laptop. To start XAMPP service, Please click at the XAMPP shortcut to xampp start at the desktop.

User (Testing).

i) Username : eoa Pass: initial1 - admin access ii) Username : suffian Pass : initial - customer access.

Functions

There is 5 functions inside the e-priority system. i) Change Password User can change his password by entering old password and new password. Password will hash inside SAP. ii) Create Ticket Create ticket by give all obligatory information; user will have to upload attachment later after ticket created. iii) Display Tickets User can display ticket by insert ticket number inside text field. iv) Change Ticket User can change the ticket information by entering ticket number in the text field. v) Ticket List See all Outstanding ticket or All the ticket in a time range.

File Upload

i) File can only be uploaded in change mode, this means ticket has to be created first. ii) Files can be seen inside server folder C:/xamp/htdocs/E-priority/ticket