JP2010066903A - Information processor, program registration/start method and registration/start program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processor, a program registration/start method and a registration/start program, allowing simultaneous materialization of both elimination of dependency relation between programs started in different layers and facilitation of registration of a program. <P>SOLUTION: The information processor has: a first mediation means to be started in a first layer on a framework; a second mediation means to be started in a second layer on the framework; a communication means for performing communication between the first mediation means and the second mediation means for receiving messages from first and second programs started in the first layer and the second layer; and a registration reception means for receiving registration of the second program into the second layer, and storing setting information necessary to start the second program in the second layer in a data management means. The first mediation means starts the second mediation means according to the setting information, the second mediation means starts the second program according to the setting information, and the second program operates according to the setting information. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an information processing apparatus, a program registration activation method, and a registration activation program, and more particularly to an information processing apparatus, a program registration activation method, and a program activation program to which a predetermined framework based on one program language is applied.

  In recent years, some image forming apparatuses as an example of information processing apparatuses can plug in necessary modules. A plug-in is a function for adding functions to various applications using a small program (plug-in). Note that the image forming apparatus is a generic name for, for example, a copy, a printer, a scanner, a facsimile machine, and a multifunction machine.

  FIG. 1 is a simplified diagram showing a software configuration of an image forming apparatus in which necessary modules can be plugged in. The image forming apparatus 1 applies an OSGi (Open Service Gateway initiative) framework 11.

  The OSGi framework 11 is a standardization technology based on the OSGi alliance, and is an open software componentization technology based on the Java (registered trademark) language. In an image forming apparatus to which the OSGi framework 11 is applied, Java (registered trademark) language software is installed in units of software components (bundles) called bundles.

  The image forming apparatus 1 in FIG. 1 can be configured with functions as bundles, and can also update, customize, and maintain functions by installing bundles.

  The image forming apparatus 1 in FIG. 1 includes a CVM (Compact Virtual Machine) 10 for executing Java (registered trademark) software, an OSGi framework 11 for managing bundles, a bundle 12, and a Java (registered trademark) language. A component 13 which is software and a daemon 14 which is native language software are included.

