PeopleSoft Enterprise PeopleTools 8.4 to 8.49 Cumulative ... - Oracle

More documents

Recommendations

Info

PeopleSoft Enterprise PeopleTools 8.4 to 8.49 Cumulative Feature Overview January 2007 performance and message exchange, especially when you are working with large messages tha exceed one gigabyte. • Another performance enhancement is the ability to use multi-threading to send groups of messages in parallel. • WSDL generated from PeopleSoft messages and component interfaces will be compliant with the Web Services Interoperability Basic Profile 1.0 (WS-I) specification. In addition, SOAP messages exchanged at runtime will also be WS-I compliant. • PeopleSoft Integration Broker will provide web services security (WS-Security) that will: • Enable applications to construct secure SOAP message exchanges. • Associate security tokens with messages. • Third-party application developers will be able to programmatically access information about PeopleSoft web services through the web services introspection API. This API will allow two basic functions: • A call to get a list of all web services in the system. • A call to get the WSDL for a particular web service. • PeopleSoft Integration Broker will provide three connectors, for listening, response, and target, for use with Applicability Statement 2 (AS2) specification. You can use the AS2 listening and target connectors to transport any kind of data including, but not limited to, XML, EDI, text, and binary data. The AS2 response connector is used for handling Message Disposition Notifications (MDNs). • When external systems send inbound transactions consisting of flat files, you can use the Inbound File Loader utility to translate the incoming files into messages and process them. Release 8.47 • For Enterprise PeopleTools 8.47, we are continuing to focus on the interoperability between Enterprise Integration Broker and Oracle BPEL Process Manager, an effort carried forward from PeopleTools 8.46. • PeopleTools 8.47 supports using Oracle Application Server (OAS) as a Java Messaging Service (JMS) provider when using the JMS listening connector and the JMS target connector. • In Enterprise PeopleTools 8.47, if a JMS queue or JMS topic on which the JMS listening connector is listening becomes unavailable, the JMS listening connector will try to reestablish connection to that queue or topic. Release 8.48 • PeopleTools 8.48 features a services-oriented architecture for integrations. Users create services and service operations that contain message, routing information and processing logic. You create processing logic using application classes and then associate the logic to service operations using PeopleCode handlers. Users then use Copyright © 2006 Oracle. All rights reserved. 31
PeopleSoft Enterprise PeopleTools 8.4 to 8.49 Cumulative Feature Overview January 2007 wizard-driven pages for generating, providing and consuming WSDL with integration partners. • In this PeopleTools release, transaction IDs, which uniquely identify transactions, replace publication IDs (pub IDs) from previous PeopleTools 8.4x releases. • Beginning with this PeopleTools release you now create and manage messages and queues (formerly message channels) using a PeopleSoft page. • You can now create container messages and add one or more message parts to the container message. • Several enhancements were added to services security, including the addition of web service security (WS-Security) and a unique transaction ID in a web sercies addressing (WS-Addressing) SOAP header. • The Integration Metadata Backport utility enables you to backport a limited amount of PeopleTools 8.48 integration for use with prior PeopleTools 8.4x systems. • PeopleTools 8.48 supports integrations with BPEL process-based services. • PeopleTools 8.48 supports creating services from PeopleSoft component interface records and their corresponding methods. • The Node Definitions page features a new Default User ID field that is used web services security. If a web service request comes into the system without a user ID specified, the system checks the default user ID specified. If that user ID has clearance in the PeopleSoft system, then PeopleSoft honors the request. • The Node Definition page features a WSIL URL field used in conjunction with introspection and deployment validation on external nodes. • The IB Throttle Threshold field enables you to enter a value to limit the number of requests sent to the node per dispatch. • The Node Definitions page displays new External User ID and External Password fields when enabling WS-Security on external nodes. • When creating XSLT transformation programs you can launch the Oracle XSL Mapper from an XSLT step in an application engine transformation program. • PeopleSoft Integration Broker provides a DMS handler type that serves as a bulk loader to insert data. This handler is available when working with async one-way service operation types that contain rowset-based messages. • PeopleSoft Integration Broker supports the ability to create dedicated slave pub/sub servers called static slaves, where users can create domain(s) with nothing but dedicated slave pub/sub servers. • If an outbound synchronous request fails you can throw a framework exception leading to a message box error and subsequent component roll back of the transaction. • A new PSADMIN parameter, Load Balance Interval, enables you to resubmit failed transactions for processing. Copyright © 2006 Oracle. All rights reserved. 32
Page 1 and 2: PeopleSoft Enterprise PeopleTools 8
Page 3 and 4: Apache Software Foundation This pro
Page 5 and 6: THIS SOFTWARE IS PROVIDED BY THE CO
Page 35: PeopleSoft Enterprise PeopleTools 8

PeopleSoft Enterprise PeopleTools 8.4 to 8.49 Cumulative ... - Oracle

Create successful ePaper yourself

Delete template?

Save as template?