WO2022181122A1 - 運用支援装置、システム及び方法並びにコンピュータ可読媒体 - Google Patents
運用支援装置、システム及び方法並びにコンピュータ可読媒体 Download PDFInfo
- Publication number
- WO2022181122A1 WO2022181122A1 PCT/JP2022/001645 JP2022001645W WO2022181122A1 WO 2022181122 A1 WO2022181122 A1 WO 2022181122A1 JP 2022001645 W JP2022001645 W JP 2022001645W WO 2022181122 A1 WO2022181122 A1 WO 2022181122A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- screen
- data
- definition
- information
- display
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 107
- 238000012545 processing Methods 0.000 claims abstract description 196
- 230000004044 response Effects 0.000 claims description 26
- 239000000470 constituent Substances 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 24
- 238000004891 communication Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 8
- 230000010365 information processing Effects 0.000 description 7
- 238000004590 computer program Methods 0.000 description 5
- 238000012806 monitoring device Methods 0.000 description 5
- 238000004458 analytical method Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 238000012800 visualization Methods 0.000 description 2
- 230000001174 ascending effect Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units
- G06F3/147—Digital output to display device ; Cooperation and interconnection of the display device with other functional units using display panels
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/26—Visual data mining; Browsing structured data
Definitions
- the present invention relates to an operation support device, system, method and program, and more particularly to an operation support device, system, method and program for supporting the operation of information systems.
- Patent Literature 1 discloses a technique related to a data analysis processing device.
- Patent Literature 2 discloses a technology related to a method for jointly creating a visualization dashboard.
- the present disclosure has been made to solve such problems, and is intended to support the operation of information systems by flexibly and easily performing connection settings for various databases and screen display control.
- An object is to provide an operation support device, system, method, and program.
- the operation support device includes: A registration unit that registers data source definitions including connection methods, connection destination information and data attributes for accessing databases managed by external systems, and screen definitions including data attributes to be processed and display formats of target data.
- a registration unit that registers data source definitions including connection methods, connection destination information and data attributes for accessing databases managed by external systems, and screen definitions including data attributes to be processed and display formats of target data.
- An operation support system includes: a database managed by an external system; an operation support device communicably connected to the external system; with The operation support device is a registration unit for registering a data source definition including a connection method for accessing the database, connection destination information and data attributes, and a screen definition including a data attribute to be processed and a display format of the target data; an identification unit that identifies a screen definition specified in a screen display request received from a request source and identifies a data source definition corresponding to a data attribute included in the identified screen definition; a selection unit that selects a connection processing means corresponding to the connection method included in the identified data source definition; a data acquisition unit that acquires target data from the database based on connection destination information and data attributes included in the specified data source definition using the selected connection processing means; a generation unit that generates display screen information including the display format included in the identified screen definition and the acquired target data; an output unit that outputs the generated display screen information to the request source; Prepare.
- An operation support method includes: Register the data source definition including the connection method, connection destination information and data attribute for accessing the database managed by the external system, and the screen definition including the data attribute to be processed and the display format of the target data, Identify the screen definition specified in the screen display request received from the requester, identify the data source definition corresponding to the data attribute included in the identified screen definition, selecting a connection processing means corresponding to the connection method included in the identified data source definition; Acquiring target data from the database based on connection destination information and data attributes included in the specified data source definition using the selected connection processing means; generating display screen information including the display format included in the identified screen definition and the acquired target data; The generated display screen information is output to the request source.
- the operation support program is Registration process to register data source definition including connection method, connection destination information and data attribute for accessing database managed by external system, and screen definition including data attribute to be processed and display format of target data
- identification processing of identifying a screen definition specified in a screen display request received from a requester and identifying a data source definition corresponding to a data attribute included in the identified screen definition a selection process of selecting a connection processing means corresponding to the connection method included in the identified data source definition; data acquisition processing of acquiring target data from the database based on connection destination information and data attributes included in the specified data source definition using the selected connection processing means; a generation process of generating display screen information including the display format included in the identified screen definition and the acquired target data; an output process of outputting the generated display screen information to the request source; run on the computer.
- an operation support device, system, method, and program for supporting the operation of an information system by flexibly and easily performing connection settings for various databases and screen display control.
- FIG. 1 is a block diagram showing the configuration of an operation support device according to the first embodiment;
- FIG. 4 is a flow chart showing the flow of an operation support method according to the first embodiment;
- FIG. 11 is a block diagram showing the overall configuration of an operation support system according to a second embodiment;
- FIG. FIG. 11 is a block diagram showing the configuration of an operation support device according to the second embodiment;
- FIG. FIG. 11 is a diagram showing a configuration example of a data source definition according to the second embodiment;
- FIG. FIG. 11 is a diagram showing a configuration example of screen definition according to the second embodiment;
- FIG. 11 is a diagram showing an example of a data source definition registration screen according to the second embodiment;
- FIG. 11 is a flow chart showing the flow of data source definition registration processing according to the second embodiment;
- FIG. 11 is a diagram showing an example of a screen definition registration screen according to the second embodiment; 10 is a flow chart showing the flow of screen definition registration processing according to the second embodiment. 9 is a flowchart showing the flow of screen display processing according to the second embodiment; FIG. 11 is a diagram showing an example of a display screen according to the second embodiment; FIG. FIG. 11 is a block diagram showing the overall configuration of an operation support system according to a third embodiment; FIG. FIG. 11 is a diagram showing an example of a display screen according to the third embodiment; FIG. FIG. 16 is a diagram showing a configuration example of screen definition information according to the fourth embodiment; FIG. 13 is a diagram showing an example of a display screen according to the fourth embodiment; FIG.
- FIG. 1 is a block diagram showing the configuration of an operation support device 1 according to the first embodiment.
- the operation support device 1 is an information processing device for supporting the operation of an information system (external system).
- the operation support device 1 is connected to external systems and operation terminals via a communication network (not shown; hereinafter, the communication network will also be simply referred to as a network).
- the external system manages the database and may be the database system itself or may have an access interface between the outside and the database.
- the operation terminal is an information processing device operated by an operation user to manage an external system via the operation support device 1 .
- the operation terminal may be a management terminal operated by an administrator of the external system.
- the operation support device 1 includes a registration unit 11 , a specification unit 12 , a selection unit 13 , a data acquisition unit 14 , a generation unit 15 and an output unit 16 .
- the registration unit 11 registers data source definitions and screen definitions.
- a data source definition is information including a connection method, connection destination information, and data attributes for accessing a database managed by an external system.
- the screen definition is information including the attributes of data to be processed and the display format of the target data.
- the specifying unit 12 specifies the screen definition specified in the screen display request received from the request source.
- the identifying unit 12 also identifies a data source definition corresponding to the data attribute included in the identified screen definition.
- the selection unit 13 selects connection processing means corresponding to the connection method included in the specified data source definition.
- the connection processing means is a plurality of software modules or hardware interface circuits that exist for each connection method.
- the connection processing means performs connection processing with the database for the external system based on the connection destination information and the data attribute.
- the connection processing means transmits a data acquisition request to the external system based on the connection destination information and the data attribute.
- the data acquisition unit 14 uses the selected connection processing means to acquire target data from the database based on the connection destination information and data attributes included in the specified data source definition.
- the generation unit 15 generates display screen information including the display format included in the identified screen definition and the acquired target data.
- the display screen information may be a display screen on which the acquired target data is displayed according to the display format included in the specified screen definition.
- the display screen information may be screen generation control information for causing the request source to generate a display screen for displaying the acquired target data according to the display format.
- the output unit 16 outputs the generated display screen information to the request source.
- FIG. 2 is a flow chart showing the flow of the operation support method according to the first embodiment.
- the registration unit 11 registers a data source definition and a screen definition (S11). For example, the registration unit 11 receives a data source definition and a screen definition as input information from the management terminal. Then, the registration unit 11 registers the received input information in an internal or external storage device. Note that the registration unit 11 may receive input information through an input device (not shown) connected to the operation support device 1 according to the input operation of the administrative user.
- the specifying unit 12 receives a screen display request from the request source.
- the request source is, for example, an operation terminal or an operation system (not shown). It is assumed that information specifying the screen definition is specified in the screen display request.
- the specifying unit 12 then specifies the screen definition specified in the screen display request received from the request source (S12).
- the specifying unit 12 specifies a data source definition corresponding to the data attribute included in the screen definition specified in step S12 (S13).
- the specifying unit 12 specifies a data source definition corresponding to the designated screen definition and data attribute from among the plurality of data source definitions and screen definitions registered in step S11.
- the selection unit 13 selects connection processing means corresponding to the connection method included in the data source definition identified in step S13 (S14).
- each of the plurality of connection processing means is stored in a storage device (not shown) inside or outside the operation support device 1 .
- the selection unit 13 selects the connection processing means corresponding to the connection method included in the identified data source definition from the storage device.
- the data acquisition unit 14 acquires target data from the database of the external system based on the connection destination information and data attributes included in the specified data source definition ( S15).
- the generation unit 15 generates display screen information including the display format included in the screen definition specified in step S12 and the target data acquired in step S15 (S16).
- the output unit 16 outputs the display screen information generated in step S16 to the request source (S17).
- the requester causes the display device to display the display screen based on the display screen information received from the operation support device 1 .
- the display screen information is a display screen
- the generation unit 15 generates a display screen (for example, Generate DOM (Document Object Model).
- the output unit 16 outputs the display screen generated in step S16 to the request source.
- the requesting operation terminal displays the display screen according to the received DOM.
- the display screen information may be screen generation control information (for example, information in JSON (JavaScript (registered trademark) Object Notation) format).
- step S16 the generation unit 15 generates screen generation control information for causing the request source to generate a display screen in which the target data acquired in step S15 is displayed in accordance with the display format included in the screen definition specified in step S12. Generate.
- step S17 the output unit 16 outputs the screen generation control information generated in step S16 to the request source.
- the requesting operation terminal generates and displays a display screen based on the received screen generation control information. Therefore, the operating user can confirm, through the display screen, the contents of the data corresponding to the data attributes set in the data source definition and the screen definition among the data in the database of the external system to be operated. In addition, the operational user can check the data corresponding to the data attribute through the display screen, arranged according to the display format defined by the screen definition.
- the data source definition settings according to the connection method that the external system or database supports as an external interface
- it is possible to connect to the database without modifying the system for various external systems. access can be realized.
- the display format settings according to the operational user's needs in the screen definition
- the data content can be visually recognized in a flexible layout without depending on an external system. For example, it can be displayed in a display format different from the display screen of the database provided by the external system. Alternatively, even if the external system does not have a display interface, it is possible to easily generate a display screen of the data content of the database.
- the operation support device 1 includes a processor, memory, and storage device as configurations not shown. Further, the storage device stores a computer program in which processing of the operation support method according to the present embodiment is implemented. Then, the processor loads the computer program from the storage device into the memory and executes the computer program. Thereby, the processor realizes the functions of the registration unit 11 , the identification unit 12 , the selection unit 13 , the data acquisition unit 14 , the generation unit 15 and the output unit 16 .
- the registration unit 11, the identification unit 12, the selection unit 13, the data acquisition unit 14, the generation unit 15, and the output unit 16 may each be realized by dedicated hardware.
- part or all of each component of each device may be implemented by general-purpose or dedicated circuitry, processors, etc., or combinations thereof. These may be composed of a single chip, or may be composed of multiple chips connected via a bus. A part or all of each component of each device may be implemented by a combination of the above-described circuits and the like and programs.
- a processor a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an FPGA (field-programmable gate array), a quantum processor (quantum computer control chip), or the like can be used.
- each component of the operation support device 1 when part or all of each component of the operation support device 1 is realized by a plurality of information processing devices, circuits, etc., the plurality of information processing devices, circuits, etc. may be centrally arranged, They may be distributed.
- the information processing device, circuits, and the like may be implemented as a form in which each is connected via a communication network, such as a client-server system, a cloud computing system, or the like.
- the functions of the operation support device 1 may be provided in a SaaS (Software as a Service) format.
- FIG. 3 is a block diagram showing the overall configuration of the operation support system 1000 according to the second embodiment.
- the operation support system 1000 is an information system for supporting the operation of the plurality of external systems 210 and 220 operated by the operation user U2.
- the operation support system 1000 includes a management terminal 110 , an operation terminal 120 , an external system 210 , an external system 220 and an operation support device 300 .
- the management terminal 110, the operation terminal 120, the external system 210, the external system 220, and the operation support device 300 are connected via a network N, respectively.
- the network N is a wired or wireless communication line such as the Internet.
- the administrative user U1 and operational user U2 are users who manage and operate information systems such as the external system 210 and the external system 220 .
- the administrative user U1 and the operational user U2 use the operation support device 300, for example, to analyze data in the database 211 and the database 222.
- the administrative user U1 inputs the data source definition of the data to be analyzed and the screen definition for displaying the data to be analyzed to the management terminal 110 and registers them in the operation support device 300 .
- the operational user U2 performs an operation on the operational terminal 120 to display a display screen for displaying data to be analyzed. Note that the administrative user U1 and the operational user U2 may be the same person.
- the management terminal 110 is an information terminal operated by the management user U1.
- the operational terminal 120 is an information terminal operated by the operational user U2.
- the management terminal 110 and the operation terminal 120 are information processing devices such as personal computers and portable information terminals. Also, the management terminal 110 and the operation terminal 120 may be the same terminal.
- the management terminal 110 transmits a registration request for the data source definition and screen definition input by the management user U1 to the operation support device 300 via the network N.
- the management terminal 110 may use a setting tool (not shown) in the operation support system 1000 to generate a data source definition and screen definition registration request.
- the setting tool generates an SQL (Structured Query Language) statement for inserting a record corresponding to the data source definition and the screen definition into a predetermined table of the database inside the operation support device 300, which will be described later, as a registration request. There may be.
- the management terminal 110 performs registration by executing the SQL statement generated by the setting tool to the database of the operation support device 300 via the network N.
- the management terminal 110 may input the data source definition and the screen definition to the registration screen provided by the operation support device 300 and request registration of the input contents.
- the operation terminal 120 transmits a screen display request for displaying analysis results and the like to the operation support device 300 via the network N in response to an operation by the operation user U2.
- the screen display request is access destination information including a screen definition ID, which will be described later, for displaying a display screen.
- the access destination information may be, for example, a URL (Uniform Resource Locator).
- the URL may specify the screen definition ID in addition to the host name of the operation support device 300 and the like.
- the operation terminal 120 receives the display screen data as a response to the screen display request from the operation support device 300 via the network N, and displays the display screen data on the display device.
- the operation terminal 120 receives screen generation control information (for example, information in JSON format) as a response to the screen display request from the operation support device 300 via the network N, and generates display screen data based on the screen generation control information. is generated and displayed on the display device.
- screen generation control information for example, information in JSON format
- the external system 210 is at least part of the information system operated by the operating user U2.
- An external system 210 manages a database 211 .
- External system 210 may be a database system.
- the external system 210 connects to the database 211 via the network N using a JDBC (Java (registered trademark) Database Connectivity) connection, for example, in response to a connection request from the operation support device 300 . After the connection, the external system 210 enables the operation support device 300 to access the database 211 .
- JDBC Java (registered trademark) Database Connectivity
- the external system 220 is at least part of the information system operated by the operating user U2.
- External system 220 manages database 222 .
- the external system 220 also includes a web application server 221 connected to a database 222 .
- the WEB application server 221 accesses (processes) the database 222 in response to an access request from the outside via the network N, for example, using a Web API (Application Programming Interface), and requests processing results (search results, etc.). Reply to original.
- REST Representational State Transfer
- connection method may be used as the Web API (connection method).
- the operation support device 300 is an example of the operation support device 1 described above.
- the operation support device 300 is an information processing device that registers a data source definition and a screen definition, and generates and returns display screen information in response to a screen display request in which the screen definition is specified.
- the operation support device 300 may be made redundant by a plurality of servers, and each functional block may be realized by a plurality of computers.
- FIG. 4 is a block diagram showing the configuration of the operation support device 300 according to the second embodiment.
- the operation support device 300 includes a storage unit 310 , a memory 320 , a communication unit 330 and a control unit 340 .
- the storage unit 310 is an example of a storage device such as a hard disk or flash memory.
- the storage unit 310 stores a program 311 , a DB connection processing module 312 , a WEB connection processing module 313 , a data source definition 314 , a screen definition 315 and a screen template 316 .
- a program 311 is a computer program in which processing of the operation support method according to the second embodiment is implemented. Note that the program 311 may include the function of the setting tool described above.
- the DB connection processing module 312 is a program module whose connection method corresponds to database connection (DB connection) (first connection method) and performs connection processing with the database.
- the DB connection processing module 312 is, for example, a class, a library function, etc. for making a JDBC connection.
- the WEB connection processing module 313 is a program module that supports a WEB connection (second connection method) as a connection method and connects to and accesses a database via the WEB.
- the WEB connection processing module 313 is, for example, a class, a library function, or the like for HTTP (Hypertext Transfer Protocol) access corresponding to REST connection.
- the DB connection processing module 312 and the WEB connection processing module 313 may be included in the program 311.
- the data source definition 314 is information that defines information including information specifying databases and tables that manage data to be processed, connection methods for accessing databases, connection destination information, and data attributes. Data attributes may also include processing logic.
- FIG. 5 is a diagram showing a configuration example of the data source definition 314 according to the second embodiment.
- the data source definition 314 includes data source definition information 4110 to 41m0, data attribute information 4210 to 42n0, and source attribute association definitions 4310 to 43m0.
- m and n are two or more natural numbers.
- the data source definition information 4110 is information in which the data source ID 4111, connection method 4112, and connection destination information 4113 are associated with each other.
- a data source ID 4111 is identification information of a data source, that is, a database.
- the data source ID 4111 may be information identifying an instance of the database 211 or database 222 .
- the connection method 4112 is information indicating a connection method to the data source.
- the connection method 4112 is database connection (first connection method) or WEB connection (second connection method).
- the connection method 4112 may be information indicating JDBC, REST, or the like.
- connection destination information 4113 stores the type of DBMS (Database Management System), DB server name, DB instance name, DB connection URL, DB connectable user ID and password, and processing target data. Includes table names, etc.
- the connection destination information 4113 includes, in the case of WEB connection, the URL of the Web API endpoint, HTTP method, URL query parameters, and the like.
- Data source definition information 4120 (not shown), . . . , data source definition information 41m0 have the same configuration.
- the data source ID 41m1, connection method 41m2, and connection destination information 41m3 of the data source definition information 41m0 are data equivalent to the data source ID 4111, connection method 4112, and connection destination information 4113, respectively.
- the data attribute information 4210 is information in which attribute ID 4211, attribute name 4212, processing logic 4213 and setting information 4214 are associated.
- the attribute ID 4211 is identification information of the data attribute of the processing target data.
- the attribute name 4212 is a character string indicating the name of the column (attribute) in the table storing the data to be processed (data attribute value).
- the processing logic 4213 is information defining processing logic for data attribute values acquired from the database.
- the processing logic 4213 is logic for processing and displaying data attribute values, or logic for sorting (ascending or descending order) when displaying a list of a plurality of data attribute values.
- the setting information 4214 is information defining various settings related to data attributes to be processed.
- the setting information 4214 includes, for example, option settings related to list display, form display or map display, arguments to be passed to the processing logic 4213, and the like.
- the setting information 4214 may also include processing logic for generating a set of values that can be set in the form and their display names, and processing logic for switching between validation and invalidation of the editing form.
- the setting information 4214 may be described in JSON format.
- the processing logic 4213 and the processing logic in the setting information 4214 may be written in JavaScript (registered trademark), for example.
- Data attribute information 4220 (not shown), . . . , 42n0 have the same configuration.
- the attribute ID 42n1, attribute name 42n2, processing logic 42n3, and setting information 42n4 of the data attribute information 42n0 are data equivalent to the attribute ID 4211, attribute name 4212, processing logic 4213, and setting information 4214, respectively.
- the source attribute relation definition 4310 and the like is information that defines a one-to-many relation between data source definition information and data attribute information.
- Each of the source attribute relation definitions 4310 to 43m0 corresponds to each of the data source definition information 4110 to 41m0.
- a source attribute association definition 4310 is information that associates a data source ID 4311 with attribute IDs 43121 to 4312x.
- the data source ID 4311 is the data source ID 4111 of the data source definition information 4110
- the attribute IDs 43121-4312x are any of the attribute IDs 4211-42n1 of the data attribute information 4210-42n0.
- Source attribute relation definitions 4320 (not shown), . . . , 43m0 have similar configurations.
- the source attribute association definition 43m0 is information that associates a data source ID 43m1 with attribute IDs 43m21 to 43m2y.
- the data source ID 43m1 is the data source ID 41m1 of the data source definition information 41m0
- the attribute IDs 43m21-43m2y are any of the attribute IDs 4211-42n1 of the data attribute information 4210-42n0.
- x and y described above may be at least 1 or more natural numbers. Attribute IDs may overlap among the source attribute association definitions 4310 to 43m0.
- the screen definition 315 is information that defines the display format for displaying the data to be processed, the constituent elements of the screen, and the like.
- the screen definition 315 is information defining attribute information of a table of a database in which data to be processed is stored, processing for the data to be processed, and the like.
- Screen definition 315 may include multiple screen components. At least some of the plurality of screen components include data attributes included in the data source definition. Also, at least some of the plurality of screen components may include processing logic.
- FIG. 6 is a diagram showing a configuration example of screen definition according to the second embodiment.
- the screen definition 315 includes screen definition information 5110 to 51i0, screen configuration information 5210 to 52j0, screen configuration related definitions 5310 to 53i0, and configuration attribute related definitions 5410 to 54j0.
- i and j are two or more natural numbers.
- the screen configuration information 5210 and the like are examples of screen configuration elements. Also, the screen configuration information 5210 and the like can be said to include definitions of data attributes by attribute IDs defined in the configuration attribute relation definition 5410 and the like.
- the screen definition information 5110 is information in which a screen definition ID 5111, a display format 5112, and a data source ID 5113 are associated with each other.
- the screen definition ID 5111 is identification information of the display screen.
- the screen definition ID 5111 is also information specified in the screen display request. Since the screen definition ID 5111 can be said to be part of the screen configuration information, it may be called a component ID, and screen identification information may exist separately.
- the display format 5112 is information indicating the format of the display screen.
- the display format 5112 may be, for example, a list screen, a detailed data display screen, or a dedicated map screen, but is not limited to these.
- the data source ID 5113 is identification information of a data source definition including data attributes of processing target data used for the screen.
- the data source ID 5113 may be 2 or more. That is, the screen definition ID 5111 and the data source ID 5113 may be associated one-to-many.
- Screen definition information 5120 (not shown), . . . , screen definition information 51i0 have the same configuration.
- screen definition ID 51i1, display format 51i2, and data source ID 51i3 of screen definition information 51i0 are data equivalent to screen definition ID 5111, display format 5112, and data source ID 5113, respectively.
- the screen configuration information 5210 is information in which a configuration ID 5211, a type 5212, and a processing logic 5213 are associated with each other.
- the configuration ID 5211 is identification information of screen configuration elements. Note that the configuration ID 5211 may also be called a component ID.
- the type 5212 is information indicating the type of screen component. Types 5212 include, but are not limited to, buttons, menus, lists, forms, unique objects, graphs, headers, footers, metrics, maps, and the like.
- the processing logic 5213 is information defining processing logic for data attribute values (processing target data) acquired from the database. Configuration IDs and attribute IDs are associated on a one-to-many basis in the configuration attribute association definition described later.
- the processing logic 5213 can be said to be, for example, information defining processing logic for acquired data corresponding to the attribute IDs 54121 to 5412p associated with the configuration ID 5411 (configuration ID 5211) in the configuration attribute association definition 5410.
- FIG. Note that the processing logic 5213 is not essential and may not be set depending on the type 5212 .
- the screen configuration information 5210 may include setting information that defines various settings for components.
- the setting information may include processing logic and may be described in JSON format, similar to the setting information 4214 described above.
- the processing logic 5213 and the processing logic in the setting information may be written in JavaScript (registered trademark), for example.
- the screen configuration information 5220 (not shown), . . . , the screen configuration information 52j0 also have the same configuration.
- the configuration ID 52j1, type 52j2 and processing logic 52j3 of the screen configuration information 52j0 are data equivalent to the configuration ID 5211, type 5212 and processing logic 5213, respectively.
- the screen configuration related definitions 5310 and the like are information that defines one-to-many associations between screen definition information and screen configuration information.
- Each of the screen configuration related definitions 5310 to 53i0 corresponds to each of the screen definition information 5110 to 51i0.
- a screen configuration related definition 5310 is information that associates a screen definition ID 5311 with configuration IDs 53121 to 5312z.
- the screen definition ID 5311 is the screen definition ID 5111 of the screen definition information 5110
- the configuration IDs 53121-5312z are any of the configuration IDs 5211-52j1 of the screen configuration information 5210-52j0. . . , 53i0 also have the same configuration.
- the screen configuration related definition 53i0 is information that associates the screen definition ID 53i1 with the configuration IDs 53i21 to 53i2w.
- the screen definition ID 53i1 is the screen definition ID 51i1 of the screen definition information 51i0
- the configuration IDs 53i21 to 53i2w are any of the configuration IDs 5211 to 52j1 of the screen configuration information 5210 to 52j0.
- z and w described above may be at least 1 or more natural numbers.
- the configuration IDs may overlap among the screen configuration related definitions 5310 to 53i0.
- the configuration attribute relation definition 5410 and the like is information that defines the one-to-many association between the screen configuration information and the data attribute information corresponding to the processing target data.
- Configuration attribute related definitions 5410 to 54j0 correspond to screen configuration information 5210 to 52j0, respectively.
- a configuration attribute relation definition 5410 is information that associates a configuration ID 5411 with attribute IDs 54121 to 5412p.
- the configuration ID 5411 is the configuration ID 5211 of the screen configuration information 5210
- the attribute IDs 54121-5412p are any of the attribute IDs 4211-42n1 of the data attribute information 4210-42n0.
- Configuration attribute related definitions 5420 (not shown), . . . , 54j0 have similar configurations.
- the configuration attribute relation definition 54j0 is information that associates the configuration ID 54j1 with the attribute IDs 54j21 to 54j2q.
- the configuration ID 54j1 is the configuration ID 52j1 of the screen configuration information 52j0
- the attribute IDs 54j21 to 54j2q are any of the attribute IDs 4211 to 42n1 of the data attribute information 4210 to 42n0.
- p and q described above may be at least 1 or more natural numbers.
- attribute IDs may be duplicated among the configuration attribute association definitions 5410 to 54j0.
- the screen template 316 is template information used when generating a display screen.
- a screen template 316 may exist for each display format.
- the screen template 316 may be configured to display 0 to a plurality of pieces of screen configuration information for each type of screen configuration information.
- the memory 320 is a volatile storage device such as RAM (Random Access Memory), and is a storage area for temporarily holding information when the control unit 340 operates.
- a communication unit 330 is a communication interface with the network N. FIG.
- the control unit 340 is a processor that controls each component of the operation support device 300, that is, a control device.
- the control unit 340 loads the program 311 from the storage unit 310 into the memory 320 and executes the program 311 .
- the control unit 340 realizes the functions of the registration unit 341 , the identification unit 342 , the selection unit 343 , the data acquisition unit 344 , the generation unit 345 and the output unit 346 .
- the registration unit 341 is an example of the registration unit 11 described above.
- the registration unit 341 registers the data source definition 314 and the screen definition 315 .
- the registration unit 341 generates the data source definition 314 based on the registration request regarding the data source definition received from the management terminal 110 and stores it in the storage unit 310 .
- the registration unit 341 generates the screen definition 315 based on the registration request regarding the screen definition received from the management terminal 110 and stores it in the storage unit 310 .
- the registration unit 341 may have the function of the setting tool described above.
- the registration unit 341 may display a registration screen on the management terminal 110 and accept the registration request via the registration screen.
- the identification unit 342 is an example of the identification unit 12 described above.
- the identifying unit 342 receives a screen display request from the operation terminal 120 and identifies the screen definition ID specified in the screen display request. Then, the identifying unit 342 identifies screen definition information including the identified screen definition ID from the screen definition 315, and identifies the data source ID included in the identified screen definition information. Further, the specifying unit 342 specifies one or more pieces of screen configuration information associated with the specified screen definition ID from among the screen configuration related definitions. Further, the specifying unit 342 specifies attribute IDs associated with each of the configuration IDs of the specified screen configuration information from among the configuration attribute related definitions.
- the identifying unit 342 identifies data source definition information including the identified data source ID from the data source definition 314 . Then, the identifying unit 342 identifies one or more attribute IDs associated with the identified data source ID from among the source attribute association definitions. Then, the specifying unit 342 specifies the attribute ID group (data attribute) specified from the configuration attribute relation definition among the attribute ID group specified from the source attribute relation definition.
- the selection unit 343 is an example of the selection unit 13 described above.
- the selection unit 343 selects the connection processing means corresponding to the connection method included in the specified data source definition information. For example, when the connection method is database connection, the selection unit 343 selects the DB connection processing module 312 . If the connection method is WEB connection, the selection unit 343 selects the WEB connection processing module 313 .
- the data acquisition unit 344 is an example of the data acquisition unit 14 described above.
- the data acquisition unit 344 uses the selected connection processing means to acquire target data from the database based on the connection destination information and data attributes included in the specified data source definition. For example, when the connection method is database connection, the data acquisition unit 344 uses the selected DB connection processing module 312 to perform connection processing with the database 211 for the external system 210 based on the connection destination information. After the connection process, the data acquisition unit 344 acquires target data by performing a search process for data corresponding to the specified data attribute in the database 211 . If the connection method is WEB connection, the data acquisition unit 344 uses the selected WEB connection processing module 313 to transmit a data acquisition request including connection destination information and data attributes to the external system 220. do. Then, the data acquisition unit 344 acquires target data by receiving a response from the external system 220 .
- the connection method is database connection
- the data acquisition unit 344 uses the selected DB connection processing module 312 to perform connection processing with the database 211 for
- the generation unit 345 is an example of the generation unit 15 described above.
- the generation unit 345 generates a display screen for displaying the acquired target data according to the display format included in the identified screen definition. Specifically, the generation unit 345 arranges each screen component at a display position according to the display format, and displays the target data acquired by the data acquisition unit 344 on the screen component including the data attribute. Generate a screen.
- the generation unit 345 generates the display screen including the processing logic included in the arranged screen components.
- the generation unit 345 generates a display screen including the processing logic included in the data attribute corresponding to the acquired target data.
- the generation unit 345 may generate the screen generation control information without generating the display screen.
- the screen generation control information is information for causing the request source to generate a display screen for displaying the acquired target data according to the display format.
- the output unit 346 is an example of the output unit 16 described above.
- the output unit 346 outputs the generated display screen (or screen generation control information) to the operation terminal 120 that is the source of the request.
- the management terminal 110 transmits a request to display a data source definition registration screen to the operation support device 300 via the network N in response to an operation by the management user U1.
- the operation support device 300 returns a data source definition registration screen to the management terminal 110 in response to the display request.
- the management terminal 110 displays the received registration screen.
- FIG. 7 is a diagram showing an example of the data source definition registration screen 4 according to the second embodiment.
- the data source definition registration screen 4 includes a data source definition 40 , data attribute information 41 , 42 and 43 , and a registration button 49 . Also, FIG. 7 shows a state in the middle of input by the administrative user U1.
- the data source definition 40 includes input fields for a data source ID 401 , connection method 402 and connection destination information 403 .
- the connection method 402 shows an example in which "JDBC" or "REST” can be selected from a pull-down, and "JDBC" is selected.
- connection destination information 403 shows an example in which the DBMS type, the DB connection URL, the DB connectable user ID and password, and the table name storing the processing target data are input. Note that when "REST" is selected in the connection method 402, the display content of the connection destination information 403 is also changed to an input field corresponding to "REST".
- the data attribute information 41 to 43 are input fields for data attribute groups corresponding to the data to be processed among the columns of the table input to the connection destination information 403 .
- the data attribute information 41 includes attribute ID 411 , attribute name 412 , processing logic 413 and setting information 414 .
- data attribute information 42 comprises attribute ID 421 , attribute name 422 , processing logic 423 and setting information 424 .
- the data attribute information 43 also includes attribute ID 431 , attribute name 432 , processing logic 433 , setting information 434 and an add button 435 .
- attribute names 412, 422, and 432 are examples in which character strings of column names defined in the table "temperature" are input.
- an input field for new data attribute information is additionally displayed.
- values input by the administrative user U1 may be displayed when anything other than "automatic numbering" is selected from the pull-down menu.
- the registration button 49 is a button for sending a registration request including the input contents of the data source definition 40 and the data attribute information 41 to 43 to the operation support device 300 when pressed.
- FIG. 8 is a flowchart showing the flow of data source definition registration processing according to the second embodiment.
- the management terminal 110 receives and displays the input contents of the data source definition registration screen 4 by the input operation of the management user U1.
- the management terminal 110 additionally displays an input field for data attribute information, and further receives and displays input contents.
- the management terminal 110 receives the press of the registration button 49 from the management user U1
- the management terminal 110 generates a data source definition registration request including the input contents of the data source definition registration screen 4.
- the management terminal 110 transmits a data source definition registration request to the operation support device 300 via the network N.
- the registration unit 341 of the operation support device 300 receives a data source definition registration request from the management terminal 110 (S201).
- the registration unit 341 generates registration information based on the input content included in the received registration request (S202). For example, the registration unit 341 generates the data source definition information 4110 from the input contents of the data source ID 401 , connection method 402 and connection destination information 403 . Further, the registration unit 341 generates data attribute information 4210 from the input contents of the data attribute information 41 . Specifically, the registration unit 341 newly issues the attribute ID 4211, and converts the input contents of the attribute name 412, the processing logic 413, and the setting information 414 into the data attribute information 4210 as the attribute name 4212, the processing logic 4213, and the setting information 4214.
- the registration unit 341 generates data attribute information 4220 and 4230 for the input contents of the data attribute information 42 and 43 .
- the registration unit 341 then associates the data source ID 4111 of the data source definition information 4110 with the attribute IDs 4211 to 4231 of the data attribute information 4210 to 4230 to generate the source attribute relation definition 4310 .
- the registration unit 341 registers the generated registration information (data source definition information 4110, data attribute information 4210 to 4230, and source attribute relation definition 4310) in the storage unit 310 as the data source definition 314 (S203).
- the management terminal 110 transmits a display request for a screen definition registration screen to the operation support apparatus 300 via the network N in response to an operation by the management user U1.
- the operation support device 300 returns a screen definition registration screen to the management terminal 110 in response to the display request.
- the management terminal 110 displays the received registration screen.
- FIG. 9 is a diagram showing an example of the screen definition registration screen 5 according to the second embodiment.
- the screen definition registration screen 5 includes screen definition information 50 , a header 51 , a footer 52 , a list 53 , a button 54 , a form 55 , a menu 56 , a graph 57 , a map 58 and a registration button 59 .
- the screen definition registration screen 5 may include input fields for unique objects and metrics.
- FIG. 9 shows a state in the middle of input by the administrative user U1. Also, the input fields of the header 51, footer 52, form 55, menu 56, graph 57 and map 58 are hidden. It is assumed that when the "+" button of each input field is pressed, the individual input field is expanded and displayed. Further, when the "-" button of each input column is pressed, the individual input column is closed and displayed.
- the screen definition information 50 is input fields for a screen definition ID 501, a display format 502, and a data source ID 503.
- a display format 502 allows selection of a list screen, a detailed data display screen, a dedicated map screen, or the like from a pull-down menu.
- a data source ID 503 is an input field for data source IDs, and two or more data source IDs can optionally be input. For example, when the "Add" button of the data source ID 503 is pressed, one input field for the data source ID is added.
- the header 51 is an input field for information for customizing the header area of the display screen as a screen component.
- the footer 52 is an information input field for customizing the footer area of the display screen as a screen component.
- the list 53 is an input field for defining the display attributes of acquired data when displaying the list.
- a list 53 indicates that attribute names have been entered in the input fields for attribute names 531, 532, and 533, respectively.
- an attribute ID entry field may be used instead of the attribute name.
- the list 53 may be provided with input fields for various settings other than the attribute name. For example, an input field for processing logic may be provided in association with each attribute name. Processing logic may be processing that is performed when an attribute value is displayed.
- the button 54 is an input field for defining buttons that can be used in list display and detailed display.
- the button 54 has, for example, an input field for the processing logic 541 in addition to the button type and display name.
- the button type may be, for example, output (download) of list display contents, update of display contents, approval (registration or update of display contents), instruction to execute a specific command to an external system, or the like.
- Processing logic 541 is a definition of processing logic that is executed when a button is pressed.
- the form 55 is an input field for defining a form such as input or search that can be used in detailed display.
- a menu 56 is an input column for defining a menu list used as options in list display.
- a graph 57 is an input field for defining the graph display.
- a map 58 is an input field for defining a map display.
- Form 55 , menu 56 , graph 57 and map 58 may be provided with input fields for attribute names such as list 53 and processing logic such as button 54 .
- the list 53, button 54, form 55, menu 56, graph 57 and map 58 may also define multiple screen elements within.
- a registration request including input contents of the screen definition information 50, the header 51, the footer 52, the list 53, the button 54, the form 55, the menu 56, the graph 57 and the map 58 is sent to the operation support device.
- 300 is a button for sending.
- FIG. 10 is a flowchart showing the flow of screen definition registration processing according to the second embodiment.
- the management terminal 110 receives and displays the input contents of the screen definition registration screen 5 by the input operation of the management user U1.
- the management terminal 110 expands and displays the details of each input field, and when the "-" button is pressed, the details of each input field are closed and displayed. .
- the management terminal 110 further receives and displays input contents in the expanded input fields.
- the management terminal 110 receives the press of the registration button 59 from the management user U1
- the management terminal 110 generates a screen definition registration request including the input contents of the screen definition registration screen 5 .
- the management terminal 110 transmits a screen definition registration request to the operation support device 300 via the network N.
- the registration unit 341 of the operation support device 300 receives a screen definition registration request from the management terminal 110 (S211).
- the registration unit 341 generates registration information based on the input content included in the received registration request (S212). For example, the registration unit 341 generates the screen definition information 5110 from the input contents of the screen definition ID 501 , the display format 502 and the data source ID 503 . Further, the registration unit 341 newly issues a configuration ID corresponding to each of the header 51 to the map 58, sets a type corresponding to each screen component, and generates screen configuration information 5210 and the like. For example, when generating the screen configuration information 5210 corresponding to the button 54 , the registration unit 341 sets information indicating “button” to the type 5212 and sets the content of the processing logic 541 to the processing logic 5213 .
- the registration unit 341 also includes the display name and the like in the screen configuration information 5210 corresponding to the button 54 .
- the registration unit 341 then associates the screen definition ID 5111 of the screen definition information 5110 with the configuration ID of each screen configuration information to generate the configuration attribute relation definition 5410 .
- the registration unit 341 converts the attribute name of each screen component into an attribute ID based on the data source ID 503 . For example, the registration unit 341 searches for and identifies an attribute ID corresponding to the data source ID 503 “1000” and the attribute name 531 “date” based on the source attribute relation definition and the data attribute information of the data source definition 314 . Then, the registration unit 341 associates the configuration IDs issued in the list 53 with the converted (specified) attribute ID group to generate configuration attribute association definitions.
- the registration unit 341 registers the generated registration information (screen definition information 5110, screen configuration information 5210, etc., screen configuration related definition 5310, configuration attribute related definition 5410, etc.) in the storage unit 310 as the screen definition 315 (S213). .
- the management terminal 110 may use the setting tool provided by the operation support device 300 to generate an SQL statement (insert statement for each record) as a registration request. For example, when the registration button 49 or 59 is pressed, the setting tool generates a record to be inserted into each table of the data source definition 314 and the screen definition 315 as in steps S202 and S212 based on the input contents of the registration screen. You may output the Insert statement of . In that case, the management terminal 110 may connect to the database of the operation support device 300 via a command line UI (User Interface) and execute the generated SQL statement.
- UI User Interface
- FIG. 11 is a flowchart showing the flow of screen display processing according to the second embodiment.
- the administrative user U1 has already registered in the operation support device 300 a screen definition of a display screen for customizing and displaying data contents of a database managed by an external system and a data source definition thereof. Then, it is assumed that the operational user U2 browses the display screen.
- the operation terminal 120 transmits a screen display request for the display screen to the operation support device 300 via the network N in accordance with the operation of the operation user U2.
- the screen display request includes the screen definition ID of the display screen.
- the screen display request is an HTTP request message for a URL containing the host name of the operation support device 300 and the screen definition ID.
- the identification unit 342 of the operation support device 300 receives a screen display request from the operation terminal 120 (S221). The identifying unit 342 then analyzes the received screen display request and identifies the screen definition ID.
- the identifying unit 342 identifies screen definition information and screen configuration information based on the identified screen definition ID (S222). Specifically, as described above, the identifying unit 342 identifies the data source ID and configuration ID group associated with the identified screen definition ID, and identifies the attribute ID group associated with each identified configuration ID. .
- the identifying unit 342 identifies data source definition information and data attribute information based on the identified data source ID and attribute ID group (S223). At this time, the identifying unit 342 identifies the connection method and connection destination information included in the identified data source definition information.
- the selection unit 343 determines the specified connection method (S224).
- the connection method is DB connection
- the selection unit 343 selects the DB connection processing module 312 (S225).
- the data acquisition unit 344 uses the DB connection processing module 312 to perform connection processing with the database 211 for the external system 210 based on the connection destination information (S226).
- the data acquisition unit 344 sets a DB connection URL, a user ID and a password that allow DB connection to the DB connection processing module 312, and executes connection processing with the database 211 by the DB connection processing module 312. .
- the data acquisition unit 344 searches the database 211 for data corresponding to the specified data attribute (S227). For example, the data acquisition unit 344 issues a search command designating the columns “date”, “average”, “highest”, etc. in the table “temperature” to the database 211 . Then, the data acquisition unit 344 acquires search results from the database 211 .
- the selection unit 343 selects the WEB connection processing module 313 (S228). Then, the data acquisition unit 344 uses the WEB connection processing module 313 to transmit a data acquisition request including the connection destination information and data attributes to the external system 220 (S229).
- the URL of the WEB application server 221 for REST connection is set for the WEB connection processing module 313 , and the WEB connection processing module 313 transmits an HTTP request to the WEB application server 221 .
- the data acquisition unit 344 then receives a response from the web application server 221 (S230).
- the generation unit 345 uses the screen definition information and the screen configuration information to generate a display screen for displaying the acquired target data (S231). Specifically, generation unit 345 reads screen template 316 corresponding to the display format included in the identified screen definition information. Then, the generation unit 345 arranges a tag or the like according to the specified type of screen configuration information at the arrangement position of each piece of screen configuration information in the screen template 316 . In addition, the generation unit 345 arranges target data corresponding to the attribute ID group associated with the configuration ID at the arrangement position of each piece of screen configuration information. Similarly, the generation unit 345 embeds processing logic associated with the configuration ID at the arrangement position of each piece of screen configuration information. In addition, the generation unit 345 embeds processing logic and setting information included in the data attribute information corresponding to the attribute ID group associated with the configuration ID at the layout position of each piece of screen configuration information.
- the output unit 346 outputs the generated display screen to the request source (S232). Specifically, the output unit 346 transmits the generated display screen to the operation terminal 120 via the network N.
- the operation terminal 120 displays the received display screen.
- the generation unit 345 may generate screen generation control information including the specified screen definition information and screen configuration information, and the acquired target data.
- the generation unit 345 may generate screen generation control information in JSON format.
- the output unit 346 transmits the generated screen generation control information to the operation terminal 120 via the network N.
- the operation terminal 120 may use a predetermined screen template from the received screen generation control information to perform processing corresponding to step S231 described above to generate the display screen.
- FIG. 12 is a diagram showing an example of the display screen 6 according to the second embodiment.
- the display screen 6 has a header 61 , a search form field 62 , a list display field 63 and an export button 64 .
- the header 61 is the content generated based on the display information and setting information of the screen configuration information whose type is header.
- the search form column 62 has contents generated based on the screen configuration information whose type is form.
- the search form field 62 includes a monitoring device name input field 621 , a prefecture selection field 622 and a search button 623 .
- the monitoring device name input field 621 is an input field for the name of the server of the external system to be searched.
- the monitoring device name input field 621 is generated based on the display name and check box option settings defined in the screen configuration information whose type is form.
- the prefecture selection column 622 is a column for selecting the condition of the prefecture in which the search target server or the like is installed.
- the prefecture selection field 622 is generated from the search result of the prefecture to which the installation location of the monitoring target device belongs from a predetermined database, whether "Tokyo" or the like is set in the display name defined in the screen configuration information whose type is form. It is what was done. Also, the prefecture selection column 622 is generated based on the option setting of the check box.
- the search button 623 is a button that, when pressed, transmits a search request using the monitoring device name input field 621 and the prefecture selection field 622 as search conditions to the database of the external system.
- the search button 623 may be automatically generated along with the search form.
- the list display column 63 has contents generated based on the display information, data attributes, processing logic, setting information, etc. of the screen configuration information whose type is list.
- the list display column 63 includes attribute names 631 and operating states 632 .
- the attribute name 631 is the display name of each piece of data attribute information (column) associated with screen configuration information whose type is list.
- Each record displayed in the list display column 63 is target data acquired based on each data attribute information associated with the screen configuration information whose type is list.
- the operating state 632 indicates that processing logic is set in the data attribute information associated with the screen configuration information whose type is list, and the display has been processed according to the processing logic.
- the processing logic is, for example, a process of displaying in color when the acquired data of the attribute "operating state" is "stopped”. By defining processing logic in this way, flexible display control can be achieved. Of course, the processing logic is not limited to this.
- the export button 64 is a button for outputting the checked records in the list display field 63 to the operation terminal 120 when pressed.
- the export button 64 displays a display name defined in the screen configuration information of the button type, and embeds a processing logic as a search request and search result output processing.
- a wide variety of screen components can be easily customized.
- visualization using a wide variety of existing data sources can be easily realized. For example, after defining a display screen for a certain database, when defining a display screen for another database with a different connection destination or connection method, it can be easily handled by adding or changing the data source definition. Also, when creating a large number of similar display screens for an existing data source, it is possible to easily add screens by using the screen definition. Then, the amount of system modification at that time can be reduced. In particular, the amount of program coding can be reduced. In addition, since processing logic can be set in the data source definition and screen definition, detailed display control can be easily achieved.
- Embodiment 3 is a modification of Embodiment 2 described above. It is assumed that the request source according to the third embodiment is the content provider server, and the content includes a screen definition ID that identifies the screen definition. Therefore, the specifying unit according to the third embodiment receives a screen display request designating a screen definition ID from the provider server during content display processing in the provider server. The specifying unit then specifies a screen definition corresponding to the screen definition ID. In other words, although the operation support device 300 differs from the second embodiment in the source of the screen display request, it can use the same processing for generating the display screen information.
- FIG. 13 is a block diagram showing the overall configuration of the operation support system 1000a according to the third embodiment.
- the operation support system 1000a has an operation management system 230 added as compared with FIG. Since other configurations are the same as those in FIG. 3, illustration and description are omitted as appropriate.
- the operation management system 230 is an existing information system used by the operation user U2 or the like to manage the operation of the external systems 210 and 220 by modifying contents for operation management.
- the operation management system 230 includes a web application server 231 and a storage device 232 .
- the storage device 232 stores contents 233 for operation management.
- the content 233 is template data of a dynamically generated WEB page (display screen).
- the content 233 defines (describes) a plurality of frames 2331 and 2332 .
- a frame 2331 is a unique content area of the operation management system 230 .
- a frame 2332 defines a screen display request access destination URL 23321 .
- the frame 2332 may define the screen display request access destination URL 23321 using an HTML5 iframe tag.
- the screen display request access destination URL 23321 is access destination information including a screen definition ID registered in the operation support device 300 .
- the screen display request access destination URL 23321 is a URL containing the host name and screen definition ID
- the WEB application server 231 is connected to the network N.
- the web application server 231 receives an access request to the content 233 from the operation terminal 120 or the like via the network N, the web application server 231 analyzes the content 233, generates a display screen according to the definition of each frame, and sends it to the operation terminal 120. Reply.
- the web application server 231 transmits a request to the screen display request access destination URL 23321 included in the frame 2332 . That is, the WEB application server 231 transmits an HTTP request to the operation support apparatus 300 via the network N with the screen display request access destination URL 23321 as the destination.
- the operation support device 300 executes the processes of steps S221 to S232 described above based on the screen definition ID specified in the HTTP request received from the WEB application server 231, generates a display screen, and returns it. do. Then, the WEB application server 231 receives the display screen from the operation support device 300 as a response to the HTTP request. The web application server 231 then embeds the received display screen in the frame 2332 to generate a display screen corresponding to the content 233 . The WEB application server 231 then returns the display screen to the operation terminal 120 that is the source of the request. Note that the operation support device 300 may generate and return screen generation control information instead of the display screen as in the second embodiment described above.
- FIG. 14 is a diagram showing an example of the display screen 6a according to the third embodiment.
- the display screen 6 a includes frames 651 , 652 and a frame 653 .
- a frame 651 is unique content of the operation management system 230 .
- Frames 652 and 653 indicate that the graph display screen and the list display screen generated in the operation support device 300 are displayed by setting the screen display request access destination URL 23321 including different screen definition IDs.
- the third embodiment can also achieve the same effects as the above-described second embodiment.
- the display screen information generation function of the operation support device 300 can be called from the content of the external system (operation management system) itself. Therefore, it is possible to easily realize more flexible display control by finely responding to the needs of operation users.
- Embodiment 4 is an improved example of Embodiment 2 or 3 described above.
- At least part of the plurality of screen components according to the fourth embodiment includes operation information for the external system.
- the generation unit according to the fourth embodiment embeds a process for transmitting a processing request to an external system based on the operation information included in the arranged screen component in response to the user's operation on the arranged screen component. , to generate the display screen.
- an operational user who has visually recognized the display screen customized according to the second or third embodiment can continue to make processing requests to the external system for the display screen according to the display content. In other words, there is no need for the operating user to separately operate the external system.
- operational information includes processing logic in at least one of data acquisition or data update for a database, or instruction for an external system. Therefore, flexible control can be realized for the external system.
- processing request according to the fourth embodiment includes at least one request for data acquisition processing or data update processing for the database, or command execution for the external system. Therefore, flexible control can be realized for the external system.
- the operation support device 300 has operation information added to the screen definition information in the screen definition 315 .
- FIG. 15 is a diagram showing a configuration example of the screen definition information 5210b according to the fourth embodiment.
- the screen definition information 5210b includes operation information 5214 in addition to the configuration ID 5211, type 5212 and processing logic 5213.
- FIG. Operational information 5214 includes processing logic in retrieving or updating data to a database and/or issuing instructions to external systems, as described above.
- FIG. 16 is a diagram showing an example of the display screen 6b according to the fourth embodiment.
- the display screen 6b has a device control menu 66 added in addition to the header 61, search form column 62 and list display column 63 described above.
- the device control menu 66 is content generated based on the display information, processing logic, setting information, operation information, etc. of the screen configuration information whose type is menu.
- the device control menu 66 is a selection column from which a plurality of menus, data acquisition 661, data update 662, and restart 663 can be selected by pull-down. Operation information is set for each of data acquisition 661, data update 662, and restart 663, and when one of the menus is selected, a processing request based on the set operation information is sent to the database. be.
- the operating user U2 selects any one of data acquisition 661, data update 662, and restart 663, an operation corresponding to the selected menu is executed for the external system.
- operation information for acquiring data from the database of the external system for the checked records in the list display field 63 and outputting the data to the operation terminal 120 is set.
- the data acquisition 661 may be set with the same processing logic as the export button 64 described above.
- the data update 662 is set with operation information for transmitting a processing request for updating data in the database of the external system for the checked record when each item value of the display record in the list display column 63 is editable. ing.
- the data update 662 may be set with operation information for updating the contents of the record entered in the update data input field, which is not shown in FIG. 16, to the database of the external system.
- operation information is set for sending a restart command for the OS, WEB application server, database, etc. to the external system.
- the fourth embodiment can also achieve the same effect as the above-described second or third embodiment.
- the operational user U2 acquires and visualizes information from the database of an existing external system, changes the settings of the external system, requests processing (restart, stop, job execution, etc.) to the external system. )It can be performed.
- the operating user U2 checks the status of the information system to be operated from the display screen based on the display screen information generated by the operation support device 300, and continues to issue processing instructions to the external system on the same display screen. It can be carried out. Therefore, further operation support can be realized.
- Non-transitory computer readable media include various types of tangible storage media.
- Examples of non-transitory computer-readable media include magnetic recording media (e.g., flexible discs, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical discs), CD-ROMs (Read Only Memory), CD-Rs, Includes CD-R/W, DVD (Digital Versatile Disc), semiconductor memory (eg, mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory)).
- magnetic recording media e.g., flexible discs, magnetic tapes, hard disk drives
- magneto-optical recording media e.g., magneto-optical discs
- CD-ROMs Read Only Memory
- CD-Rs Includes CD-R/W
- DVD Digital Versatile Disc
- semiconductor memory eg, mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM,
- the program may also be delivered to the computer on various types of transitory computer readable medium.
- Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves.
- Transitory computer-readable media can deliver the program to the computer via wired channels, such as wires and optical fibers, or wireless channels.
- Appendix A1 A registration unit that registers data source definitions including connection methods, connection destination information and data attributes for accessing databases managed by external systems, and screen definitions including data attributes to be processed and display formats of target data.
- an identification unit that identifies a screen definition specified in a screen display request received from a request source and identifies a data source definition corresponding to a data attribute included in the identified screen definition; a selection unit that selects a connection processing means corresponding to the connection method included in the identified data source definition; a data acquisition unit that acquires target data from the database based on connection destination information and data attributes included in the specified data source definition using the selected connection processing means; a generation unit that generates display screen information including the display format included in the identified screen definition and the acquired target data; an output unit that outputs the generated display screen information to the request source; Operation support device.
- the screen definition includes a plurality of screen components, at least some of the plurality of screen components include the data attribute included in the data source definition;
- the generation unit arranges each screen component at a display position according to the display format, and generates the display screen information so as to display the acquired target data on the screen component including the data attribute.
- the operation support device described in . at least some of the plurality of screen components include processing logic;
- At least some of the plurality of screen components include operation information for the external system;
- the generating unit embeds a process for transmitting a processing request based on the operation information included in the screen component to the external system in response to a user's operation on the arranged screen component to generate the display screen.
- the operation support device according to appendix A2 or A3 that generates information.
- the operation support device according to appendix A5, wherein the operation information includes processing logic in at least one of data acquisition or data update for the database, or instruction for the external system.
- Appendix A6 The operation support device according to appendix A4 or A5, wherein the processing request includes at least one of a request for data acquisition processing or data update processing for the database, or a command execution request for the external system.
- the data source definition includes processing logic for the data attributes;
- the operation support device according to any one of Appendixes A1 to A6, wherein the generation unit generates the display screen information including the processing logic included in the data attribute corresponding to the acquired target data.
- the request source is a content provider server; the content includes a screen definition ID that identifies the screen definition;
- the identifying unit receives a screen display request designating the screen definition ID from the provider server and identifies the screen definition corresponding to the screen definition ID during display processing of the content in the provider server.
- the operation support device according to any one of A1 to A7.
- the data acquisition unit if the connection method is a database connection, using the selected connection processing means, performs connection processing with the database based on the connection destination information for the external system;
- the operation support device according to any one of appendices A1 to A8, wherein after the connection process, the target data is acquired by performing a search process for data corresponding to the data attribute in the database.
- connection method is a WEB connection
- the selected connection processing means is used to transmit a data acquisition request including the connection destination information and the data attributes to the external system
- the operation support device according to any one of Appendices A1 to A9, wherein the target data is obtained by receiving a response.
- the generating unit generates, as the display screen information, a display screen for displaying the acquired target data according to the display format included in the specified screen definition,
- the operation support device according to any one of appendices A1 to A10, wherein the output unit outputs the generated display screen to the requester.
- the generation unit generates, as the display screen information, screen generation control information for causing the request source to generate a display screen for displaying the acquired target data according to the display format,
- the operation support device according to any one of Appendices A1 to A10, wherein the output unit outputs the generated screen generation control information to the requester.
- (Appendix B1) a database managed by an external system; an operation support device communicably connected to the external system; with The operation support device is a registration unit for registering a data source definition including a connection method for accessing the database, connection destination information and data attributes, and a screen definition including a data attribute to be processed and a display format of the target data; an identification unit that identifies a screen definition specified in a screen display request received from a request source and identifies a data source definition corresponding to a data attribute included in the identified screen definition; a selection unit that selects a connection processing means corresponding to the connection method included in the identified data source definition; a data acquisition unit that acquires target data from the database based on connection destination information and data attributes included in the specified data source definition using the selected connection processing means; a generation unit that generates display screen information including the display format included in the identified screen definition and the acquired target data; an output unit that outputs the generated display screen information to the request source; operation support system.
- the screen definition includes a plurality of screen components, at least some of the plurality of screen components include the data attribute included in the data source definition;
- the generation unit arranges each screen component at a display position according to the display format, and generates the display screen information such that the acquired target data is displayed on the screen component including the data attribute.
- (Appendix C1) the computer Register the data source definition including the connection method, connection destination information and data attribute for accessing the database managed by the external system, and the screen definition including the data attribute to be processed and the display format of the target data, Identify the screen definition specified in the screen display request received from the requester, identify the data source definition corresponding to the data attribute included in the identified screen definition, selecting a connection processing means corresponding to the connection method included in the identified data source definition; Acquiring target data from the database based on connection destination information and data attributes included in the specified data source definition using the selected connection processing means; generating display screen information including the display format included in the identified screen definition and the acquired target data; outputting the generated display screen information to the requester; Operational support method.
- operation support device 11 registration unit 12 identification unit 13 selection unit 14 data acquisition unit 15 generation unit 16 output unit 1000 operation support system 1000a operation support system 110 management terminal 120 operation terminal 210 external system 211 database 220 external system 221 web application server 222 Database 230 Operation management system 231 WEB application server 232 Storage device 233 Contents 2331 Frame 2332 Frame 23321 Screen display request access destination URL 300 operation support device 310 storage unit 311 program 312 DB connection processing module 313 WEB connection processing module 314 data source definition 315 screen definition 316 screen template 320 memory 330 communication unit 340 control unit 341 registration unit 342 identification unit 343 selection unit 344 data acquisition unit 345 generation unit 346 output unit 4110 data source definition information 4111 data source ID 4112 Connection method 4113 Connection destination information 41m0 Data source definition information 41m1 Data source ID 41m2 Connection method 41m3 Connection destination information 4210 Data attribute information 4211 Attribute ID 4212 Attribute name 4213 Processing logic 4214 Setting information 42n0 Data attribute information 42n1 Attribute ID 42n2 At
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
Description
外部システムで管理されるデータベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録する登録部と、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定する特定部と、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択する選択部と、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行うデータ取得部と、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成する生成部と、
前記生成した表示画面情報を前記要求元へ出力する出力部と、
を備える。
外部システムで管理されるデータベースと、
前記外部システムと通信可能に接続される運用支援装置と、
を備え、
前記運用支援装置は、
前記データベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録する登録部と、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定する特定部と、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択する選択部と、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行うデータ取得部と、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成する生成部と、
前記生成した表示画面情報を前記要求元へ出力する出力部と、
を備える。
外部システムで管理されるデータベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録し、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定し、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択し、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行い、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成し、
前記生成した表示画面情報を前記要求元へ出力する。
外部システムで管理されるデータベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録する登録処理と、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定する特定処理と、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択する選択処理と、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行うデータ取得処理と、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成する生成処理と、
前記生成した表示画面情報を前記要求元へ出力する出力処理と、
をコンピュータに実行させる。
図1は、本実施形態1にかかる運用支援装置1の構成を示すブロック図である。運用支援装置1は、情報システム(外部システム)の運用を支援するための情報処理装置である。ここで、運用支援装置1は、通信ネットワーク(不図示、以降、通信ネットワークを単にネットワークとも称する)を介して、外部システムや運用端末と接続されている。外部システムは、データベースを管理しており、データベースシステムそのものであるか、外部とデータベースとのアクセスインタフェースを有していてもよい。運用端末は、運用ユーザが操作し、運用支援装置1を介して外部システムを管理するための情報処理装置である。尚、運用端末は、外部システムの管理者が操作する管理端末であってもよい。運用支援装置1は、登録部11、特定部12、選択部13、データ取得部14、生成部15及び出力部16を備える。
本実施形態2は、上述した実施形態1の具体例である。図3は、本実施形態2にかかる運用支援システム1000の全体構成を示すブロック図である。運用支援システム1000は、運用ユーザU2により運用される複数の外部システム210及び220等の運用を支援するための情報システムである。運用支援システム1000は、管理端末110、運用端末120、外部システム210、外部システム220及び運用支援装置300を備える。管理端末110、運用端末120、外部システム210、外部システム220及び運用支援装置300のそれぞれは、ネットワークNを介して接続される。ここで、ネットワークNは、有線又は無線の通信回線、例えばインターネットである。
画面定義315は、処理対象データを表示するための表示形式、画面の構成要素等を定義した情報である。また、画面定義315は、処理対象データが格納されたデータベースのテーブルの属性情報や処理対象データに対する処理等を定義した情報である。画面定義315は、複数の画面構成要素を含んでもよい。複数の画面構成要素の少なくとも一部は、データソース定義に含まれるデータ属性を含む。また、複数の画面構成要素の少なくとも一部は、処理ロジックを含んでもよい。
画面テンプレート316は、表示画面を生成する際に用いられるテンプレート情報である。例えば、画面テンプレート316は、表示形式ごとに存在してもよい。画面テンプレート316は、画面構成情報の種別ごとに0から複数個の画面構成情報を表示するように構成されていてもよい。
本実施形態3は、上述した実施形態2の変形例である。本実施形態3にかかる要求元は、コンテンツの提供元サーバであり、コンテンツには、画面定義を識別する画面定義IDが含まれるものとする。そのため、本実施形態3にかかる特定部は、提供元サーバにおけるコンテンツの表示処理時に、当該提供元サーバから、画面定義IDを指定した画面表示要求を受け付ける。そして、特定部は、当該画面定義IDに対応する画面定義を特定する。つまり、運用支援装置300は、実施形態2とは画面表示要求の要求元が異なるものの、表示画面情報の生成処理に同様のものを用いることができる。
本実施形態4は、上述した実施形態2又は3の改良例である。本実施形態4にかかる複数の画面構成要素の少なくとも一部は、外部システムに対するオペレーション情報を含む。そして、本実施形態4にかかる生成部は、配置された画面構成要素に対するユーザの操作に応じて当該画面構成要素に含まれるオペレーション情報に基づく処理要求を外部システムへ送信するための処理を埋め込んで、表示画面を生成する。これにより、実施形態2又は3によりカスタマイズした表示画面を視認した運用ユーザが、表示内容に応じて当該表示画面に対して引き続き、外部システムに対する処理要求を行うことができる。つまり、運用ユーザが別途、外部システムに対してオペレーション操作を行う必要がない。
尚、上述の実施形態では、ハードウェアの構成として説明したが、これに限定されるものではない。本開示は、任意の処理を、CPUにコンピュータプログラムを実行させることにより実現することも可能である。
(付記A1)
外部システムで管理されるデータベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録する登録部と、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定する特定部と、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択する選択部と、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行うデータ取得部と、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成する生成部と、
前記生成した表示画面情報を前記要求元へ出力する出力部と、
を備える運用支援装置。
(付記A2)
前記画面定義は、複数の画面構成要素を含み、
前記複数の画面構成要素の少なくとも一部は、前記データソース定義に含まれる前記データ属性を含み、
前記生成部は、前記表示形式に従った表示位置に各画面構成要素を配置し、前記データ属性を含む画面構成要素に前記取得した対象データを表示させるように前記表示画面情報を生成する
付記A1に記載の運用支援装置。
(付記A3)
前記複数の画面構成要素の少なくとも一部は、処理ロジックを含み、
前記生成部は、前記配置された画面構成要素に含まれる前記処理ロジックを含めて前記表示画面情報を生成する
付記A2に記載の運用支援装置。
(付記A4)
前記複数の画面構成要素の少なくとも一部は、前記外部システムに対するオペレーション情報を含み、
前記生成部は、前記配置された画面構成要素に対するユーザの操作に応じて当該画面構成要素に含まれる前記オペレーション情報に基づく処理要求を前記外部システムへ送信するための処理を埋め込んで、前記表示画面情報を生成する
付記A2又はA3に記載の運用支援装置。
(付記A5)
前記オペレーション情報は、前記データベースに対するデータ取得もしくはデータ更新、又は、前記外部システムに対する命令の少なくともいずれかにおける処理ロジックを含む
付記A4に記載の運用支援装置。
(付記A6)
前記処理要求は、前記データベースに対するデータ取得処理もしくはデータ更新処理、又は、前記外部システムに対する命令実行の少なくともいずれかの要求を含む
付記A4又はA5に記載の運用支援装置。
(付記A7)
前記データソース定義は、前記データ属性に処理ロジックを含み、
前記生成部は、前記取得した対象データに対応するデータ属性に含まれる前記処理ロジックを含めて前記表示画面情報を生成する
付記A1乃至A6のいずれか1項に記載の運用支援装置。
(付記A8)
前記要求元は、コンテンツの提供元サーバであり、
前記コンテンツには、前記画面定義を識別する画面定義IDが含まれ、
前記特定部は、前記提供元サーバにおける前記コンテンツの表示処理時に、当該提供元サーバから、前記画面定義IDを指定した画面表示要求を受け付け、当該画面定義IDに対応する前記画面定義を特定する
付記A1乃至A7のいずれか1項に記載の運用支援装置。
(付記A9)
前記データ取得部は、
前記接続方式がデータベース接続である場合、前記選択された接続処理手段を用いて、前記外部システムに対して前記接続先情報に基づき前記データベースとの接続処理を行い、
前記接続処理後に、前記データベースに対して前記データ属性に対応するデータの検索処理を行うことにより、前記対象データの取得を行う
付記A1乃至A8のいずれか1項に記載の運用支援装置。
(付記A10)
前記データ取得部は、
前記接続方式がWEB接続である場合、前記選択された接続処理手段を用いて、前記外部システムに対して前記接続先情報及び前記データ属性を含めたデータ取得要求を送信し、前記外部システムからの応答を受信することにより、前記対象データの取得を行う
付記A1乃至A9のいずれか1項に記載の運用支援装置。
(付記A11)
前記生成部は、前記特定した画面定義に含まれる表示形式に従って前記取得した対象データを表示させる表示画面を前記表示画面情報として生成し、
前記出力部は、前記生成した表示画面を前記要求元へ出力する
付記A1乃至A10のいずれか1項に記載の運用支援装置。
(付記A12)
前記生成部は、前記取得した対象データを前記表示形式に従って表示させる表示画面を前記要求元において生成させるための画面生成制御情報を前記表示画面情報として生成し、
前記出力部は、前記生成した画面生成制御情報を前記要求元へ出力する
付記A1乃至A10のいずれか1項に記載の運用支援装置。
(付記B1)
外部システムで管理されるデータベースと、
前記外部システムと通信可能に接続される運用支援装置と、
を備え、
前記運用支援装置は、
前記データベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録する登録部と、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定する特定部と、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択する選択部と、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行うデータ取得部と、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成する生成部と、
前記生成した表示画面情報を前記要求元へ出力する出力部と、
を備える運用支援システム。
(付記B2)
前記画面定義は、複数の画面構成要素を含み、
前記複数の画面構成要素の少なくとも一部は、前記データソース定義に含まれる前記データ属性を含み、
前記生成部は、前記表示形式に従った表示位置に各画面構成要素を配置し、前記データ属性を含む画面構成要素に前記取得した対象データを表示させるように前記表示画面情報を生成する
付記B1に記載の運用支援システム。
(付記C1)
コンピュータが、
外部システムで管理されるデータベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録し、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定し、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択し、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行い、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成し、
前記生成した表示画面情報を前記要求元へ出力する、
運用支援方法。
(付記D1)
外部システムで管理されるデータベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録する登録処理と、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定する特定処理と、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択する選択処理と、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行うデータ取得処理と、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成する生成処理と、
前記生成した表示画面情報を前記要求元へ出力する出力処理と、
をコンピュータに実行させる運用支援プログラム。
11 登録部
12 特定部
13 選択部
14 データ取得部
15 生成部
16 出力部
1000 運用支援システム
1000a 運用支援システム
110 管理端末
120 運用端末
210 外部システム
211 データベース
220 外部システム
221 WEBアプリケーションサーバ
222 データベース
230 運用管理システム
231 WEBアプリケーションサーバ
232 記憶装置
233 コンテンツ
2331 フレーム
2332 フレーム
23321 画面表示要求アクセス先URL
300 運用支援装置
310 記憶部
311 プログラム
312 DB接続処理モジュール
313 WEB接続処理モジュール
314 データソース定義
315 画面定義
316 画面テンプレート
320 メモリ
330 通信部
340 制御部
341 登録部
342 特定部
343 選択部
344 データ取得部
345 生成部
346 出力部
4110 データソース定義情報
4111 データソースID
4112 接続方式
4113 接続先情報
41m0 データソース定義情報
41m1 データソースID
41m2 接続方式
41m3 接続先情報
4210 データ属性情報
4211 属性ID
4212 属性名
4213 処理ロジック
4214 設定情報
42n0 データ属性情報
42n1 属性ID
42n2 属性名
42n3 処理ロジック
42n4 設定情報
4310 ソース属性関連定義
4311 データソースID
43121 属性ID
4312x 属性ID
43m0 ソース属性関連定義
43m1 データソースID
43m21 属性ID
43m2y 属性ID
5110 画面定義情報
5111 画面定義ID
5112 表示形式
5113 データソースID
51i0 画面定義情報
51i1 画面定義ID
51i2 表示形式
51i3 データソースID
5210 画面構成情報
5210b 画面構成情報
5211 構成ID
5212 種別
5213 処理ロジック
5214 オペレーション情報
52j0 画面構成情報
52j1 構成ID
52j2 種別
52j3 処理ロジック
5310 画面構成関連定義
5311 画面定義ID
53121 構成ID
5312z 構成ID
53i0 画面構成関連定義
53i1 画面定義ID
53i21 構成ID
53i2w 構成ID
5410 構成属性関連定義
5411 構成ID
54121 属性ID
5412p 属性ID
54j0 構成属性関連定義
54j1 構成ID
54j21 属性ID
54j2q 属性ID
4 データソース定義の登録画面
40 データソース定義
401 データソースID
402 接続方式
403 接続先情報
41 データ属性情報
411 属性ID
412 属性名
413 処理ロジック
414 設定情報
42 データ属性情報
421 属性ID
422 属性名
423 処理ロジック
424 設定情報
43 データ属性情報
431 属性ID
432 属性名
433 処理ロジック
434 設定情報
435 追加ボタン
49 登録ボタン
5 画面定義の登録画面
50 画面定義情報
501 画面定義ID
502 表示形式
503 データソースID
51 ヘッダ
52 フッタ
53 リスト
531 属性名
532 属性名
533 属性名
54 ボタン
541 処理ロジック
55 フォーム
56 メニュー
57 グラフ
58 マップ
59 登録ボタン
6 表示画面
61 ヘッダ
62 検索フォーム欄
621 監視装置名入力欄
622 都道府県選択欄
623 検索ボタン
63 リスト表示欄
631 属性名
632 稼働状態
64 エクスポートボタン
6a 表示画面
651 フレーム
652 フレーム
653 フレーム
6b 表示画面
66 装置制御メニュー
661 データ取得
662 データ更新
663 再起動
N ネットワーク
U1 管理ユーザ
U2 運用ユーザ
Claims (15)
- 外部システムで管理されるデータベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録する登録手段と、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定する特定手段と、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択する選択手段と、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行うデータ取得手段と、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成する生成手段と、
前記生成した表示画面情報を前記要求元へ出力する出力手段と、
を備える運用支援装置。 - 前記画面定義は、複数の画面構成要素を含み、
前記複数の画面構成要素の少なくとも一部は、前記データソース定義に含まれる前記データ属性を含み、
前記生成手段は、前記表示形式に従った表示位置に各画面構成要素を配置し、前記データ属性を含む画面構成要素に前記取得した対象データを表示させるように前記表示画面情報を生成する
請求項1に記載の運用支援装置。 - 前記複数の画面構成要素の少なくとも一部は、処理ロジックを含み、
前記生成手段は、前記配置された画面構成要素に含まれる前記処理ロジックを含めて前記表示画面情報を生成する
請求項2に記載の運用支援装置。 - 前記複数の画面構成要素の少なくとも一部は、前記外部システムに対するオペレーション情報を含み、
前記生成手段は、前記配置された画面構成要素に対するユーザの操作に応じて当該画面構成要素に含まれる前記オペレーション情報に基づく処理要求を前記外部システムへ送信するための処理を埋め込んで、前記表示画面情報を生成する
請求項2又は3に記載の運用支援装置。 - 前記オペレーション情報は、前記データベースに対するデータ取得もしくはデータ更新、又は、前記外部システムに対する命令の少なくともいずれかにおける処理ロジックを含む
請求項4に記載の運用支援装置。 - 前記処理要求は、前記データベースに対するデータ取得処理もしくはデータ更新処理、又は、前記外部システムに対する命令実行の少なくともいずれかの要求を含む
請求項4又は5に記載の運用支援装置。 - 前記データソース定義は、前記データ属性に処理ロジックを含み、
前記生成手段は、前記取得した対象データに対応するデータ属性に含まれる前記処理ロジックを含めて前記表示画面情報を生成する
請求項1乃至6のいずれか1項に記載の運用支援装置。 - 前記要求元は、コンテンツの提供元サーバであり、
前記コンテンツには、前記画面定義を識別する画面定義IDが含まれ、
前記特定手段は、前記提供元サーバにおける前記コンテンツの表示処理時に、当該提供元サーバから、前記画面定義IDを指定した画面表示要求を受け付け、当該画面定義IDに対応する前記画面定義を特定する
請求項1乃至7のいずれか1項に記載の運用支援装置。 - 前記データ取得手段は、
前記接続方式がデータベース接続である場合、前記選択された接続処理手段を用いて、前記外部システムに対して前記接続先情報に基づき前記データベースとの接続処理を行い、
前記接続処理後に、前記データベースに対して前記データ属性に対応するデータの検索処理を行うことにより、前記対象データの取得を行う
請求項1乃至8のいずれか1項に記載の運用支援装置。 - 前記データ取得手段は、
前記接続方式がWEB接続である場合、前記選択された接続処理手段を用いて、前記外部システムに対して前記接続先情報及び前記データ属性を含めたデータ取得要求を送信し、前記外部システムからの応答を受信することにより、前記対象データの取得を行う
請求項1乃至9のいずれか1項に記載の運用支援装置。 - 前記生成手段は、前記特定した画面定義に含まれる表示形式に従って前記取得した対象データを表示させる表示画面を前記表示画面情報として生成し、
前記出力手段は、前記生成した表示画面を前記要求元へ出力する
請求項1乃至10のいずれか1項に記載の運用支援装置。 - 前記生成手段は、前記取得した対象データを前記表示形式に従って表示させる表示画面を前記要求元において生成させるための画面生成制御情報を前記表示画面情報として生成し、
前記出力手段は、前記生成した画面生成制御情報を前記要求元へ出力する
請求項1乃至10のいずれか1項に記載の運用支援装置。 - 外部システムで管理されるデータベースと、
前記外部システムと通信可能に接続される運用支援装置と、
を備え、
前記運用支援装置は、
前記データベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録する登録手段と、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定する特定手段と、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択する選択手段と、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行うデータ取得手段と、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成する生成手段と、
前記生成した表示画面情報を前記要求元へ出力する出力手段と、
を備える運用支援システム。 - コンピュータが、
外部システムで管理されるデータベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録し、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定し、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択し、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行い、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成し、
前記生成した表示画面情報を前記要求元へ出力する、
運用支援方法。 - 外部システムで管理されるデータベースへアクセスするための接続方式、接続先情報及びデータ属性を含むデータソース定義と、処理対象のデータ属性と対象データの表示形式とを含む画面定義とを登録する登録処理と、
要求元から受け付けた画面表示要求に指定された画面定義を特定し、当該特定した画面定義に含まれるデータ属性に対応するデータソース定義を特定する特定処理と、
前記特定したデータソース定義に含まれる接続方式に対応する接続処理手段を選択する選択処理と、
前記選択された接続処理手段を用いて、前記特定したデータソース定義に含まれる接続先情報及びデータ属性に基づき前記データベースから対象データの取得を行うデータ取得処理と、
前記特定した画面定義に含まれる表示形式と前記取得した対象データとを含めた表示画面情報を生成する生成処理と、
前記生成した表示画面情報を前記要求元へ出力する出力処理と、
をコンピュータに実行させる運用支援プログラムが格納された非一時的なコンピュータ可読媒体。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP22759165.8A EP4300321A1 (en) | 2021-02-25 | 2022-01-18 | Operation support device, system, and method, and computer-readable medium |
JP2023502163A JP7481056B2 (ja) | 2021-02-25 | 2022-01-18 | 運用支援装置、システム、方法及びプログラム |
US18/275,903 US20240118861A1 (en) | 2021-02-25 | 2022-01-18 | Operation support apparatus, system, method, and computer readable medium |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2021028304 | 2021-02-25 | ||
JP2021-028304 | 2021-02-25 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022181122A1 true WO2022181122A1 (ja) | 2022-09-01 |
Family
ID=83049060
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2022/001645 WO2022181122A1 (ja) | 2021-02-25 | 2022-01-18 | 運用支援装置、システム及び方法並びにコンピュータ可読媒体 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20240118861A1 (ja) |
EP (1) | EP4300321A1 (ja) |
JP (1) | JP7481056B2 (ja) |
WO (1) | WO2022181122A1 (ja) |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040221257A1 (en) * | 2003-05-01 | 2004-11-04 | Lockheed Martin Corporation | Method and apparatus for status display |
JP2010157219A (ja) | 2008-12-31 | 2010-07-15 | Internatl Business Mach Corp <Ibm> | 視覚化ダッシュボードの共同作成方法、システムおよびコンピュータ・プログラム |
US20120144332A1 (en) * | 2010-12-03 | 2012-06-07 | Salesforce.Com, Inc. | Systems and methods for generating a dashboard in a multi-tenant database system environment |
US20150153918A1 (en) * | 2013-12-04 | 2015-06-04 | General Electric Company | System and method for dashboard software maintained by an end user |
JP2015130174A (ja) * | 2014-01-03 | 2015-07-16 | フィッシャー−ローズマウント システムズ,インコーポレイテッド | プラント監視システムのユーザ表示に用いるための迅速に編集可能な特徴を有する再使用可能なグラフィカル要素 |
WO2016080413A1 (ja) * | 2014-11-19 | 2016-05-26 | 株式会社インフォメックス | データ検索装置、プログラム、及び記録媒体 |
JP2019040287A (ja) | 2017-08-23 | 2019-03-14 | 株式会社日立製作所 | データ分析処理支援装置、及びデータ分析処理支援方法 |
US10366079B1 (en) * | 2015-01-26 | 2019-07-30 | Microstrategy Incorporated | Enterprise connectivity |
JP2021028304A (ja) | 2019-08-09 | 2021-02-25 | 株式会社トクヤマ | クエン酸第二鉄水溶液の製造方法 |
-
2022
- 2022-01-18 EP EP22759165.8A patent/EP4300321A1/en active Pending
- 2022-01-18 JP JP2023502163A patent/JP7481056B2/ja active Active
- 2022-01-18 WO PCT/JP2022/001645 patent/WO2022181122A1/ja active Application Filing
- 2022-01-18 US US18/275,903 patent/US20240118861A1/en active Pending
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040221257A1 (en) * | 2003-05-01 | 2004-11-04 | Lockheed Martin Corporation | Method and apparatus for status display |
JP2010157219A (ja) | 2008-12-31 | 2010-07-15 | Internatl Business Mach Corp <Ibm> | 視覚化ダッシュボードの共同作成方法、システムおよびコンピュータ・プログラム |
US20120144332A1 (en) * | 2010-12-03 | 2012-06-07 | Salesforce.Com, Inc. | Systems and methods for generating a dashboard in a multi-tenant database system environment |
US20150153918A1 (en) * | 2013-12-04 | 2015-06-04 | General Electric Company | System and method for dashboard software maintained by an end user |
JP2015130174A (ja) * | 2014-01-03 | 2015-07-16 | フィッシャー−ローズマウント システムズ,インコーポレイテッド | プラント監視システムのユーザ表示に用いるための迅速に編集可能な特徴を有する再使用可能なグラフィカル要素 |
WO2016080413A1 (ja) * | 2014-11-19 | 2016-05-26 | 株式会社インフォメックス | データ検索装置、プログラム、及び記録媒体 |
US10366079B1 (en) * | 2015-01-26 | 2019-07-30 | Microstrategy Incorporated | Enterprise connectivity |
JP2019040287A (ja) | 2017-08-23 | 2019-03-14 | 株式会社日立製作所 | データ分析処理支援装置、及びデータ分析処理支援方法 |
JP2021028304A (ja) | 2019-08-09 | 2021-02-25 | 株式会社トクヤマ | クエン酸第二鉄水溶液の製造方法 |
Non-Patent Citations (1)
Title |
---|
ANONYMOUS: "Using IBM Cloud Application Business Insights version 1.1.3", CLOUD APPLICATION BUSINESS INSIGHTS, 1 June 2020 (2020-06-01), JP, pages 1 - 132, XP009539278 * |
Also Published As
Publication number | Publication date |
---|---|
US20240118861A1 (en) | 2024-04-11 |
EP4300321A1 (en) | 2024-01-03 |
JPWO2022181122A1 (ja) | 2022-09-01 |
JP7481056B2 (ja) | 2024-05-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11561846B2 (en) | API notebook tool | |
US11216453B2 (en) | Data visualization in a dashboard display using panel templates | |
US10395181B2 (en) | Machine learning system flow processing | |
US10845962B2 (en) | Specifying user interface elements | |
JP7316349B2 (ja) | カスタマイズ可能な企業自動化テストフレームワーク | |
US9547480B2 (en) | Generating application model build artifacts | |
CN104025068B (zh) | 来自多个来源的css定义的冲突解决 | |
US10956505B2 (en) | Data search method, data search apparatus, and non-transitory computer-readable storage medium storing program for data search | |
CN106575298A (zh) | 包含动态内容和陈旧内容的网站的快速呈现 | |
CN111008051A (zh) | 基于多维规则的动态布局 | |
US11252257B2 (en) | Dynamic rest access | |
US9934291B2 (en) | Dynamic presentation of a results set by a form-based software application | |
CN111427577A (zh) | 代码处理方法、装置及服务器 | |
US20220156245A1 (en) | System and method for managing custom fields | |
US8938520B2 (en) | Methods and systems for smart adapters in a social media content analytics environment | |
JP6692289B2 (ja) | 画面情報生成装置、画面情報生成方法、及びプログラム | |
WO2022181122A1 (ja) | 運用支援装置、システム及び方法並びにコンピュータ可読媒体 | |
US11570230B1 (en) | System and method for creating a protocol-compliant uniform resource locator | |
US20220035606A1 (en) | System and method for tailoring a customizer for integration process modeling visual element to a domain specific language for business integrations | |
US11275729B2 (en) | Template search system and template search method | |
JP2004342061A (ja) | 画面とコンポーネント間のリンクを使用したウェブアプリケーションの開発方法および開発支援装置 | |
US11995296B2 (en) | System and method for creating a single-entity protocol-compliant uniform resource locator | |
US20230350965A1 (en) | System and Method for Validating a Protocol-Compliant Uniform Resource Locator | |
US20230367471A1 (en) | System and Method for Specifying Properties for a Protocol-Compliant Uniform Resource Locator | |
WO2023162260A1 (ja) | 環境構築支援装置、システム及び方法、並びに、コンピュータ可読媒体 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22759165 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 18275903 Country of ref document: US Ref document number: 2023502163 Country of ref document: JP |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112023016087 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112023016087 Country of ref document: BR Kind code of ref document: A2 Effective date: 20230810 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022759165 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2022759165 Country of ref document: EP Effective date: 20230925 |