In the OSGi framework 11 of the image forming apparatus 1 in FIG. 1, the component 13 uses the bundle 12 to plug in the component 13 to the Java (registered trademark) layer. Note that when the daemon 14 which is native language software is installed in the native layer, the conventional image forming apparatus 1 is performed in such a manner that the daemon 14 is included in the bundle 12, for example. It is easy to register the daemon 14 by installing the daemon 14 which is native language software in the native layer so that the daemon 14 is included in the bundle 12. Note that an image forming apparatus 1 to which the OSGi framework 11 is applied is conventionally known (see, for example, Patent Document 1).
Japanese Patent Laid-Open No. 2007-110589

  However, in the image forming apparatus 1 of FIG. 1, a problem occurs when the daemon 14 installed in the Native layer transmits and receives messages to and from the Java (registered trademark) layer component 13.

  When the daemon 14, which is native language software, is installed in the native layer in such a manner that the daemon 14 is included in the bundle 12, method calls between the Java (registered trademark) layer and the native layer are mainly JNI (Java Native Interface). Done in JNI is an API (Application Program Interface) for calling a method between a component 13 developed in Java (registered trademark) language and a daemon 14 developed in Native language.

  When calling a method with JNI, it is necessary to specify the class name and method name of the other party. Therefore, the daemon 14 needs to hard-code the specification, and the dependency relationship with the component 13 of the calling party can be made. . For this reason, the image forming apparatus 1 of FIG. 1 has a problem in that it is difficult to cope with version upgrades and vulnerability countermeasures that are likely to be in the daemon 14 developed in the Native language.

  In other words, the conventional image forming apparatus 1 eliminates the dependency relationship between the component 13 developed in the Java (registered trademark) language and the daemon 14 developed in the Native language, and makes the daemon 14 easily in the Native layer. It was difficult to balance installation.

  The present invention has been made in view of the above points, and is an information processing apparatus, a program registration activation method, and a registration that can eliminate the dependency between programs activated in different layers and facilitate program registration. The purpose is to provide a startup program.

  In order to solve the above problem, the present invention is an information processing apparatus to which a predetermined framework based on one program language is applied, and the first program described in the one program language is activated. First mediating means activated in the first layer on the framework and second mediating means activated in the second layer on the framework where the second program written in another programming language is activated Between the first mediating means for accepting a message from the first program activated in the first layer and the second mediating means for accepting a message from the second program activated in the second layer. And a communication unit for receiving the registration of the second program in the second layer and setting information necessary for starting the second program in the second layer to the data management unit Existing registration acceptance means, and after starting the framework, the first mediation means activates the second mediation means according to the setting information stored in the data management means, and the second mediation means Starts the second program according to the setting information, and the second program operates according to the setting information.

  In addition, what applied the component, expression, or arbitrary combination of the component of this invention to a method, an apparatus, a system, a computer program, a recording medium, a data structure, etc. is also effective as an aspect of this invention.

  According to the present invention, it is possible to provide an information processing apparatus, a program registration activation method, and a registration activation program capable of eliminating the dependency relationship between programs activated in different layers and facilitating program registration.

  Next, the best mode for carrying out the present invention will be described based on the following embodiments with reference to the drawings.

  FIG. 2 is a simplified diagram illustrating a software configuration of the image forming apparatus according to the present exemplary embodiment. The image forming apparatus 2 illustrated in FIG. 2 includes a CVM 10, an OSGi framework 11, a daemon 14, an http service component (http service CMP) 21, a data management component 22, and an OSGi framework 11 having functions such as various applications. A component 23 such as a print management component and a FAX component, a mediation component 24, and a mediation daemon 25.

  In the image forming apparatus 2 in FIG. 2, the same parts as those in the image forming apparatus 1 in FIG. The http service component 21 is an example of a reception port when the daemon 14 is added and registered. The data management component 22 manages data such as various setting information. The data management component 22 is responsible for storing data such as various setting information. The component 23 is a partner with which the daemon 14 ultimately wants to send and receive messages.

  The mediation component 24 accepts a message on the Java (registered trademark) layer side to bridge a message between the Java (registered trademark) layer and the native layer. The intermediary daemon 25 accepts messages on the native layer side when bridging messages between the Java (registered trademark) layer and the native layer.

  As shown in FIG. 2, in the image forming apparatus 2, the mediation component 24 is activated in the Java (registered trademark) layer, and the mediation daemon 25 is activated in the Native layer. This is because it is necessary to fix the JNI function with the partner when communicating between the Java (registered trademark) layer and the Native layer. By fixing the JNI function between the mediation component 24 and the mediation daemon 25, a user such as the daemon 14 that communicates between the Java (registered trademark) layer and the native layer can communicate without being aware of the JNI. It becomes.

  In the image forming apparatus 1 shown in FIG. 1, various functions can be added according to the plug-in concept of the component 13. However, in many cases, the daemon 14, which is native language software activated in the native layer, cannot directly call the I / F provided by Java (registered trademark). Cannot support adding functions.

  The image forming apparatus 2 according to the present exemplary embodiment illustrated in FIG. 2 includes a mediating component 24 and a mediating daemon that absorb the dependency of the Java (registered trademark) layer and the native layer on the Java (registered trademark) layer and the native layer, respectively. By starting 25, there is no dependency between the Java (registered trademark) layer and the native layer, and a mechanism for dynamically adding the daemon 14 that is native language software in a form corresponding to the OSGi framework 11 is provided. To do.

  FIG. 3 is a class diagram of the software configuration of the image forming apparatus according to the present exemplary embodiment. The http service component 21 acquires registration data 31. The registration data 31 is a set of setting information described in the program of the daemon 14 and XML. The http service component 21 decomposes the registration data 31 into the daemon 14 program and setting information described in XML, and installs the daemon 14 program. The http service component 21 analyzes the contents of the setting information described in XML, creates a profile of the daemon 14 and a profile of the mediation daemon 25, and registers them in the data management component 22.

  Further, the mediation component 24 acquires the profile of the daemon 14 and the profile of the mediation daemon 25 from the data management component 22, and generates a configuration file 32 for the mediation daemon 25 and a configuration file 33 for the daemon 14. The mediation daemon 25 refers to the setting file 32 for the mediation daemon 25 and activates the daemon 14. The daemon 14 refers to the configuration file 33 for the daemon 14 and operates according to the configuration file 33 for the daemon 14.

  After being activated, the mediation component 24 receives a message from the Java (registered trademark) layer side and transmits the message to the Java (registered trademark) layer side. The mediation component 24 receives a message from the native layer side via the mediation daemon 25, and transmits the message to the native layer side via the mediation daemon 25.

  The mediation daemon 25 receives a message from the daemon 14 on the native layer side, and transmits the message to the Java (registered trademark) layer side via the mediation component 24. The mediation daemon 25 receives a message from the Java (registered trademark) layer side via the mediation component 24 and transmits the message to the daemon 14 on the native layer side.

