JP2011065495A - Network system, method, and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To collectively manage communication between a development network environment and an operational network environment. <P>SOLUTION: A distribution server 12 includes a transfer processing part 121 which transmits, to a neutral server 21, a program module to be released to the operational network environment 3 and makes a request for releasing the program module. The neutral server includes: an approval processing part 214 which receives an input of information which indicates that release of the program module receiving the release request from the distribution server is approved by a prescribed approver; a log storage part 213 which stores approval history data based on the input received by the approval processing part; and a delivery directory 212 which distributes the program module, whose release is approved by the approver, to a release server. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a network system having a development network environment and an operation network environment.

  Conventionally, in a system constructed in an environment where the development environment and the operation environment are independent from each other, a storage medium is provided between these separate environments, so that files accumulated on the development environment side are transferred to the operation environment side. The technique to make is known (for example, patent document 1).

  In the technology shown in Patent Document 1, the information of the interface repository IR defined in the development environment is extracted as an IDL file and stored in a storage medium in a distributed object environment conforming to CORBA, and stored in the storage medium. By developing an IDL file in a completely different operating environment and registering it as an interface repository IR in that environment, it is possible to construct a development environment and an operating environment as different environments.

JP-A-11-327881

  By the way, in recent years, in order to comply with the so-called Japanese version of the SOX law, requirements for separation of duties between developers and operators and requirements for auditing have become stricter. For this reason, the development network environment and the operation network environment are clearly separated, and audit logs are collected when an application is released from the development network environment to the operation network environment. It is necessary to manage the exchanges between them.

  Accordingly, an object of the present invention is to collectively manage exchanges between the development network environment and the operation network environment.

  A network system according to an embodiment of the present invention includes a development network environment for performing program development, including a distribution server, and an operation including a plurality of business servers for executing program modules developed in the development network environment. A network system comprising a network environment and a neutral server connected to the development network environment and the operation network environment, wherein the distribution server sends a program module for releasing to the operation network environment to the neutral server Information indicating that the neutral server has approved the release of the program module that has received the release request from the distribution server from a predetermined approver; of Receiving means for receiving a force, approval history storage means for storing approval history data based on an input received by the receiving means, and means for transmitting a program module released and approved by the approver to the release server. The release server includes an installation unit that stores the release-approved program module transmitted from the neutral server in another device in the operation network environment so that the plurality of business servers can execute the module.

  In a preferred embodiment, the operational network environment further includes a shared data storage unit connected to the plurality of business servers, and the installation unit stores the release approved program module in the shared data storage unit. The plurality of business servers execute the approved program module with reference to the shared data storage unit.

  In a preferred embodiment, the neutral server obtains an installation result of the approved program module by the installation unit from the release server and stores it in the approval history storage unit.

  According to the present invention, it is possible to collectively manage exchanges between the development network environment and the operation network environment.

