0 Bewertungen0% fanden dieses Dokument nützlich (0 Abstimmungen)
36 Ansichten38 Seiten
Application development has four phases phase 1 - Planning Phase. Here you examine functional business requirements and convert them into technical requirements. Phase 2 - Data Design Phase. Here you develop the data structures starting from fields definition to record definition in Application Designer. Phase 3 - User Interface Design. In this phase you design the user facing elements of the application. Phase 4 - Testing Phase. In this phase you verify the navigation, security.
Application development has four phases phase 1 - Planning Phase. Here you examine functional business requirements and convert them into technical requirements. Phase 2 - Data Design Phase. Here you develop the data structures starting from fields definition to record definition in Application Designer. Phase 3 - User Interface Design. In this phase you design the user facing elements of the application. Phase 4 - Testing Phase. In this phase you verify the navigation, security.
Copyright:
Attribution Non-Commercial (BY-NC)
Verfügbare Formate
Als PDF, TXT herunterladen oder online auf Scribd lesen
Application development has four phases phase 1 - Planning Phase. Here you examine functional business requirements and convert them into technical requirements. Phase 2 - Data Design Phase. Here you develop the data structures starting from fields definition to record definition in Application Designer. Phase 3 - User Interface Design. In this phase you design the user facing elements of the application. Phase 4 - Testing Phase. In this phase you verify the navigation, security.
Copyright:
Attribution Non-Commercial (BY-NC)
Verfügbare Formate
Als PDF, TXT herunterladen oder online auf Scribd lesen
Architecture 2 Slide 2 SOA IT Introduction to PeopleSoft Internet Architecture Agenda On day one, we will discuss these topics: Technology Overview. Navigating PeopleSoft applications. Describing PeopleSoft Internet Architecture. Validating data. 3 Slide 3 SOA IT Introduction to PeopleSoft Internet Architecture Technology Overview We will talk about.. PeopleSoft application development methodology. PeopleSoft Application Designer. How to find information about the PeopleSoft Application Designer in PeopleBooks. 4 Slide 4 SOA IT Introduction to PeopleSoft Internet Architecture Application Development Methodology Application Development has four phases Phase 1 - Planning Phase. Here you examine functional business requirements and convert them into technical requirements. This may require assistance from functional users. Phase 2 - Data Design Phase. Here you develop the data structures starting from fields definition to record definition in Application Designer, the IDE tool for PeopleSoft development. This phase ends with the build of a database level table based on the record definition created. 5 Slide 5 SOA IT Introduction to PeopleSoft Internet Architecture Application Development has four phases Phase 3 - User Interface Design. In this phase you design the user facing elements of the application. First part is to design a page - a design element that gets loaded on the web browser at run time to display information and carryout transactions. Second part is to tie one or more pages logically into a single transaction element called component. This is followed by defining the navigation to this transaction that a user needs to follow and grant the security to required set of users. Phase 4 - Testing Phase. In this phase you verify the navigation, security. You test the transaction by entering data to ascertain that it works as intended. Application Development Methodology (contd) 6 Slide 6 SOA IT Introduction to PeopleSoft Internet Architecture PeopleSoft Application Designer PeopleSoft Application Designer is the IDE that is used to carryout most development tasks Creating all definitions used in a PeopleSoft environment. Creating PeopleCode programs. Creating Application Engine programs. Creating internet workflow. Integrating products. Development tasks that you do not perform in Application Designer include: Setting up definition security. Creating queries. Creating SQR programs. Modifying COBOL programs. Running PeopleSoft Data Mover scripts. 7 Slide 7 SOA IT Introduction to PeopleSoft Internet Architecture Finding information in PeopleBooks Use the PeopleTools 8.xx PeopleBook: PeopleSoft Application Designer to find development information including: Information for planning application development. Information for creating data structures. User Interface design and implementation. Appendixes. Some additional books that you will be referring are: PeopleTools 8.xx PeopleBook: PeopleSoft Application Designer PeopleTools 8.xx PeopleBook: Security Administration PeopleTools 8.xx PeopleBook: Internet Technology PeopleTools 8.xx PeopleBook: PeopleCode Developer's Guide You can also access related material by clicking the Help link. This automatically takes you to the relevant information in the appropriate PeopleBook. 8 Slide 8 SOA IT Introduction to PeopleSoft Internet Architecture PeopleSoft Navigation We will talk about.. How to navigate in PeopleSoft. How to use search pages. Identifying definitions. Entering and modifying data. 9 Slide 9 SOA IT Introduction to PeopleSoft Internet Architecture PeopleSoft Navigation Enter a valid URL, user ID and password to log in After signing in, user sees the home page which has three areas i) menu pagelet ii) header area and iii) Target Area One can use "Add to Favorites and "My Favorites to define and use navigational shortcuts. Another method of navigation is through the search feature on the homepage. To use the search feature: Type a word to search. Click the Search button. Click a link. The menu pagelet enables a user to navigate to applications. Folders define the hierarchy of the navigation. Triangular icons identify folders. Folders can contain other folders and content references. Click the triangular icon or the folder name to expand the folder. Content references are links to components in the database. Click the content reference to build the search page in the target area. 10 Slide 10 SOA IT Introduction to PeopleSoft Internet Architecture PeopleSoft Navigation - Search Pages Search Pages are an interim step between a content reference and its component. They are dynamically built based on several definition properties. There are two types of Search Pages - Basic & Advanced. You can click the Search button with no search parameters and the search returns all data rows to a maximum of 300. It may be case-sensitive. You can use wildcard characters. You enter search parameters in one search field. You cannot change the comparison operator in Basic Search Page. While you can select from multiple comparison operators on an Advanced Search Page. The search fields that appear on the page are determined in the record definition. They are called: Search keys. Alternate search keys. 11 Slide 11 SOA IT Introduction to PeopleSoft Internet Architecture PeopleSoft Navigation - Activity 1 Log in to the PeopleSoft Application Create some Favorites e.g. - Personal Information about employees Use the alternate method of Navigation using "Search to find the content reference link related to Personal Information about employees. Use Search Page to search for specific data row. 12 Slide 12 SOA IT Introduction to PeopleSoft Internet Architecture PeopleSoft Navigation - Identifying Definition The component definition is central to the user interface. Component definitions determine: The search page. The toolbar buttons at the bottom of the screen. The mode of the component: update/display, history, or correction. The pages that you access. Page tabs or links. The page defines what the user sees. Each component can hold multiple pages. Pages contain fields. Levels segment pages. All pages include a level zero, and many have other levels as well. Level zero contains the highest-level key values that make a row of data unique. Level zero key values are entered once, when a new row is created. A scroll area or a grid, if one exists, binds other levels. Pages can contain different field types represented by different controls -Edit boxes, Drop-down list boxes, Check boxes, Radio buttons, Images. Fields on a page hold data that you save to tables in the database. They can be interactive or display-only. From any component in the application, use CTRL + J to see an information page that includes the names of the component definitions that make up the interface. 13 Slide 13 SOA IT Introduction to PeopleSoft Internet Architecture PeopleSoft Navigation - Activity 2 Log in to the PeopleSoft Application Modify some Personal Information of an employee. Create a new employee record 14 Slide 14 SOA IT Introduction to PeopleSoft Internet Architecture Describing PeopleSoft Internet Architecture. We will talk about.. Structure of PeopleSoft databases. data transfer in PeopleSoft Internet Architecture. Identify requirements for the development environment. 15 Slide 15 SOA IT Introduction to PeopleSoft Internet Architecture Structure of PeopleSoft databases Tables in PeopleSoft databases fall into three general areas: System catalog tables contain database metadata. These tables: Track all objects in the entire database. Are analogous to a table of contents. Vary based on platform. PeopleTools tables contain metadata about the PeopleSoft application installed on the database. PeopleTools tables: Are structured consistently between applications. Vary in content between applications. Can be modified by PeopleTools such as PeopleSoft Application Designer. Are converted to HTML and delivered to a browser. Use the naming convention PS*; for example, PSPNLDEFN. Application data tables hold the data that users enter into the database. Specific tables are determined by the application. Developers can create more of these tables. Content is modified through the user interface. Tables use the naming convention PS_*; for example, PS_CUSTOMER_TBL. You can use a query tool to examine table contents, but do not change the contents outside of approved PeopleTools. PeopleTools tables and the application data table could become unsynchronized. 16 Slide 16 SOA IT Introduction to PeopleSoft Internet Architecture Structure of PeopleSoft databases - Activity 3 Log in to Application Designer. Open the record definition of PSRECDEFN. Query in backend query tool on PSRECDEFN - a PS tool table. Open Record definition "EMPLOYEE. Query in backend query tool on EMPLOYEE table. 17 Slide 17 SOA IT Introduction to PeopleSoft Internet Architecture Structure of PeopleSoft databases These tables store data that is directly pertinent to an individual company. The type of information stored in these tables includes ledger names, inventory items, employee names, and payroll data. Application data These tables record information about the definitions that make up a PeopleSoft application. The type of information stored in these tables includes page names, record names, and component names. PeopleTools These tables record information about the database and its contents. The type of information stored in these tables includes table names, column names, and index names. System catalog Description Table Type 18 Slide 18 SOA IT Introduction to PeopleSoft Internet Architecture Structure of PeopleSoft databases Some Tools Tables are: PSDBFIELD - used to create fields on a page in the user interface and columns in application data tables. PSRECDEFN - Values used to build application data tables, indexes, views, and some field attributes in the user interface. PSPNLDEFN - Values converted into HTML as pages viewed in browsers. PSPNLGRPDEFN - Definitions of components, which aggregate pages into groups and define the table to search when adding new values. PSPRSMDEFN - Contents of the portal registry, which builds the user navigation. PSXLATITEM Values used to validate data for specific fields. examples of application data tables: Human Capital Management - PS_JOB Financials - PS_LEDGER_TBL Contact Relationship Management - PS_PROD_COMPTTRS 19 Slide 19 SOA IT Introduction to PeopleSoft Internet Architecture PeopleSoft Internet Architecture The architecture of PeopleSoft Internet Architecture takes raw data from the application database and delivers it in the form of an interactive user interface on a standard web browser. Components of PeopleSoft Internet Architecture are: Browsers as clients - An application that provides a user a way to view and interact with information on the internet. Web servers - A server program that presents HTML files that form web pages of a PeopleSoft application. Application servers - A server program that provides the business logic for the PeopleSoft application. Database servers - A server program that collects and organizes information so that you can access and update it. 20 Slide 20 SOA IT Introduction to PeopleSoft Internet Architecture Activity 4 - Identifying Terms and Definitions Match 1) Application Designer ___ Data about data; describes the contents of the system catalog and PeopleTools tables. 2) BEA WebLogic ___ A program written in Java that resides on a web server. 3) Deferred Processing ___ An example of an application data table; can hold data about anything that the developer designs it to hold. 4) BEA Jolt ___ Software on an application server; manages multiple connections to a database. 5) Metadata ___ Software that resides on a web server and displays HTML for a browser. 6) PS_PNL_DEFS ___ Connection for a development workstation directly to the database. 7) PSPNLDEFN ___ A communication protocol; allows BEA Tuxedo to communicate with Java servlets. 8) Servlet ___ One of the web services programs supported in PeopleTools 8.4. 9) Three-Tier ___ An example of a PeopleTools table; holds definitions of pages that appear in a browser. 10) BEA Tuxedo ___ Connection for a development workstation to the database by way of an application server. 11) Two-Tier ___ A feature that prevents trips to the application server until all actions on a page have been saved. 12) Web Services ___ Tool used to create definitions stored in PeopleTools tables. 21 Slide 21 SOA IT Introduction to PeopleSoft Internet Architecture Flow of Data in PeopleSoft Internet Architecture When a user navigates through a PeopleSoft application using a browser, a number of things happen. A request for a page of data say about a student, goes through these architecture elements to the browser: PeopleTools tables - All the raw data required to assemble the student data component is contained in PeopleTools tables. This includes definitions of the component, page, fields, navigation, and other elements. This raw data goes to the application server for assembly as HTML. Application data tables - After the request is made, the information about Mark Larsen is retrieved and sent to the application server. PeopleSoft services - There are dozens of individual processes running. One (PSAPPSRV) takes the PeopleTools data and application data about Mark Larsen and assembles it into HTML for display. BEA Tuxedo and Jolt - BEA Tuxedo manages the multiple connections to the database. Jolt is a Java-based communication protocol. BEA Jolt and Tuxedo send the assembled HTML to the web server. Java servlets - Individual programs manage the state of each user session, including a buffer that allows the use of the browser Back button. Servlets pass the HTML to web services for display. 22 Slide 22 SOA IT Introduction to PeopleSoft Internet Architecture Identify requirements for the development environment. Developers need access to the entire PeopleSoft Internet Architecture setup to test their work, as shown below: 23 Slide 23 SOA IT Introduction to PeopleSoft Internet Architecture Validating Data We will cover the following. Describe prompt tables. Use effective dating. Compare validation types. Explain tableset sharing. 24 Slide 24 SOA IT Introduction to PeopleSoft Internet Architecture Prompt Tables In a prompt table edit, field values can be filled or edited only from a list of values in the prompt table. This diagram shows the prompt table PSU_INSTR_TBL providing a list of values for the Instructor field in the PSU_CRS_SESSN table. When you select from the search results, the key value from the prompt table is written to the field. If you enter an invalid value, the system warns you and does not allow a save. 25 Slide 25 SOA IT Introduction to PeopleSoft Internet Architecture Prompt Process Flow Lookup Page - When you click the prompt button, a lookup page displays. You may notice that this page, although called a lookup page, is almost identical to the search pages that you see when you select a content reference. The mechanism that creates the lookup is the same for creating a search page. How to Identify Prompts on the Screen - Fields that validate against prompt tables typically display a magnifying glass icon to the right of the field. Note. If you configure a field as prompt without edit, the system prompts against a table, but the displayed values are only suggestions. Users can enter any value. When you enter a new value in a prompt without edit field, it is stored only in the table that you are editing. The value is not added to the prompt table. Structurally, a prompt table is no different from any other application data table. It stores values that other tables can validate against. 26 Slide 26 SOA IT Introduction to PeopleSoft Internet Architecture Effective Dating Tables containing an effective date (EFFDT) field as a key are called effective-dated tables. Effective dating: Retains historical data. Stores data for future use. If Bryan Lake were promoted to senior clerk, would there be a record of his being a clerk? If the products price changes at midnight, you cant make this happen with the following table structure. 27 Slide 27 SOA IT Introduction to PeopleSoft Internet Architecture Effective Dating Effective-dated tables include three types of rows: Future Current History Future - The effective date is greater than the current system date. Current - The effective date is the closest to today, but is not in the future. History - The effective date is less than the current effective date. In other words History = EFFDT < Current Row Current = MAX (EFFDT) <= System Date (today) Future = EFFDT > System Date You will see some of these formulas in Query, PeopleCode, and SQL. 28 Slide 28 SOA IT Introduction to PeopleSoft Internet Architecture Effective Dating These altered table structures solve the challenges: To be effective dated, a table must include the field EFFDT as a descending order key. The application uses the date that is entered in this field to determine the current data row. Many effective-dated tables also include the field EFF_STATUS. This field reports whether the row of data is active (A) or inactive (I). 29 Slide 29 SOA IT Introduction to PeopleSoft Internet Architecture Effective Dating When entering rows into effective-dated tables, you have four action choices: Add Update/Display Include History Correct History As you do with any other table, you use Add to create a new search key value: Use Update/Display to edit data that is subordinate to an existing search key, including inserting rows, as shown in this table: In Update/Display mode, only the current and future rows are available to the user. You can update the future rows and you can insert any row with an EFFDT greater than the current row. Use Include History to view (but not change) historical data, as shown in this table: 30 Slide 30 SOA IT Introduction to PeopleSoft Internet Architecture Effective Dating Use Correct History to view and edit data regardless of effective date, as shown in this table: This table summarizes each action mode: 31 Slide 31 SOA IT Introduction to PeopleSoft Internet Architecture Effective Dating - Activity 5 Explore a table with Effective date logic and see how prompt works 32 Slide 32 SOA IT Introduction to PeopleSoft Internet Architecture Comparing Validation Types In addition to prompt tables, there are other types of validation: The translate table (PSXLATITEM) edit. The Yes/No edit. The 1/0 edit Fields that have translate values must: Be a Character data type. Have a length less than or equal to 4. Have fewer than 30 valid values. Be static data. Need only a long and short description. Translate Table Edit The translate table is a universal prompt table that many fields in an application share. The translate table is similar to a prompt table, but there are significant differences as well. The translate table is a specialized effective-dated prompt table that is keyed to specific field names. It has a fixed structure that you cannot customize. You use the translate table to quickly enter a list of values for the prompt on a specific field. Using the translate table is great if you need only a value and a short or long description. If you need other descriptive information, you should create a prompt table. Prompt tables can be built to any specification. 33 Slide 33 SOA IT Introduction to PeopleSoft Internet Architecture Comparing Validation Types Structure of the Translate Table FIELDNAME Name of the field definition that uses these values for a prompt. FIELDVALUE Values stored in the prompting table. This is a character field with a length of 4 or less. EFFDT Effective date for the row. As with any effective-dated table, multiple dates can be entered for any value. EFF_STATUS Effective status; either A (Active) or I (Inactive). XLATLONGNAME Long version of the name that appears to the user in a prompt. XLATSHORTNAME Short version of the name that appears to the user in a prompt. The Yes/No Edit The translate table stores a special set of values for binary switches, which you set by using the Yes/No table edit: Yes/No -- On/Off -- Selected/Clear The Yes/No table is a subset of translate table values, but it is set up differently during development. The field name is PSYESNO, and values are either Y or N. The default is a Y as the value when selected and an N for the value when cleared. The developer, as required, can reverse the behavior. The default page control of a Yes/No prompt on the browser is a check box. The advantage of this type of edit is that you have a way of having two valid values for many fields without having to have two translate values for each field. The 1/0 Edit If you validate a number field, the Yes/No edit will appear as a 1/0 edit. Being able to multiply by 1 or 0 makes this option more versatile if used in SQL, SQR, or PeopleCode. 34 Slide 34 SOA IT Introduction to PeopleSoft Internet Architecture Comparing Validation Types Prompt and translate tables provide values for the users to select. However, the fields they represent differ visually. This is a summary of prompt and translate table characteristics: 35 Slide 35 SOA IT Introduction to PeopleSoft Internet Architecture Table Set Sharing Use tableset sharing to filter prompt table choices based on business rules. In PeopleSoft applications, a large percentage of the tables are keyed with one of two fields: - Business Unit - Business Unit is the key field for transaction tables. - SetID - SetID is the key field for control tables. In HCM applications, you will find these fields in many tables. However it is very extensively used in Financials Application. Many PeopleSoft applications include prebuilt tableset sharing that filters results by product line, department, reporting structure, region, and other organizational lines. This diagram shows prompt values that have been limited by location: 36 Slide 36 SOA IT Introduction to PeopleSoft Internet Architecture Determining Validation Strategies - Activity 6 In this activity, you will view a data model. Use the diagram to decide what types of validation are appropriate for this application 37 Slide 37 SOA IT Introduction to PeopleSoft Internet Architecture Determining Validation Strategies - Activity 6 Explaining Prompt Table Edits In PSU_INSTR_TBL, the INSTRUCTOR field serves as a prompt for INSTRUCTOR edit box in both the T1_COURSE_TBL and T1_CRS_SESSN prompt tables. In PSU_TRNLOC_TBL, the TRAINING_LOC field prompts to the TRAINING_LOC field in the T1_CRS_SESSN table. In T1_COURSE_TBL, the COURSE field prompts to COURSE in both the T1_CRS_MATRL and T1_CRS_SESSN prompt tables. Explaining Effective-Dated Tables T1_COURSE_TBL. PSU_INSTR_TBL PSU_TRNLOC_TBL Because the PSU_INSTR_TBL table is effective dated and serves as a prompt table, only current, active instructors will be available when users prompt for a list of instructors from either the T1_COURSE_TBL or PSU_CRS_SESSN table. Explaining Translate Tables Fields that prompt against the translate table should have a limited number of options that are not likely to change over time. There are many candidates here, including: - PSU_MATRL_TBL.PSU_COLOR - T1_COURSE_TBL.COURSE_TYPE - T1_CRS_SESSN.CLASSROOM 38 Slide 38 SOA IT Introduction to PeopleSoft Internet Architecture Determining Validation Strategies - Activity 6 Explaining Yes/No Edits T1_COURSE_TBL.ONSITE (Is the course offered on-site?) PSU_INSTR_TBL.CURR_DEV_FLAG (Is the instructor also a curriculum developer?) Tableset Sharing The Course Session table (T1_CRS_SESSN) includes the BUSINESS_UNIT field, which makes it a transaction table. The control table is PSU_TRNLOC_TBL (keyed by SetID). When a user sets up a course session, only locations that are within the business units region will be available at the prompt. The Instructor table (PSU_INSTR_TBL) is also a transaction table. The instructors home facility is limited to those in the business units region (using the same rules as the Course Session table).