(Process when registering daemon 14)
FIG. 4 is a simplified diagram showing processing at the time of daemon registration. When the user registers the daemon 14, the registration data 31 is installed. The registration data 31 is a set of setting information 42 described in the program 41 of the daemon 14 and XML. The content of the registration data 31 is an example. For example, the registration data 31 may include information defined in advance other than the program 41 of the daemon 14 and the setting information 42 described in XML, or may be encrypted or uniquely formatted.

  FIG. 5 is a configuration diagram showing an example of setting information described in XML. The setting information in FIG. 5 has a configuration including an information part 51 for creating a profile of the mediation daemon 25 and an information part 52 for creating a profile of the daemon 14. In the information part 51, information (for example, a file path, a start program name, a start option, etc.) for the mediation daemon 25 to start the daemon 14 is described. In the information portion 52, information for operating the daemon 14 (for example, the path, file name, setting contents, etc. of the setting file 33 for the daemon 14) is described.

  When the registration data 31 is installed, a mediation component 24 for the daemon 14 is generated. The http service component 21 decomposes the registration data 31 into a program of the daemon 14 and setting information described in XML. The http service component 21 places the program of the daemon 14 at a predetermined location. In addition, the http service component 21 analyzes the contents of the setting information described in XML, creates a profile of the daemon 14 and a profile of the mediation daemon 25, and registers them in the data management component 22. The http service component 21 registers with the OSGi framework 11 so that the mediation daemon 25 is generated after the next activation.

  FIG. 6 is a sequence diagram showing processing at the time of daemon registration. When registering the daemon 14, the user proceeds to step S <b> 1 and installs the registration data 31. When the registration data 31 is installed, the http service component 21 proceeds to step S2, parses the acquired registration data 31, and decomposes it into a program of the daemon 14 and setting information described in XML.

  In step S 3, the http service component 21 analyzes the contents of the setting information described in XML, creates a profile of the daemon 14, and registers it in the data management component 22. In step S4, the http service component 21 analyzes the contents of the setting information described in XML, creates a profile of the mediation daemon 25, and registers it in the data management component 22.

In step S5, the http service component 21 arranges the program of the daemon 14 at a predetermined location. In step S6, the http service component 21 generates a mediation component 24. In step S7, the http service component 21 registers with the OSGi framework 11 so that the mediation daemon 25 is generated after the next activation.
(Processing when the mediation daemon 24 is started)
FIG. 7 is a simplified diagram showing processing at the start of the mediation daemon. When the OSGi framework 11 is activated, the mediation component 24 acquires the profile of the daemon 14 and the profile of the mediation daemon 25 from the data management component 22. The mediation component 24 generates a setting file 32 for the mediation daemon 25 from the acquired profile of the mediation daemon 25. Further, the mediating component 24 generates a configuration file 33 for the daemon 14 from the acquired profile of the daemon 14.

  In the case of the setting information of FIG. 5, the mediation component 24 generates a setting file 33 for the daemon 14 as shown in FIG. FIG. 8 is a configuration diagram showing an example of a configuration file for daemons. After generating the configuration file 32 for the mediation daemon 25 and the configuration file 33 for the daemon 14, the mediation component 24 activates the mediation daemon 25.

  FIG. 9 is a sequence diagram illustrating a process when the mediation daemon is activated. When the OSGi framework 11 is activated, the mediation component 24 proceeds to step S11 and acquires the profile of the mediation daemon 25 from the data management component 22. In step S 12, the mediation component 24 generates a setting file 32 for the mediation daemon 25 from the profile of the mediation daemon 25.