1 is an overall configuration diagram of a network system according to an embodiment. It is a figure which shows an example of the log memorize | stored in the log memory | storage part. It is a figure for demonstrating the function of an approval expansion | deployment part. It is a figure which shows an example of the data structure inside NAS. It is explanatory drawing for demonstrating an example of the operation | movement in the normal release process of the network system concerning this embodiment. It is an example of the flowchart which shows the expansion | deployment process of the expansion | deployment process part in the normal release process. It is explanatory drawing for demonstrating an example of the operation | movement in the emergency release process of the network system concerning this embodiment. It is explanatory drawing for demonstrating an example of the operation | movement in the switch-back process of the network system concerning this embodiment. It is an example of the flowchart which shows the expansion | deployment process of the expansion | deployment process part in a switchback process.

  Hereinafter, as an example of a network system according to an embodiment of the present invention, a system that performs a release process of a program module to an operation network environment of a program module developed in a development network environment will be described as an example, with reference to the drawings. explain.

  The network system according to the present embodiment includes a development network environment 1 for performing program development, which includes a distribution server 12, and an operation including a plurality of business servers 33 that execute program modules developed in the development network environment 1. A network environment 3 and a neutral server 21 connected to the development network environment 1 and the operation network environment 3 are provided. The operation network environment 3 further includes a shared data storage unit connected to the plurality of business servers 33.

  FIG. 1 is an overall configuration diagram of a network system according to the present embodiment. The configuration of this network system will be described below with reference to FIG.

  The network system includes a development network environment 1, a neutral network environment 2, and an operation network environment 3, as shown in FIG.

  The development network environment 1, the operation network environment 3, and the neutral network environment 2 are independent network systems. In each of these network systems, a server, a storage device, and the like are connected in a network such as a LAN.

  The development network environment 1 is an environment on the program module developer side. For example, as shown in FIG. 1, one or a plurality of development application servers 11 (hereinafter referred to as development side AP servers) and a distribution server 12 are provided. Prepare.

  The development-side AP server 11 is a server used for application development, for example. The development side AP server 11 stores program modules of applications developed by the developer. Only one development-side AP server 11 may be installed per development network environment, or a plurality of development-side AP servers 11 may be installed.

  The distribution server 12 includes a distribution server 12 as a release request unit that transmits a program module to be released to the operation network environment 3 to the neutral server 21 and requests release of the program module.

  The distribution server 12 includes a transfer processing unit 121 and an extraction unit 122.

  When the release request from the developer that “a program module of a predetermined version of a predetermined application is released to the operation network environment 3” is received by the distribution server 12 through the terminal device 4, the extraction unit 122 For example, a predetermined version of a program module (hereinafter referred to as a target module) of a predetermined application requested to be released from the developer is extracted from the development-side AP server 11. At this time, the target module is not the entire program module group of the predetermined version of the predetermined application requested by the developer, but the version in which the application is currently operating in the operation network environment 3 (hereinafter referred to as the current version). ) And only the difference program module.

  The transfer processing unit 121 requests the neutral server 21 to release the target module by transferring the target module to the neutral server 21.

  For example, the neutral server 121 archives the target module and transfers it to the neutral server 21 as an archive file.

  The archive file may be created for each predetermined unit, for example, for each business. The archive file has, for example, the desired release date of the target module included in the archive file, the application name and version name of the target module, and the release number when a plurality of target modules are released with one archive file. May be described. The transfer is performed in the FTP format, for example.

  The neutral network environment 2 relays when releasing a program module from the development network environment 1 to the operation network environment 3, and performs collective management of the release of the program module from the development network environment 1 to the operation network environment 3. It is a network system.

  In the neutral network environment 2, for example, as shown in FIG. 1, a neutral server 21 is installed.

  The neutral server 21 receives an input of information indicating that the release of the program module for which the release request from the distribution server 12 has been accepted is received from a predetermined approver, and the accepting unit accepts the approval processing unit 214 as an accepting unit. A log storage unit 213 serving as an approval history storage unit that stores approval history data (log) based on the input, and a transfer processing unit 215 serving as a unit that transmits the program module released and approved by the approver to the release server 31. . The neutral server 21 may also include a moving directory 211 and a distribution directory. Further, the neutral server 21 acquires the installation result of the program module approved by the installation unit described later from the release server 31 and stores it in the log storage unit.

  The moving directory 211 is a directory in which the archive file transmitted from the distribution server 12 is temporarily saved.

  The distribution directory 212 is a directory in which an approval archive file, which will be described later, moved from the migration directory 211 by the approval processing unit 214 is stored, for example.

  The approval processing unit 214 performs an approval process for the target module that has received the release request.

  For example, the approval processing unit 214 receives approval information indicating whether or not the target module has been approved by the approver from the terminal device 4. Here, the approval information means that if the approver receives a request from the developer separately from this system, the approver receives the request that the target module should be released to the operation network environment 3 side. This is information indicating whether or not the request has been approved in archive units. Here, the approver approves in units of archive files. However, instead of approving in units of archive files, the approver may approve in units of program modules (target modules) in the archive file.

  When the archive file is temporarily stored in the moving directory 211 and the approval processing unit 214 receives approval information indicating that the archive file has been approved, the approval processing unit 214 reads the approved archive file (hereinafter referred to as the approved archive file). , The approval archive file) is moved to the distribution directory 212. When the approval processing unit 214 receives the approval information indicating that the moving directory 211 receives the archive file and the archive file is not approved, the approval processing unit 214 sets the archive file in the moving directory 211. Is discarded.

  Although details will be described later, the approval processing unit 214 receives a completion notification from the expansion processing unit 313 when the release processing is completed. Then, the approval processing unit 214 records the content of the received completion notification in the log file 40 of the log storage unit 213.

  The transfer processing unit 215 transfers the approval archive file stored in the distribution directory 212 to the release server 31.

  For example, the transfer processing unit 215 has a timer transmission function, and transfers the approval archive file received by the distribution directory 212 to the release server 31 in the operation network environment 3 at the reserved time reserved in advance by the timer. To do. The transfer is performed in the FTP format, for example.

  In the log storage unit 213, for example, a log including information about processing by the approval processing unit 214 is stored. For example, FIG. 2 shows an example of the log file 40 stored in the log storage unit 213. The log file 40 includes a date and time 41 indicating when the approval processing unit 214 received the approval information, an approver 42 indicating who made the determination on the approval information, and an archive indicating which archive file is the approval information. Approval information 44 indicating whether or not the content of the file 43 and the approval information has been approved, a completion notification result 45 in which the content of a completion notification result to be described later is stored when the approval is made, and release processing Is a “normal” process, an “emergency” process, or a release type 46 indicating whether a version “switchback” process has been performed instead of the release process.

  For example, as shown in FIG. 1, the operation network environment 3 includes a release server 31, a NAS (Network Attached Storage) 32, a plurality of business servers 33, and an operation monitoring server 34.

  The release server 31 includes an installation unit that stores the release-approved program module transmitted from the neutral server 21 in another device in the operation network environment 3 so that the plurality of business servers 33 can execute it. The other device is a shared data storage unit such as NAS or a local storage unit of each business server 33. In addition, the plurality of business servers 33 execute the approved program module with reference to the shared data storage unit by the installation unit.

  As shown in FIG. 1, for example, the release server 31 includes a reception directory 311, a pool directory 312, a development processing unit 313, and a monitoring unit 314.

  The release server 31 expands the approved archive file transferred from the neutral server 21, takes out the target module, and reflects the target module in the NAS 32. After reflecting the target module on the NAS 32, the release server 31 sends a completion notification that records whether the reflection to the NAS 32 is completed normally or abnormally, to the approval server of the business server 33 and the neutral network environment 2. Send to 214.

  The reception directory 311 is a directory for temporarily storing the approved archive file transferred from the distribution directory 212 of the neutral server 21.

  The reception directory 311 is a directory for temporarily storing the flag file transmitted from the business server 33. Here, the flag file is a file transmitted from a server such as the business server 33 in response to an instruction from the operation monitoring server 34 to be described later as a cue for release start. The flag file is registered in the business server 33 from the terminal device 4 by a developer, an approver, or an operator. In the flag file, for example, the name of the archive file requested to be released and the IP address of the business server 33 to which a completion notification is sent after the reflection to the NAS 32 is described.

  The pool directory 312 stores the approval archive file transferred from the reception directory 311.

  The monitoring unit 314 constantly monitors the reception directory 311 and the pool directory 312. For example, when the approval archive file is transferred from the distribution directory 212 and stored in the reception directory 311, the monitoring unit 314 moves the stored approval archive file from the reception directory 311 to the pool directory 312.

  When the reception directory 311 receives the flag file from the business server, the monitoring unit 314 selects the approval archive file name described in the flag file from the approval archive files stored in the pool directory 312. Is sent to the expansion processing unit 313.

  FIG. 3 is a diagram for explaining the function of the approval development unit 313.

  The expansion processing unit 313 receives the notification from the monitoring unit 314, expands the notified approval archive file, and takes out the target module.

  For example, the expansion processing unit 313 identifies the application name and version name of the target module based on the approved archive file name notified from the monitoring unit 314. Then, an update directory d of the identified application name and version name is created in the temporary storage unit 313a of the expansion processing unit 313. The created update directory d name becomes the new version name after update.

  Further, the development processing unit 313 copies the current version of the program module group of the target application from the NAS 32 into the update directory d of the temporary storage unit 313a, and saves the target module in the folder. As described above, the target module after the expansion process is a program module that is a difference with respect to the program module group of the current version of the target application. Therefore, the target application is stored in the update directory d by the above process. A new version of the program module group after the update is stored.

  Further, the expansion processing unit 313 reflects the update directory d created in the temporary storage unit to the NAS 32. The reflection on the NAS 32 will be described later.

  When the release processing is completed, the expansion processing unit 313 creates a completion notification and sends the created completion notification to the business server 33 and the approval processing unit 214 of the neutral server 21. The completion notification will be described later.

  The NAS 32 centrally manages program modules for each version of one or more applications.

  The NAS 32 has a directory structure as shown in FIG. When an application is executed on the business server 33, the part of the directory group 50 indicated by the dotted frame is mounted on the business server 33. The mounting on the business server 33 will be described later.

  A directory group 50 within a dotted line is a directory group 50 for one application 501, and includes an (App Name) directory 502 indicating a business name, and two (prod) and (Sys ID) directories 503 and 504 indicating a group. A (www) directory 505 indicating a subsystem, a (x86_6) directory 506 indicating architecture hardware, a (RHEL) directory 507 indicating an OS name, and a current directory 508.

  The directory 507 indicating the OS name includes one or a plurality of directories 509 (509a and 509b) in which the directory name is the version of the program. Each directory 509a and 509b stores a program module group 510 of that version. The current directory 508 is a virtual directory, and a symbolic link 511 is pasted from the current directory 508 to a directory having a current version name (the directory 509b of version 2.0 in FIG. 4). Thus, if the user designates the current directory 508, the current version of the application can be used.

  The update processing unit 313 reflects the update directory d in the NAS 32 at a predetermined position. Here, the predetermined position is, for example, a lower position of the (RHEL) folder 507 indicating the OS name. That is, each module in the update directory d is stored in the directory 509 having the version name corresponding to the update directory d reflected by the expansion processing unit 313. A symbolic link 511 of the current directory 508 is attached to the directory 509 having the reflected version name.

  When the reflection of the update directory d described above is completed, the business server 33 is notified of completion from the expansion processing unit 313. The completion notification describes whether the release of the approved archive file has ended normally or has ended abnormally.

  Each business server 33 mounts a directory group 50 in the NAS 32 in order to execute a predetermined application. The directory group 50 is mounted on a business unit basis, for example. Each business server 33 is assigned a business. Each business server 33 mounts a directory group 50 related to the business assigned to itself.

  For example, in FIG. 4, the directory group 50 in the dotted frame below is mounted on the business server 33 with the folder 502 indicating the business name of the business performed by each business server 33 as a mount point. As a result, each business server 33 can access the directory under the folder 502 indicating the business name as the mount point in the same manner as the local directory. Therefore, by reflecting the update directory d in the NAS 32, it is possible to obtain the same effect as installing the program modules individually in each business server 33. On the other hand, just by distributing the developed program module to the NAS 32, the developer side can obtain the same effect as distributing the program module to each business server 33 individually.

  The operation monitoring server 34 constantly monitors the application usage status of all the business servers 33 in the operation network environment 3. For example, the operation monitoring server 34 notifies the business server 33 that has received the flag file from the terminal device 4 when to notify the reception directory 311 of the flag file. The timing of notifying the flag file is when the application described in the flag file or the business to which the application belongs is not used by the business server 33. Further, after the operator confirms the end of the business process, the flag file may be notified to the receiving directory manually by the operator.

  When an error occurs in the operation network environment 3, the operation monitoring server 34 receives an alarm from, for example, the server 31 or 33 or NAS 32 in which the error has occurred, and interrupts the archive file release process. When the release process is interrupted or other errors occur, a switch back process for the current version of the application described later may be performed.

  The operation in the normal release process of the network system according to the present embodiment will be described below with reference to FIG.

  First, the developer inputs an instruction to release the target module to the terminal device 4 and transmits it to the distribution server 12 (S1).

  The extraction unit 122 of the distribution server 12 extracts the instructed target module from the development-side AP server 11 based on the developer's instruction in step S1 (S2).

  The transfer processing unit 121 of the distribution server 12 archives the target module extracted by the extraction unit 122, and transfers the archive file created thereby to the migration directory 211 of the neutral server 21 (S3).

  On the other hand, separately from this system, the developer requests the approver to approve the release of the target module in step S1 to the operation network environment (S00). Upon receiving the request, the approver decides whether or not to approve the release, and inputs the approval information to the terminal device 4. The terminal device 4 transmits the approval information to the approval processing unit 214 of the neutral server 21 (S4).

  Based on the approval information, the approval processing unit 214 adds the date and time 41, the approver 42, the archive file 43, the approval status 44, and the release type 46 to the log file 40 illustrated in FIG. It is registered in 213 (S5).

  If the archive file received by the moving directory 211 in step S3 is approved by the approval information, the approval processing unit 214 moves the approved archive file in the moving directory 211 to the distribution directory 212 (S6).

  The approval processing unit 214 transmits the approval archive file in the distribution directory 212 to the reception directory 311 at a preset reservation time (S7).

  When the reception directory 311 receives the approval archive file, the monitoring unit 314 moves the approval archive file in the reception directory 311 to the pool directory 312 (S8).

  For all business servers 33 in the operational network environment 3, the operation monitoring server 34 that monitors the usage status of the application uses the flag file for the business server 33 that holds the flag file from the developer. When the described application is not being executed by any business server 33, the business server 33 is notified (S9).

  In step S 9, the business server 33 that has received a notification from the operation monitoring server 34 that the application described in the flag file is not being executed by any business server 33, stores the flag file in the reception directory 311. Transmit (S10).

  When the operation monitoring server 34 detects that the flag file has been received in the reception directory 311, the operation monitoring server 34 extracts the approved archive file described in the flag file from the pool directory 312 and sends it to the expansion processing unit 313. Copy (S11).

  The expansion processing unit 313 extracts the target module from the approved archive file by, for example, the expansion process illustrated in FIG. 6 and reflects it in the NAS 32 (S12).

  The development processing unit 313 detects whether the reflection of the target module to the NAS 32 has ended normally or abnormally (S13).

  Based on the detection result, the deployment processing unit 313 creates a completion notification and transmits it to the business server 33 (S14).

  The deployment processing unit 313 also notifies the completion processing to the approval processing unit 214 of the neutral network environment 2 (S15).

  FIG. 6 is an example of a flowchart showing the expansion processing by the expansion processing unit 313.

  The development processing unit 313 detects the application name and version name of the target module included in the approved archive file extracted from the pool directory 312 (S100).

  Next, the expansion processing unit 313 creates an update folder d indicating the detected version name in the temporary storage unit (S101).

  The expansion processing unit 313 refers to the NAS 32, extracts the directory 509a indicating the version name (1.0) of the current version of the detected application, and program module group in the directory 509a indicating the version name (1.0) Is copied into the update folder d created in step S101 (S102).

  The expansion processing unit 313 stores the target module extracted and extracted from the approved archive file extracted from the pool directory 312 in step S100 in the update folder d (S103).

  Next, the expansion processing unit 313 reflects the update folder d on the NAS 32 (S104).

  Based on the detection result of step S13, the deployment processing unit 313 creates a completion notification and transmits it to the business server 33 and the approval processing unit 214 of the neutral server 21 (S105).

  Next, the operation of the emergency release process of the network system according to the present embodiment will be described below with reference to FIG. In the following description, the operation of the release process of the target module in an emergency will be described mainly with respect to a part different from the operation of the release process of the target module at the normal time, and the description of the same operation may be omitted.

  In an emergency, the flag file is not registered in the business server 33 by the developer who requested the release, but is sent to the approval processing unit 214 by, for example, an approver who requested the approval from the developer. For example, when the approval information is sent to the approval processing unit 214 in step S4, it is sent to the approval processing unit 214 together.

  Then, the approval processing unit 214 sends the flag file to the reception directory 311 (S21). For this reason, step S9 and step S10 in normal times are omitted.

  Further, instead of step S7, when the distribution directory 212 receives the approval archive file from the migration directory 211, the approval processing unit 214 immediately transmits it to the reception directory 311 (S22).

  Next, as a modification of the release process of the network system according to the present embodiment, the operation of the current version switchback process for a predetermined application stored in the NAS 32 will be described with reference to FIG. Description of the same operation as that of the release processing of the target module in the normal time may be omitted.

  The switch-back process for the current version of the application is performed mainly when the release process fails, such as when the release process is interrupted, or when an error occurs in this system.

  First, instead of step S1, the developer inputs to the terminal device 4 an instruction to switch back the current version of a predetermined application stored on the NAS 32, and transmits it to the distribution server 12 as an instruction file (S31). ).

  For this reason, step S2 is omitted.

  Instead of step S3, the transfer processing unit 121 of the distribution server 12 archives the instruction file to create an archive file, and transfers the archive file to the migration directory 211 (S32).

  On the other hand, separately from this system, the developer requests the approver to approve the switch-back instruction in step S31 (S99). In response to the request, the approver inputs approval information about the switchback to the terminal device 4 instead of step S4, and transmits it to the approval processing unit 214 of the neutral server 21 (S33).

  At the time of switchback processing, the flag file is not registered in the business server 33 by the developer who requested the switchback, but, for example, by the approver who requested the approval from the developer, the approval processing unit 214. To be sent to. For example, when the approval information is sent to the approval processing unit 214 in step S33, it is sent to the approval processing unit 214 together.

  Then, the approval processing unit 214 transmits the flag file to the reception directory 311 (S34).

  Steps S5 and S6 are the same as in normal times.

  Instead of step S7, when the distribution directory 212 receives the approval archive file from the migration directory 211, the approval processing unit 214 immediately transmits it to the reception directory 311 (S35).

  Step S8 is the same as in normal time.

  As described above, since the flag file is sent to the approval processing unit 214 in step S4, steps S9 and S10 are omitted.

  Step S11 is the same as in normal time.

  Instead of step S12, the expansion processing unit 313 takes out the instruction file from the approved archive file, for example, by the expansion process shown in FIG. 9, and performs a switchback process of the corresponding version in the NAS 32 based on the instruction (S36).

  Instead of step S13, the development processing unit 313 detects whether the switchback processing of the corresponding version has ended normally or abnormally (S37).

  Steps S14 and S15 are the same as in normal times.

  FIG. 9 is an example of a flowchart illustrating the expansion process performed by the expansion processing unit 313 during the current version switch-back process.

  The expansion processing unit 313 expands the approval archive file extracted from the pool directory 312 to the temporary storage unit 313a (S200).

  The development processing unit 313 refers to the instruction file in the temporary storage unit 313a, detects the current version of the application described therein from the NAS 32, and switches back the current version (S201). Switching back the current version is performed by changing the position where the symbolic link 510 of the current folder 508 is pasted from the folder 509 having the version name currently instructed to the folder 509 having a higher version name.

  The expansion processing unit 313 that has detected the result of whether or not the current version has been successfully switched back creates a completion notification based on this result, and transmits it to the approval processing unit 214 of the business server 33 and the neutral server 21 ( S202).

  According to the present embodiment, the neutral network environment 2 is provided between the development network environment 1 and the operation network environment 3, and the release processing or operation of the program module to the operation network environment 3 is performed in the neutral server 21 in the neutral network environment 2. A log for the current version switchback processing in the network environment 3 is stored. Therefore, the neutral server 21 can centrally manage the exchanges with the development network environment 1 and the operation network environment 3, particularly the exchanges by the release process and the current version switchback process.

  According to this embodiment, the program modules of each version of one or a plurality of applications are centrally managed. Therefore, the developer only has to release the developed program module only to the NAS 32 without being conscious of each business server 33.

  According to the present embodiment, the internal structure of the NAS 32 in which the application version information is stored has a directory structure. Therefore, if each business server 33 accesses the NAS 32 as necessary, the current version of the application in the NAS 32 can be used in the same way as if it is installed in itself.

  Further, since the internal structure of the NAS 32 in which the version information of the application is stored is a directory structure, even if the release of the program module to the NAS 32 fails, the current version of the application described above is switched back. The current state can be easily recovered by processing.

  As mentioned above, although several Example of this invention was described, these are the illustrations for description of this invention, Comprising: It is not the meaning which limits the scope of the present invention only to these Examples. The present invention can be implemented in various other forms.

