CN1598846B - The system and method for the assembly management reallocated resources - Google Patents
The system and method for the assembly management reallocated resources Download PDFInfo
- Publication number
- CN1598846B CN1598846B CN200410058964.8A CN200410058964A CN1598846B CN 1598846 B CN1598846 B CN 1598846B CN 200410058964 A CN200410058964 A CN 200410058964A CN 1598846 B CN1598846 B CN 1598846B
- Authority
- CN
- China
- Prior art keywords
- service
- action
- entity
- application
- metadata
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 230000000875 corresponding Effects 0.000 claims abstract description 16
- 230000001808 coupling Effects 0.000 claims description 8
- 238000010168 coupling process Methods 0.000 claims description 8
- 238000005859 coupling reaction Methods 0.000 claims description 8
- 239000000203 mixture Substances 0.000 claims description 8
- 230000002596 correlated Effects 0.000 claims description 5
- 238000007689 inspection Methods 0.000 claims 3
- 230000023298 conjugation with cellular fusion Effects 0.000 claims 2
- 230000013011 mating Effects 0.000 claims 2
- 230000021037 unidirectional conjugation Effects 0.000 claims 2
- 238000000034 method Methods 0.000 description 29
- 230000003068 static Effects 0.000 description 13
- 238000003860 storage Methods 0.000 description 5
- 238000004891 communication Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 241000699666 Mus <mouse, genus> Species 0.000 description 2
- 230000000712 assembly Effects 0.000 description 2
- 230000002093 peripheral Effects 0.000 description 2
- 230000001131 transforming Effects 0.000 description 2
- 239000009798 Shen-Fu Substances 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004040 coloring Methods 0.000 description 1
- 238000000151 deposition Methods 0.000 description 1
- 238000009795 derivation Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical Effects 0.000 description 1
- 230000000576 supplementary Effects 0.000 description 1
Images
Abstract
A kind of application entity can set up in the application by user and define.Can mate and merge by the related service entity of different attendant application management.Application entity can be associated to one or more relevant service entities.The metadata corresponding with the service entities being associated can be supplied to application program.These metadata can make the service entities being associated can be managed from application program.
Description
(1) technical field
The present invention relates to resource management field, particularly integrate the resource management between application service and application program.
(2) background technology
In traditional resource management system, application service is generally worked with application program one.In these application services
The different assemblies of each managed resource.Such as: two application services can manage the different assemblies of loan ratification process.
Specifically, the first application service can manage the credit history assembly of loan ratification process, and the second application program can manage
The down payment assembly of loan ratification process.First application service all can manage the relevant clothes being associated to ratification process of providing a loan
Entity.Such as: each application program can manage " applicant " service entities, and the second application service can manage relevant " borrowing
Money " service entities.
The application program that works with application service one is it may be that such as: enable the e-mail applications journey producing document
Sequence, word-processing application or spreadsheet applications.These documents can often be quoted service entities and affect in application
The management of the service entities of service center.Such as: document can include text, " John Smith does not pay credit card expense ".“John
Smith " can be the applicant's entity by the first application service management and the loan entity by the second application service management.Cause
This, document can affect application entity " John Smith " and loan entity " John Smith ".Specifically, document can affect use
The state of the application entity " John Smith " in the first application service is become " refusal loan " state by family.Document also can cause
Loan entity " John Smith " in the second application service becomes " returning down payment " state.
Although document can often affect the management of the service entities in application service, but access, inquire about and from application program
The ability of middle management service entities is typically limited.Such as: if documents affect user changes in the Shen of the first application service
Asking someone the state of entity " John Smith ", then change this state, user must access the first application service should first
The applicant's service entities is identified with service center.But it is the most highly difficult at application service identification service entities, because document leads to
The semanteme of the attribute of enough relevant definition service entities is not often provided.Such as: when document quotes loan application people by its full name
" John Smith ", the first application service can be with separate " name " and " surname " attribute definition the applicant's service entities.
Access from application program, inquire about and the limited capability of middle management service entities, should from difference at a documents affect
During with the management of related entities of service, become to bother very much.Such as: if the document causes user to change at the first application clothes
The state of applicant's entity " John Smith " of business also changes the loan entity " John Smith " in the second application service
State, then user must separately access each application service and identify each service entities in each application service respectively.Point
Open and identify that the service entities in different application service is the most troublesome, even if because different service entities is relevant, also
Service entities can be defined by different attribute group at each application service.Such as: can be with separate in the first application service
During " name " and " surname " attribute definition the applicant's service entities, the second application service can be with " applicant " attribute rather than use name
Attribute defines loan entity.
Application program is the commonly provided to manage relevant another difficulty is that with service entities in traditional resource management system
The information of the availability of the action performed on limited relevant service entities at application service.Specifically, each application
Service can have the specific rule relevant with the action executing to service entities and condition.Such as: these rule and conditions
The executable most number of times of action can be included, it is necessary to the time period of execution action, limited user or the user class of action can be performed,
Or the condition that must occur before or after action executing.What application program these rules the most uncertain and condition be,
And whether they meet.Therefore, user must access each component process to determine the most whether action can be used.
It is typically it addition, application program coordinates the ability of the management of resource between multiple users according to these rules and condition
Limited.Specifically, the execution of application tracks action and prevent or try to stop execution invalid action or easily produce conflict
The ability of action be limited.It addition, application program provides a user with about by the entity of different application Service Management and mistake
Journey, is typically limited with by other user to the ability of the information of relation between execution action in these related entities.This
A little information can be used for determining the availability of action and preventing the conflict relevant with action executing.
Therefore, this area needs to integrate the system and method for the resource management between application service and application program.Preferable
Be these system and methods enable, such as: mate from different application service related service entity, be associated with document
Service entities, and from application program, manage service entities.
(3) summary of the invention
The service metadata that application service maintenance is corresponding with service entities.This service metadata can be carried by application service
Supply context service and action service.The service entities that context service can be correlated with based on service metadata coupling.Context
The service entities that these are relevant can be merged into context entity by service.Context service can by with these related service entity phases
Corresponding service metadata is merged into context metadata.
The application metadata that application service maintenance is corresponding with application entity.Answer when selecting one in the application
When using entity, the application metadata corresponding with the application entity selected can be retrieved by the service that performs, and this is applied
Metadata is supplied to context service.
Context service can according to application metadata and text meta-data by the application entity of selection be associated
Context entity matches.The recognizable service entities therefrom deriving the context entity being associated of context service.Context
Entity can be to perform the service metadata that service provides corresponding with the service entities being associated.Execution service can generate and can be used for
The display of the service metadata that the service entities that at application program, management is associated is provided.
In one embodiment of the invention, the action that application service can perform on the service entities of application service
Availability classify.These actions can be divided into: can use optimistically, can use or commonly available according to rule.Can will divide
Class is supplied to action service, and action service this classification available determines the availability of the action on the service entities being associated.
Action service can include the follower of the execution of a tracking action.Action service may also include use from follow-up service
Data and combining classification determine the conflict the protection mechanism whether execution of action can lead to a conflict.Can will can be used for relevant
The action performed on the service entities of connection is supplied to application program, generates the view of this action on application program.
By below with reference to the accompanying drawing detailed description to exemplary embodiment, the advantage making the supplementary features of the present invention being become
Obtain clearly.
(4) accompanying drawing explanation
After Shenfu figure has read further detail below, it will be more fully understood that these exemplary embodiments.
Fig. 1 is the square frame representing the general-purpose computing system that can add various aspects of the invention and/or its each several part
Figure；
Fig. 2 is the block diagram of the resource management system of example prior art；
Fig. 3 a and 3b is the flow chart of example business process；
Fig. 4 illustrates an example document；
Fig. 5 is the block diagram of the example resources management system according to the present invention；
Fig. 6 illustrates the example application program user interface according to the present invention；
Fig. 7 a and 7b is for managing the flow chart of the exemplary method of service entities from application program according to the present invention；With
Fig. 8 illustrates the example application program user interface including actions available according to the present invention.
(5) detailed description of the invention
I example computer environment
Fig. 1 and following discussion aim to provide a suitable computers environment that can implement the present invention and/or its each several part
Brief description.Although not requiring, will at computer executable instructions (such as: performed by PC and/or computer installation
Program module) total background under present invention is described.Program module generally includes example and performs particular task or enforcement
The routine of particular abstract data type, program, object, assembly, data structure etc..In addition, it should be understood that other meter available
The present invention and/or its each several part are implemented in the configuration of calculation machine system, including: handheld devices, multicomputer system, based on microprocessor
Or programmable consumption electronic product, network PC, minicomputer, mainframe computer etc..The present invention can also be in distribution
Implementing in formula computer environment, wherein task is to be performed by by the remote processing device of communication network links.Distributed
Computer environment in, program module can be located at this locality and long-range storage arrangement.
As it is shown in figure 1, the general-purpose computing system of example includes conventional PC 120 etc., including: process
Unit 121, system storage 122 and the various system components including system storage are coupled to processing unit 121
System bus 123.System bus can be to include using in multiple bus structures any one system bus or memorizer control
Device processed, any one in interior several bus structures of local bus of peripheral bus sum.System storage includes read-only depositing
Reservoir (ROM) 124 and random access memory (RAM) 125.Including such as helping the unit in PC 120 during starting
The basic input/output 126 (BIOS) of the basic routine transmitting information between part is stored in ROM124.
PC 120 may also include for for reading (not shown), and the hard disk drive of write hard disk from hard disk
127, for reading and write the disc driver 128 of moveable magnetic disc 129 from moveable magnetic disc 129, for from such as CD-
The removable CD 131 of ROM or other optical medium etc reads and writes the CD drive 130 of removable CD 131.Hard disk
Driver 127, disc driver 128 and CD drive 130 are connect by hard disk drive interface 132, disc driver respectively
Mouth 133 and CD-ROM drive interface 134 are connected to system bus 123.These drivers and the computer being associated can
Read media and computer-readable instruction, data structure, program module and other data non-volatile for PC 120 are provided
Property memorizer.
Although example context described here uses disk or mobile disk 129 and removable CD 131, it should be understood that also
Can the other type of computer-readable media operating environment for example that can store the data that can be accessed by computer.This
A little other type of media include cartridge, flash card, digital video disc, Bernoulli cartridges, random access memory
(RAM), read only memory (ROM) etc..
A number of program module can be stored in hard disk, disk 129, CD 131, ROM124 or RAM125, journey
Sequence module includes: operating system 135, one or more application program 212, program 136, other program module 137 and program number
According to 138.User will be able to be ordered by the input equipment of such as keyboard 140 etc and the pointing device 142 of such as mouse etc
It is input to PC 120 with information.Other input equipment (not shown) comprises the steps that mike, stick, game mat, disk
Formula satellite antenna, scanner etc..These and other input equipment is generally by being coupled to the serial line interface 146 of system bus even
Receive processing unit 121 but it also may by such as: other of parallel interface, game interface or USB (universal serial bus) (USB) etc
Interface connects.Monitor 147 or other type of display device connect also by the interface of a such as video adapter etc
To system bus 123.In addition to the monitor 147, PC generally includes other of such as speaker and printer etc
Peripheral output devices (not shown).The example system of Fig. 1 also includes host adapter 155, small computer system interface
(SCSI) bus 156 and the external memory devices 162 that is connected with SCSI bus 156.
Computer 120 can be a remote computer logic used one or more such as remote computers 149
The networked environment connected operates.Although illustrate only storage arrangement 150 in Fig. 1, remote computer 149 can be another
Platform PC, application service, router, PC network, peer device or other common network node, and generally comprise many or
All above-mentioned elements relevant with PC 120.Logic shown in Fig. 1 connects and comprises LAN (LAN) 151 and wide area network
(WAN)152.These network environments are common in office, enterprise-wide net, Intranet and the Internet.
When for lan networking environment, PC 120 is connected to LAN by network interface or adapter 153
151.When for wan networking environment, PC 120 generally comprises modem 154 or in such as the Internet
Etc wide area network 152 on set up other device of communication.Modem 154 can be built-in or external, permissible
It is connected with system bus 123 by serial port interface 146.In networked environment, described above relevant to PC 120
Program module or one part can be stored in remote memory device.It is exemplary for will be understood that the network of diagram connects
, it is also possible to use other means setting up communication linkage between the computers.
Resource management's environment of II example
The traditional resource management system 200 of an example shown in Fig. 2.System 200 includes and answering in client computer 230
Application service 210a and 210b worked by program 232 1.Application service 210 generally manages resource, and application program 232 in
Now and exchange about the information of these resources.
Application service 210 can be such as: business (LOB) application service, database application service, network english teaching,
The application service of print application service and document application service etc.Specifically, application service 210a can be management loan
The LOB application service of the credit history assembly of ratification process, and application service 210b can be the pre-of management loan ratification process
Pay earnest money the LOB application service of assembly.
Fig. 3 a illustrates example credit history component process 300a managed by application service 210a.In state 302a, receive
One loan application.In state 304a, receive a credit history.In state 306a, determine whether credit history is satisfied with.If
Credit history is satisfied, then in state 308a, ratify this loan.If credit history is unsatisfied with, then in state 310a, refuse this loan
Money.
Fig. 3 b illustrates example down payment component process 300b managed by application service 210b.In state 302b, receive
One loan application.In state 304b, receive a down payment.In state 308a, determine whether loan goes through.If borrowed
Money goes through, then in state 308b, and the payment of request the first month.If loan is not approved for, then in state 310b, return prepayment
Deposit.
Application service 210 manages the service entities 215 being associated with component process 300.Application service 210a manages service
Entity 215a and 215a ', application service 210b manage service entities 215b and 215b '.Specifically, service entities 215a is permissible
Be associated " applicant " entity with credit history component process 300a, and service entities 215b can be and credit history group
" loan " entity 215b that part process 300b is associated.Service entities 215a ' and 215b ' can be to be respectively dedicated each assembly
Process 300a and the incoherent service entities of 300b.
Application service 210 can maintain the service metadata 205 corresponding to these service entities 215.Can be with such as
The language definition service metadata 205 of extensible markup language (XML) etc.Service metadata 205 can include service entities 215
Attribute, and also include the unique key of service entities 215.Applicant entity 215a's described below and loan entity 215b
Instance attribute:
<applicant>
<ID>1</ID>
<first name>John</first name>
<last name>Smith</last name>
</applicant>
<loan>
<ID>10</ID>
<applicant>
<name>John Smith</name>
<applicant>
</loan>
Service metadata 205 may additionally include operational action on service entities 215.These actions can be to disobey
Rely in the static action of process status of service entities 215 or depend on the dynamic action of process status of service entities 215.
Static action can be such as: watches and change the action of attribute of service entities 215, for along relation or expansion
Exhibition relation sees the action of relevant example, and for change process status always can action.Viewing and change belong to
Property metadata comprise the steps that such as, be given such as start one dialogue the mechanism representing view.
Metadata for dynamic action can include the method for changing process status, the process shape of these methods available
State function and relevant prevented process from using these sides with using these methods multiple or conflict by what same or different user were made
The restriction of method.
Service metadata 205 may also include the information about accessing service entities 215.These metadata comprise the steps that such as,
For specific user or user's group to an entity of service entities 215 or the access limitation of a class, static action or relation or
Limit.Need such as: the mandate of valid password or identifier etc obtains each this example to entity or class, static dynamic
Make or the access right of relation.
Service metadata 205 can also include the explanation obtaining the method for the information about entity instance.These metadata
The explanation obtaining the reality maybe method of possible relation between entity instance, view and static action can also be included.
Application service 210 is communicated with client computer 230 by network 220.Network 220 can be LAN (LAN) or wide area
Net (WAN), such as: the Internet.Client computer 230 can be the calculating device calculating device 120 etc of such as Fig. 1.Can be
It is equipped with a Web browser in client computer 230 or another front-end application obtains the access right to application service 210.
Application program 232 runs on a client, and can be such as: word processor, electrical form or e-mail system etc
Application program.Application program 232 can make document 234 can be established, present and exchange between users.
It is essential that in conventional system 200 as shown in Figure 2, it is real that user can not manage service from application program 232
Body 215.Therefore, in order to change the state of applicant service entities 215a, user must separately access application service 210a and
Application service 210a identifies applicant service entities 215a.It addition, for the state changing financial service entity 215b, user
Must separately access application service 210b and in application service 210b, identify applicant service entities 215b.
The example system of the III present invention and method
Not as the legacy system 200 of Fig. 2, the present invention enables users to set up and definition application entity.The present invention also makes to be correlated with
Service entities can be matched and merge.Each application entity can be associated to one or more relevant service entities.Permissible
The metadata corresponding with the service entities being associated is supplied to application program.This metadata enables and manages from application program
The service entities being associated.
Fig. 5 illustrates the example resources management system 500 according to the present invention.Application service 210 is general to context service 510
The service metadata 505 corresponding with service entities 215 with action service 520 announcement.Context service 510 is according to service unit number
According to 505, service entities 215 is merged into context entity 515.Service metadata 505 is also merged into literary composition by context service 510
This metadata 525.Action service 520 determines the dynamic action that can be used on service entities 215.Application program 532 maintains and answers
By the corresponding application metadata 545 of entity 535.
Service metadata 505 is disclosed to context service 510 by network 220 by application service 210.It is different from Fig. 2's
Traditional service metadata 205, can include can performing together with service entities 215 according to the service metadata 505 of the present invention
The classification of the availability of action.Specifically, the classification of motion can be become commonly available, can use or root optimistically by application service 210
Can use according to rule.
Commonly available action is the action always can being performed.These actions are not by any rule or the pact of condition
Bundle.
Optimistically can action be with specific rule and the condition action as condition.Such as: these rules can include
Most number of times that action can be performed, it is necessary to the time period of execution action, it is necessary to the user of execution action or class of subscriber, must
The condition that must occur before action executing, it is necessary to the condition occurred after action executing.Become optimistically may be used by the classification of motion
The institute likely rule and the condition that must are fulfilled for applicable rule with making application service 210 to not necessarily describe make action to use.
Only just can use when being consistent with ad hoc rule and condition according to the action that rule is available.The classification of motion is become according to rule
Then can use the availability that application service 210 can be made to negate action, unless met specific rule and condition.
Context service 510 can be such as Fig. 1 calculate device 120 etc calculate the application journey run on device
Sequence.Context service 510 can identify service entities 215 and phase available on service entities with Analysis Service metadata 510
Should static action.Context service 510 can pass through, such as: makees a dummy argument calling to application service 210, it is desirable to the clothes of identification
Entity.
Service entities 215 is merged into context entity 515 by context service 510.In order to merge service entities 215, on
Hereafter service and match to relevant service entities 215, and service entities 215 that these are relevant are merged into one single upper
Hereafter entity 515.Such as: context service 510 can mate relevant service entities 215a and 215b, and combines them into
Hereafter entity 515a.Context service 510 may further determine that service entities 210a ' and 210b ' is uncorrelated, and such that it is able to by each
Service entities 210a ' and 210b ' is merged into separate context entity 515b and 515c respectively.
The service entities 215 that context service 510 is correlated with according to service metadata 505 coupling.Specifically, context clothes
The be engaged in attribute of 510 cross reference service entities 215 identifies reality and potential relation.Context service 510 can be according to genus
These relations of term identification of property.Such as: context service 510 can be by application service entity 215a and financial service entity 215b
Match, because financial service entity 215b includes " applicant " attribute.Context service 510 is divisible and combination belongs to
Property.It addition, context service 510 can perform transformation to attribute.Such as: context service 510 can perform a transformation and make application
" name " and " surname " attribute of people service entities 215a matches with " name " attribute of financial service entity 215b.
In addition to service entities 215 is merged into context entity 515, context service 510 is by service metadata 505
It is merged into text meta-data 525.Specifically, in addition to merging the attribute of service entities 215, context service 510 also closes
And the dynamic action on service entities 215.Such as: context service 510 is divisible and combination can be used on service entities 215
Static action.It addition, the static action executing of service entities 215 can be changed by context service 510.
Context service 510 can also merge the service metadata 505 about accessing service entities 215.Such as: context
The particular category Internet access context entity 215a that service 510 can adhere to regulation user, but have no right access context entity
The text meta-data 525 of 215b.
Context service 510 can also merge about the reality between entity instance and these examples, view and static action
The derivation of border or possible relation.Context service 510 can also maintain and reproduce the information for service metadata 505.On
Hereafter service 510 can also prefetch service metadata 505 from application service 210, to increase the availability of service metadata 505.
Context service 510 also can store for when application service 210 off line (such as: when power is off) recover service metadata 505
Process.
Alternatively, action service 520 can inquire about the application service 210 of identification, to obtain the status information of entity.Then,
Action service 520 can retrieve the service metadata 505 corresponding with this entity, moves for the available of service entities 215 to determine
Make.
User can pass through, such as: keys in a name of this entity in the text of document 534, with appended mouse button
Dish highlights this name etc., and selects " definitions example " option to define the example of application entity 535 from the application menu.Connect
, user is permissible, such as: selects an application entity 535 from the list of predefined application entity 535, or sets up one " newly "
The example of application entity 535.If user selects predefined application entity 535, then can show this predefined application
The view of the attribute of entity 535, and user can be defined for the attribute of example.If user sets up a new application entity
535, then user can set up the attribute of one group of application entity 535, and the set of properties of this example of definable.
Once defining the example of application entity 535, it can be as by such as: the text of underscore and special colouring shows
Go out is linked in the text of document appearance.Then, user can be by fetching this reality of selection with this chain of additional click
Example.This example is selected to may result in the view of the attribute showing this example.
Now see Fig. 6, it is shown that the application program user interface 605 of example.User interface 605 can such as be attached to client
Show in the display device of the monitor on machine 230 etc.User interface 605 includes the document window 610 showing document 534.
Document 534 includes text, " John Smith does not pay credit card expense ".Shown in link 612, " John Smith " is defined as
One example of applicant's application entity 535.
Application program user interface 605 also includes application metadata window 620.Application metadata window 620
Can be opened by clickthrough 612.Entity window 620 shows application metadata 545a, and it includes that applicant applies reality
The attribute of body 535a.In the embodiment of alternative, application metadata 545a can occur in the dialog box of document 534.
The execution service 536 discussed in detail in application program 532 referring to Fig. 7 a and 7b.Generally, service 536 is performed
The application metadata 545 selected is provided to context service 510.Perform service 536 and also include state and for providing phase
The relational view mechanism 538 of the view of the service entities 215 closed.
Fig. 7 a and 7b illustrates according to the present invention for managing the exemplary method of service entities 215 from application program 532
Flow chart.The application entity 535 being typically chosen is associated with service entities 215, and for the service entities 215 that is associated
Service metadata 505 is provided to application program 532.The service metadata 505 provided makes service entities 215 energy being associated
Manage from application program 532.
In step 710, select application entity 535 at application program 532.Such as: can be by by additional mouse-click
Application program 532 selects applicant's application entity 535a.
In step 712, perform service 536 in client computer 230 from application program 532 retrieval and the application entity selected
535 corresponding application metadata 545.Such as: if selected for applicant's application entity 535a, then service 536 is performed
Corresponding application metadata 545a can be retrieved.In step 714, perform the application program unit number that service 536 will retrieve
Context service 510 is passed to according to 545a.
In step 716, context service 510 is by the application entity 535 selected and context entity 515 phase associated
Join.It is discussed in detail the coupling of entity above by reference to Fig. 5, and cross reference application metadata 545 and text element can be passed through
The entity attributes comprised in data 525 is to perform this coupling.Such as: context service 510 will be able to be applied for according to predicable
People's application entity 535a matches with context entity 515a.
In step 718, context service 510 identifies the clothes being associated therefrom deriving the context entity 515 being associated
Entity 215.Such as: context service 510 can recognize that context entity 515a enters from applicant service entities 215a and loan
Service entities 215b derives.
In step 720, context service 510 checks that text meta-data 525 can be used on, to determine, the service entities being associated
Static action on 215.Context service 510 can generate the chart of a service entities being associated 215, to those entities
Relation, and can be used on those entities and close the static action fastened.
In step 722, context service 510 query actions service 520, can be used on, to determine, the service entities being associated
Dynamic action on 215.Action service 520 can provide the action that can be used on service entities 215, and may result in appointing of conflict
What action.Action service 520 can also limit and be used for multiple times with one or more dynamic action from same process.
In step 724, context service 510 provides the action that can be used for performing service 536.Context service 510 also may be used
Other service metadata 505 for the service entities 215 being associated is provided.If limited the service entities 215 being associated
In one conduct interviews, then may require user provides and authorizes to receive for the metadata of this entity.Such as: may require
User's identifier or password enter system.
In step 726, perform service 536 generation and can be used on the display of the action on the service entities 215 being associated.Perform
Service 536 includes state and relational view mechanism 538, to provide the view of relation between related service entity 215.Can be to this
A little relations filter, only to provide the relation of those and the functional dependence determining the state protected that relates to conflict.State and pass
It is that view mechanism 512 can provide about acquirement, successful, failed state and the state change side for related service entity 215
The information of the current state of method.
See that Fig. 8, display 815 illustrate the action that can be used on the service entities 215 being associated.Display 815 is in application journey
Shown in sequence service action window 630.Display 815 includes illustrating the static state of service entities 215a and 215b that can be used for being associated
The first display part 815b with dynamic action.Display 815 also includes illustrating the availability about the action in application service 210
Information second display part 815b.Second display part 815b illustrates the relation between component process 300a and 300b, often
Individual component process 300a and the state of 300b, and respectively in each process 300a and 300b at applicant service entities 215a and
The availability of the action on financial service entity 215b.About the shape of pending action in success, failure and process 300a and 300b
The information of state can be passed through, such as: appended mouse-click shows that the process in 815 is shown.
Alternatively, actions available can as cascade menu arrange or as classification action and option display is set.
Furthermore it is possible to dialog box in document window 610 shows actions available.Perform service 536 may call upon dialogue and to
Give and presented mechanism by what context service 510 was specified.
In step 728, user can be from display 815 one action of request.This user can pass through, such as: uses appended Mus
Mark clicks this action to ask this action.If, such as: user selects " view properties " or " change attribute ", then be associated
The attribute of service entities 215a and 215b may be displayed in a new window in user interface 805 or dialog box.So
User just can see and change attribute.
In the embodiment of an alternative, perform service 536 and these actions can be shown to user, automatically perform
Actions available.
In step 730, the action of request is sent to the application service 210 being suitable for.If the action of request is static dynamic
Make, then can pass through the application service 210 that context service 510 transmits it to be suitable for.If the action of this request is the most dynamic
Make, then can service 520 application services 210 transmitting it to be suitable for by action.
In step 732, action can be performed in applicable application service 210.This action can be recorded by follower 522
Execution.
Although, the present invention is that the preferred embodiment combining each accompanying drawing is described, it should be understood that can be similar to other
Embodiment or described embodiment is modified and increase come on the basis of without departing from the present invention perform as the present invention
Function.Therefore, should not limit the invention to any single embodiment, and should according to the appended width understanding the present invention and
Scope.
Claims (16)
1. one kind can be used for, for display in the application, multiple actions that same context entity performs together so that from institute
The method stating the interior management of application program multiple related service entities at multiple application services, described context entity is from described
Multiple related service entities are derived, and described method includes:
Application entity is selected in described application program；
Multiple service entities at identification and the associated plurality of application service of selected application entity；
Action to being associated with the first and second service entities is classified, and first service entity and the first application service are correlated with
Connection, second service entity is associated with the second application service being different from described first application service, described first application service
First service entity there is the first metadata associated there, described first metadata includes described first service entity
Attribute and can be used for the action physically performed at described first service, the second service entity tool of described second application service
The second metadata associated there, described second metadata is had to include described second service entity attributes and can be used for
The action that described second service physically performs, described first service entity attributes is with described second service entity attributes not
With, the most each action is classified according to its availability；
Come described by described first service entity attributes and described second service entity attributes are carried out cross reference
First and second service entities carry out mating to identify actual and/or possible relation；
First and second service entities of coupling are merged into the context entity of single merging, and by described first and second
Metadata merges into list combination metadata also, and described single combination metadata also includes the context entity of described single merging
Attribute and can be used for the action physically performed at the context of described single merging；
The corresponding classification of the availability of the action of the first and second service entities based on each coupling, by merged
The inspection of group metadata determines whether an action is available in related service and physically performs；And
Actions available is shown in described application program.
2. the method for claim 1, it is characterised in that the described action to being associated with the first and second service entities
Carry out classification to include becoming can use optimistically by the classification of motion, wherein said the classification of motion is become action can be divided with including optimistically
Class becomes can use with rule for condition.
3. the method for claim 1, it is characterised in that the described action to being associated with the first and second service entities
Carry out classification to include becoming to can use according to rule by the classification of motion.
4. method as claimed in claim 3, it is characterised in that described being can use according to rule by classification of motion one-tenth includes action
It is categorized into and only can use when meeting rule.
5. the method for claim 1, it is characterised in that the described action to being associated with the first and second service entities
Carry out classification to include the classification of motion is become commonly available.
6. the method for claim 1, it is characterised in that by the inspection of the group metadata merged is determined
Whether individual action is available for being used in related service physically includes determining whether the execution of this action can cause conflict.
7. the method for claim 1, it is characterised in that also include application entity and described context entity phase
Join.
8. method as claimed in claim 7, it is characterised in that offer at application program is provided and is available in described application clothes
The view of the action that each described related service at business physically performs.
9. one kind is used for providing for application program can be used for the action that the first service at the first application service physically performs
Method, it is characterised in that described method includes:
Second service entity is matched with the context entity being associated derived from first service entity, first service entity
Being associated with the first application service, second service entity is relevant to the second application service being different from described first application service
Connection, the first service entity of described first application service has the first metadata associated there, described first metadata bag
Include described first service entity attributes and can be used for the action physically performed at described first service, described second application
The second service entity of service has the second metadata associated there, and described second metadata includes that described second service is real
The attribute of body and can be used for the action physically performed at described second service, described first service entity attributes is with described
Second service entity attributes is different, wherein mates described first and second service entities, described first service entity
Being the extensible markup language being associated with described first application service, described second service entity is and described second application clothes
The extensible markup language that business is associated, wherein said first application service is connected to described second application service by network,
By the cross reference of described first service entity attributes and described second service entity attributes is come described first He
Second service entity carries out mating to identify actual and/or possible relation, is carrying out described first and second service entities
After coupling, the first and second service entities of coupling are merged into the context entity of single merging, and by described first
Merging into list combination metadata also with the second metadata, described single combination metadata also includes the upper and lower of described single merging
Literary composition entity attributes and can be used for the action physically performed at the context of described single merging；
The context entity being associated described in identification is derived from described first service entity；
In response to the selection to described first service entity, on the basis of action being classified according to the availability of action,
By the inspection of the group metadata merged is determined whether an action can be used at described first application service
First service physically performs；And
If described action can be used, then described action is supplied to described application program.
10. method as claimed in claim 9, it is characterised in that include that the context entity being associated described in identifying is from the
Second service entity at one service entities and the second application service is derived, described first service entity and described second service
Entity is correlated with.
11. methods as claimed in claim 9, it is characterised in that include based on action be optimistically can classification, determine this
Whether action can physically perform by the first service at the first application service, described optimistically can classification be to be with rule
Condition can classification.
12. methods as claimed in claim 9, it is characterised in that include that based on action be the classification available according to rule, determine
Whether this action can physically perform by the first service at the first application service.
13. methods as claimed in claim 12, it is characterised in that include only can using when meeting rule based on action
Classification, determines whether this action can physically perform by the first service at the first application service.
14. methods as claimed in claim 9, it is characterised in that include that based on action be commonly available classification, determine that this moves
Make whether can physically to perform by the first service at the first application service.
15. methods as claimed in claim 9, it is characterised in that determine whether action can physically perform bag at first service
Include and determine whether described action can lead to a conflict in the execution physically of described first service.
16. methods as claimed in claim 9, it is characterised in that be additionally included at described application program and generate described action
View.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US10/648,506 US7730182B2 (en) | 2003-08-25 | 2003-08-25 | System and method for integrating management of components of a resource |
| US10/648,506 | 2003-08-25 | ||
| US10/648.506 | 2003-08-25 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1598846A CN1598846A (en) | 2005-03-23 |
| CN1598846B true CN1598846B (en) | 2016-12-14 |
Family
ID=
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5111391A (en) * | 1989-10-05 | 1992-05-05 | Mrs. Fields, Inc. | System and method for making staff schedules as a function of available resources as well as employee skill level, availability and priority |
| JP2002245152A (en) * | 2001-02-14 | 2002-08-30 | Fujitsu Ltd | Device, method and program for processing service intermediation |
| CN1419675A (en) * | 2000-03-22 | 2003-05-21 | 伟博麦德有限公司 | Method and system for top-down business process definition and execution |
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5111391A (en) * | 1989-10-05 | 1992-05-05 | Mrs. Fields, Inc. | System and method for making staff schedules as a function of available resources as well as employee skill level, availability and priority |
| CN1419675A (en) * | 2000-03-22 | 2003-05-21 | 伟博麦德有限公司 | Method and system for top-down business process definition and execution |
| JP2002245152A (en) * | 2001-02-14 | 2002-08-30 | Fujitsu Ltd | Device, method and program for processing service intermediation |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7730182B2 (en) | System and method for integrating management of components of a resource | |
| US7805400B2 (en) | Report generation using metadata | |
| US7949728B2 (en) | System, method, and computer program product for managing and analyzing intellectual property (IP) related transactions | |
| US20050203760A1 (en) | Project time and expense | |
| Kim et al. | A knowledge management perspective to evaluation of enterprise information portals | |
| EP1510918A2 (en) | System and method for integrating management of resources between application services and applications | |
| US20110112986A1 (en) | Generative Investment Method and System | |
| US20080140484A1 (en) | System and method for creating and managing intelligence events for organizations | |
| WO2003005232A2 (en) | A method and system for the visual presentation of data mining models | |
| WO2003003254A1 (en) | Simultaneous intellectual property search and valuation system and methodology (sips-vsm) | |
| AU2010201313A1 (en) | Improved philanthropy management system and method of doing business | |
| Matus et al. | Certification systems for machine learning: Lessons from sustainability | |
| US20120101869A1 (en) | Media management system | |
| Hunink et al. | Industry taxonomy engineering: the case of the european software ecosystem | |
| CN107679977A (en) | A kind of tax administration platform and implementation method based on semantic analysis | |
| Wang | Designing information systems for electronic commerce | |
| EP1975864A1 (en) | Resource exploitation supporting method, information processing device, and computer program | |
| JP4279316B2 (en) | Resource utilization support method, information processing device constituting network system for resource utilization support, computer program for resource utilization support | |
| JP2006195974A (en) | Platform managing display as target of advertisement in computer network | |
| Chen et al. | Ontology-supported web service composition: an approach to service-oriented knowledge management in corporate services | |
| CN1598846B (en) | The system and method for the assembly management reallocated resources | |
| Allen et al. | Modeling temporal dynamics for business systems | |
| Ackland et al. | Semantic service integration for water resource management | |
| Barzilai-Nahon et al. | Gatekeeping in networks: a meta-theoretical framework for exploring information control | |
| Igorevich et al. | Digital platforms: essence, classification, opportunities and problems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20150731 Address after: Washington State Applicant after: Micro soft technique license Co., Ltd Address before: Washington State Applicant before: Microsoft Corp. |
|
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20161214 Termination date: 20200723 |