In step S 13, the mediation component 24 acquires the profile of the daemon 14 from the data management component 22. In step S 14, the mediation component 24 generates a configuration file 33 for the daemon 14 from the profile of the daemon 14. In step S15, the mediation component 24 activates the mediation daemon 25.
(Initial processing after start of mediation daemon 24)
FIG. 10 is a simplified diagram showing the initial processing after the activation of the mediation daemon. Immediately after being activated, the mediation daemon 25 acquires the settings for operating itself from the configuration file 32 for the mediation daemon 25. The setting file 32 for the mediation daemon 25 includes a description regarding the daemon 14 that the mediation daemon 25 starts. The mediation daemon 25 starts the daemon 14 according to the description of the setting file 32 for the mediation daemon 25.

  The daemon 14 refers to the configuration file 33 for the daemon 14 and operates according to the configuration file 33 for the daemon 14. Thereafter, the broker daemon 25 enters a message reception waiting state. Details of the message will be described later.

  FIG. 11 is a sequence diagram showing an initial process after the activation of the mediation daemon. Immediately after being activated, the mediation daemon 25 proceeds to step S21, and obtains the settings for operating itself from the configuration file 32 for the mediation daemon 25. The setting file 32 for the mediation daemon 25 includes a description regarding the daemon 14 that the mediation daemon 25 starts.

In step S22, the mediation daemon 25 activates the daemon 14 in accordance with the description in the configuration file 32 for the mediation daemon 25. In step S23, the daemon 14 refers to the setting file 33 for the daemon 14 and operates according to the setting file 33 for the daemon 14. Thereafter, the broker daemon 25 enters a message reception waiting state.
(Overall processing from the start of the mediation daemon 24 to the start of the daemon 14)
FIG. 12 is a sequence diagram showing the entire process from the start of the mediation daemon to the start of the daemon. Steps S11 to S23 collectively represent the sequence diagrams of FIGS. The description is omitted here.

  Proceeding to step S24 following step S23, the daemon 14 registers itself in the mediation daemon 25. When the daemon 14 ends, the process proceeds to step S25, and requests the registration daemon 25 to cancel the registration.

  FIG. 13 is a simplified diagram illustrating a process in which the daemon registers itself with the intermediary daemon. The daemon 14 of FIG. 13 is started in step S22, and after referring to the setting file 33 for the daemon 14 in step S23, registers itself in the mediation daemon 25.

  The message means between the daemon 14 and the mediation daemon 25 is not particularly limited. For example, the message means between the daemon 14 and the mediation daemon 25 may be an inter-process communication process such as communication using Unix (registered trademark) Domain Socket. In this case, a conf mechanism is used for a communication destination socket file name and the like.

  When the daemon 14 is registered, the mediation daemon 25 assigns a daemon identification ID. Thereafter, the daemon 14 exchanges messages using the daemon identification ID. The mediation daemon 25 distinguishes the daemon 14 by the daemon identification ID.

FIG. 14 is a simplified diagram illustrating a process in which a daemon cancels its own registration from an intermediary daemon. When the daemon 14 of FIG. 14 ends, the process proceeds to step S25, and requests the broker daemon 25 to delete its own registration. When the registration of the daemon 14 is deleted, the mediation daemon 25 cancels the allocation of the daemon identification ID and notifies the daemon 14 to that effect.
(Communication processing after starting the daemon 14)
FIG. 15 is a simplified diagram showing communication processing after the daemon is started. The mediation daemon 25 in FIG. 15 provides an I / F to the daemon 14 and mediates messages. The mediation component 24 serves as an entrance for receiving a message from the mediation daemon 25. Further, the mediation component 24 transmits / receives a message to / from another Java (registered trademark) layer according to the message. Note that Java (registered trademark) -Native conversion by JNI is performed between the mediation daemon 25 and the mediation component 24.

  FIG. 16 is a sequence diagram showing communication processing after the daemon is started. A message from the daemon 14 to the Java layer is transmitted as in steps S31 to S33. With the reception of data from the network as a trigger, the daemon 14 proceeds to step S31 and transmits the message (data) received from the network to the mediation daemon 25.

  In step S32, the mediation daemon 25 transmits a message to the mediation component 24 by JNI call. In step S33, the mediation component 24 transmits a message to a predetermined component 23 on the OSGi framework 11 as necessary.

  Messages from the Java layer to the daemon 14 / network are transmitted as in steps S34 to S36. In step S34, the mediation component 24 receives a message addressed to the daemon 14 from the component 23 in the Java layer.

