The two major components in the FSV are the network component design and possible network component interactions, listed in sections 4.1 and 4.3. 4.1 Network Component Design A network component design specifies the network components necessary to execute the PIP and the network component collaboration. A network component design is comprised of Agent components and Business Service components that enable roles to perform business activities in a networked environment. Network components collaborate by exchanging business action messages and business signal messages. 4.1.1 Network Component Collaboration Figure 4.1 specifies the network components and their message exchange. Figure 4-1. Maintain Account 4.1.2 Network Component Specification Each network component maps onto a role in the BOV of the PIP model. Table 4.1 specifies the mapping between roles in the BOV and network components in the FSV. Table 4.1. Network Component SpecificationNetwork Component in FSV | Classification | Maps to Role in BOV |
---|
Account User Service | Business Service | Account User | Account User Agent | Agent | Account User | Account Supplier Service | Business Service | Account Supplier | Account Supplier Agent | Agent | Account Supplier | 4.2 Business Action and Business Signal Specification Each business action maps onto a business document in the BOV of the PIP model. Table 4.2 specifies the mapping between business documents in the BOV and business actions in the FSV. Table 4.2. Business Action Business Document MappingBusiness Action in FSV | Maps to Business Document in BOV |
---|
Account Change Request Action | Account ChangeRequest | Account Change Response Action | Account Change Response | 4.3 Business Transaction Dialog Specification Each business activity between roles in the BOV is specified as a business transaction dialog between network components. There are two fundamental network components modeled in the Functional Service View. Service network component. Implements protocols that include the service layer, transaction and action layer. A service has "network identity" as a business service. The service has an identity URI that can be registered in directories and used for component communication in a distributed computer system. Agent network component. Implements protocols that include the action layer and the agent layer. There is no service layer or transaction layer. The FSV allows the following network component interaction configurations. Agent-Service interaction configuration. An agent can request service from a service component and a service can respond to the request. Agents cannot respond to requests for service. Service-Service interaction configuration. There can be any number of services between end-point services, but no agents. Services both provide services to agents and other requesting services as well as request services for other services. Agent-Agent interaction configuration. One agent can transfer an action to another agent. From these three interaction configurations it is possible to derive three additional network-component configurations specific to a trading partner agreement. Service-Agent-Service interaction configuration. Services interact using two or more agents as a bridge. This configuration is typical in configurations where the two services do not know each other's identity, or when an employee must include additional private information to an action that is sent to another service. Service-Service-Agent interaction configuration. The second service acts as a mailbox for the agent. Agent-Service-Service interaction configuration. A service-to-service transaction is a sub-transaction of a larger agent-service transaction. The rest of section 4.3 specifies the network component configurations possible for this PIP. Each figure specifies the message exchange sequence as network components collaborate to execute this PIP. Each table shows the properties for each of the messages exchanged by the interactions in the corresponding figure. 4.3.1 Request Account Change Dialog: Service-Service The following figure specifies the message exchange sequence as network components collaboration to execute this PIP. Figure 4.2. Request Account Change Interactions: Service-Service The following table shows the properties for each of the messages exchanged by the interactions in the above figure. Table 4.3. Message Exchange Controls Request Quote# | Name | Time to Acknowledge Receipt Signal | Time to Acknowledge Acceptance | Time to Respond | Included in Time to Perform | Is Authorization Required? | Is Non-Repudiation Required? | Is Secure Transport Required? |
---|
1. | Account Change Request Action | 2 hrs | N/A | 24 hrs | Y | Y | Y | Y | 1.1. | Receipt Acknowledgment | N/A | N/A | N/A | Y | Y | Y | Y | 2. | Account Change Response Action | 2 hrs | N/A | N/A | Y | Y | Y | Y | 2.1. | Receipt Acknowledgment | N/A | N/A | N/A | N | Y | N | Y | 4.3.2 Request Account Change Dialog: Service-Agent-Service The following figure specifies the message exchange sequence as network components collaborate to execute this PIP. Figure 4.3. Request Account Change Interactions: Service-Agent-Service The following table shows the properties for each of the messages exchanged by the interactions in the above figure. Table 4.4. Message Exchange Controls Request Account Change# | Name | Time to Acknowledge Receipt Signal | Time to Acknowledge Acceptance | Time to Respond | Included in Time to Perform | Is Authorization Required? | Is Non-Repudiation Required? | Is Secure Transport Required? |
---|
1.1. | Account Change Request Action | 2 hrs | N/A | 24 hrs | Y | Y | Y | Y | 1.1.1. | Account Change Request Action | N/A | N/A | N/A | Y | N/A | N/A | Y | 1.1.1.1. | Account Change Request Action | N/A | N/A | N/A | Y | N/A | N/A | Y | 1.1.1.1.1 | Receipt Acknowledgment | N/A | N/A | N/A | Y | Y | Y | Y | 2. | Account Change Response Action | 2 hrs | N/A | N/A | Y | Y | Y | Y | 2.1. | Receipt Acknowledgment | N/A | N/A | N/A | N | Y | N | Y | 4.3.3 Request Account Change Dialog: Agent-Service-Service The following figure specifies the message exchange sequence as network components collaborate to execute this PIP. Figure 4.4. Request Account Change Interactions: Agent-Service-Service The following table shows the properties for each of the messages exchanged by the interactions in the above figure. Table 4.5. Message Exchange Controls Request Account Change# | Name | Time to Acknowledge Receipt Signal | Time to Acknowledge Acceptance Signal | Time to Respond | Included in Time to Perform | Is Authorization Required? | Is Non-Repudiation Required? | Is Secure Transport Required? |
---|
1.1. | Account Change Request Action | 2 hrs | N/A | 24 hrs | Y | Y | Y | Y | 1.1.1 | Receipt Acknowledgment | N/A | N/A | N/A | Y | Y | Y | Y | 2. | Account Change Response Action | 2 hrs | N/A | N/A | Y | Y | Y | Y | 2.1. | Receipt Acknowledgment | N/A | N/A | N/A | N | Y | N | Y | |