DESCRIPTION OF SYMBOLS 1 Development network environment 2 Neutral network environment 3 Operation network environment 4 Terminal device 11 Development side application server 12 Distribution server 21 Neutral server 31 Release server 33 Business server 34 Operation monitoring server 121 Transfer processing part 211 Moving directory 212 Distribution directory 213 Log storage part 214 Approval processing unit 311 Reception directory 312 Pool directory 313 Deployment processing unit 314 Monitoring unit

Claims (5)

A development network environment for performing program development, including a distribution server, an operation network environment including a plurality of business servers for executing program modules developed in the development network environment, the development network environment, and the operation network A network system with a neutral server connected to the environment,
The distribution server
A release request means for sending a program module for releasing to the operational network environment to the neutral server and requesting release of the program module;
The neutral server is
A receiving unit that receives input of information indicating that the release of the program module that has received the release request from the distribution server is approved from a predetermined approver;
Approval history storage means for storing approval history data based on the input received by the receiving means;
Means for transmitting a program module approved for release by the approver to the release server,
The release server is
A network system comprising installation means for storing a release-approved program module transmitted from the neutral server in another device in the operation network environment so that the plurality of business servers can execute the module. The operational network environment is:
A shared data storage unit connected to the plurality of business servers;
The installation means stores the release-approved program module in the shared data storage unit,
The network system according to claim 1, wherein the plurality of business servers execute the approved program module with reference to the shared data storage unit.   The network system according to claim 2, wherein the neutral server acquires an installation result of the approved program module by the installation unit from the release server, and stores the result in the approval history storage unit. A development network environment for performing program development, including a distribution server, an operation network environment including a plurality of business servers for executing program modules developed in the development network environment, the development network environment, and the operation network A method for releasing a program module in a network system with a neutral server connected to an environment, comprising:
The distribution server is
Sending a program module for release to the operational network environment to the neutral server, and performing a release request step for requesting release of the program module,
The neutral server is
A step of receiving an input of information indicating that the release of the program module that has received the release request from the distribution server is approved from a predetermined approver;
Storing approval history data for storing approval history data based on the input received by the receiving means;
Sending a program module approved for release by the approver to the release server;
The release server is
A method of performing a step of storing a release-approved program module transmitted from the neutral server in another device in the operation network environment so that the plurality of business servers can execute the module. A development network environment for performing program development, including a distribution server, an operation network environment including a plurality of business servers for executing program modules developed in the development network environment, the development network environment, and the operation network A computer program for releasing a program module in a network system comprising a neutral server connected to an environment,
The distribution server
A release request means for sending a program module for releasing to the operational network environment to the neutral server and requesting release of the program module;
The neutral server is
A receiving unit that receives input of information indicating that the release of the program module that has received the release request from the distribution server is approved from a predetermined approver;
Approval history storage means for storing approval history data based on the input received by the receiving means;
Means for transmitting a program module approved for release by the approver to the release server,
The release server is
A computer program for constructing a network system, comprising installation means for storing a release-approved program module transmitted from the neutral server in another device in the operational network environment so that the plurality of business servers can execute the module. .

Images