In step S35, the mediation component 24 transmits a message to the mediation daemon 25 by a JNI call. In step S 36, the mediation daemon 25 transmits a message to the daemon 14. It should be noted that the exchange shown in the sequence diagram of FIG. 16 has the same movement including the registration request of the daemon 14.
(Application to image forming apparatus with service layer)
The present invention can also be applied to an image forming apparatus configured as shown in FIG. FIG. 17 is a simplified diagram showing a software configuration of an image forming apparatus having a service layer. The print application 100 corresponds to the daemon 14 in FIG. The service layer 110 corresponds to the Java layer in FIG. The OSGi framework 11 corresponds to JSDK Environment 120.

  The http service 111 corresponds to the http service component 21 in FIG. The data management service 112 corresponds to the data management component 22 of FIG. Modules 113 such as a print service and a FAX service on the JSDK Environment 120 having functions such as various applications correspond to the components 23 such as the print management component and the FAX component in FIG.

  Therefore, the image forming apparatus of FIG. 17 can achieve the same effect as the present invention by providing a configuration corresponding to the mediation component 24 and the mediation daemon 25 of FIG.

  The present invention is not limited to the specifically disclosed embodiments, and various modifications and changes can be made without departing from the scope of the claims.

FIG. 6 is a simplified diagram illustrating a software configuration of an image forming apparatus in which a necessary module can be plugged in. FIG. 2 is a simplified diagram illustrating a software configuration of the image forming apparatus according to the present exemplary embodiment. FIG. 3 is a class diagram in the software configuration of the image forming apparatus according to the present exemplary embodiment. It is the simple figure which showed the process at the time of registration of a daemon. It is a block diagram which shows an example of the setting information described by XML. It is the sequence diagram which showed the process at the time of registration of a daemon. It is the simple figure which showed the process at the time of starting of a mediation daemon. It is a block diagram which shows an example of the setting file for daemons. It is the sequence diagram which showed the process at the time of starting of a mediation daemon. It is the simplified diagram which showed the initial process after starting of a mediation daemon. It is the sequence diagram which showed the initial process after starting of a mediation daemon. It is the sequence diagram which showed the whole process from starting of a mediation daemon to starting of a daemon. FIG. 11 is a simplified diagram illustrating a process for a daemon to register itself with an intermediary daemon. FIG. 10 is a simplified diagram illustrating a process in which a daemon cancels its own registration from an intermediary daemon. It is the simplified diagram which showed the communication processing after starting of a daemon. It is the sequence diagram which showed the communication process after starting of a daemon. 2 is a simplified diagram illustrating a software configuration of an image forming apparatus having a service layer. FIG.

Explanation of symbols

1, 2 Image forming device 10 CVM (Compact Virtual Machine)
11 OSGi (Open Service Gateway initiative) Framework 12 Bundle 13, 23 Component 14 Daemon
21 http service component (http serviceCMP)
22 Data Management Component 24 Mediation Component 25 Mediation Daemon 31 Registration Data 32 Configuration File for Mediation Daemon 25 33 Configuration File for Daemon 14 41 Program for Daemon 14 42 Configuration Information Described in XML

Claims (17)

An information processing apparatus to which a predetermined framework based on one programming language is applied,
First mediating means activated in a first layer on the framework in which the first program written in the one program language is activated;
Second mediating means activated in a second layer on the framework where a second program written in another programming language is activated;
Communication is performed between first mediating means for accepting a message from the first program activated in the first layer and second mediating means for accepting a message from the second program activated in the second layer. Communication means;
Registration acceptance means for accepting registration of the second program in the second layer and storing setting information necessary for starting the second program in the second layer in a data management means;
After the framework is activated, the first mediating means activates the second mediating means according to the setting information stored in the data management means, and the second mediating means executes the second program according to the setting information. An information processing apparatus that is activated and operates according to the setting information. The registration accepting means obtains registration data including the second program and the setting information;
Means for decomposing the registration data into the second program and the setting information, storing the setting information in the data management means, and placing the second program in a second layer on the framework. The information processing apparatus according to claim 1. The first mediating means receives a message from the first program activated in the first layer; and
Means for sending a message to the first program activated in the first layer;
Means for receiving a message from the second program activated in the second layer via the second mediating means;
Means for transmitting a message to the second program activated in the second layer via the second mediating means;
The information processing apparatus according to claim 1, further comprising: The first mediating means obtains the setting information for the second mediating means and the setting information for the second program from the data management means to obtain the setting file for the second mediating means and the second program. A means for generating a configuration file;
The second mediating means includes means for referring to a setting file for the second mediating means;
Means for starting the second program according to the setting file for the second mediating means;
The information processing apparatus according to claim 3, further comprising: The second mediating means comprises means for receiving a message from the second program activated in the second layer;
Means for sending a message to the second program activated in the second layer;
Means for receiving a message from the first program activated in the first layer via the first mediation means;
Means for transmitting a message to the first program activated in the first layer via the first mediating means;
The information processing apparatus according to claim 4, further comprising: The second program refers to a setting file for the second program;
6. The information processing apparatus according to claim 4, further comprising means for operating according to the setting file for the second program. After the second program is activated, it registers itself in the second mediation means,
The information processing apparatus according to claim 1, wherein the second mediating unit assigns an identifier to the registered second program and distinguishes the second program using the identifier.   8. The communication means is an application program interface (API) that enables message transmission / reception between the first mediation means and the second mediation means. Information processing device.   The one program language is a Java (registered trademark) language, the other program language is an open source software (OSS), and the framework is an OSGi framework based on the Java (registered trademark) language. The information processing apparatus according to any one of claims 1 to 8.   The information processing apparatus according to claim 1, wherein the communication unit is JNI (Java Native Interface).   2. The setting information is written in a markup language, and the setting information for the second mediating means and the setting information for the second program are analyzed from the contents of the markup language. The information processing apparatus as described in any one of thru | or 10. A program registration start method executed by an information processing apparatus applying a predetermined framework based on one program language,
The information processing apparatus includes:
First mediating means activated in a first layer on the framework in which the first program written in the one program language is activated;
Second mediating means activated in a second layer on the framework where a second program written in another programming language is activated;
Communication is performed between first mediating means for accepting a message from the first program activated in the first layer and second mediating means for accepting a message from the second program activated in the second layer. Communication means;
Registration accepting means for accepting registration of the second program in the second layer,
The registration accepting unit accepting registration of the second program in the second layer;
The registration accepting means storing in the data management means setting information necessary for starting the second program in the second layer;
After the framework is activated, the first mediation means activates the second mediation means according to the setting information stored in the data management means;
The second mediating means starting the second program according to the setting information;
And a step of operating the second program according to the setting information. The registration receiving means obtains registration data including the second program and the setting information;
Disassembling the registration data into the second program and the setting information, storing the setting information in the data management means, and placing the second program in a second layer on the framework. The program registration starting method according to claim 12.   14. The program registration activation according to claim 12, wherein the communication means is an API (Application Program Interface) that enables message transmission / reception between the first mediation means and the second mediation means. Method.   The one program language is a Java (registered trademark) language, the other program language is an open source software (OSS), and the framework is an OSGi framework based on the Java (registered trademark) language. 15. The program registration start method according to claim 12, wherein the program registration is started.   16. The program registration start method according to claim 12, wherein the communication unit is JNI (Java Native Interface).   A registration activation program for causing a computer to execute the program registration activation method according to any one of claims 12 to 16.

Images