KR20150116343A - Methods and apparatuses for providing a multi-scale customized convergent service platform - Google Patents

Abstract

The present invention provides a method and a device for providing a platform. The method simply and quickly provides a new format convergent service platform including a function in which a customer needs, by selecting any one platform scale among mini, compact, and rich platform scales by each scale of a convergence service platform, selecting features, and providing a customized convergent service using platform data collected with respect to selected information. The method comprises the following steps: receiving platform installation information; receiving data from an external device with respect to the platform installation information, and storing to a storage; and installing a platform in an installation object server using data stored in the storage and the platform installation information.

Description

[0001] METHODS AND APPARATUS FOR PROVIDING A MULTI-SCALE CUSTOMIZED CONVERGENT SERVICE PLATFORM [0002]

The present invention relates to a platform providing method, and more particularly, to a method of providing a service platform.

The convergence service platform combines convergence applications such as message, location, presence, billing, call control, session management, multimedia management, user profile, and telecommunication services such as map, weather, social networking service Generation, execution, management, and so on.

In this regard, the currently provided convergence service platforms are manufactured by including various functions such as service creation, execution, management, and various web service components in one package.

However, the convergence service platform of one type of package has a problem that it is difficult to produce a customized convergence service platform of various scales corresponding to the demand of the user, because it does not provide only the functions required by the customer.

In addition, a fusion service platform packaged in this specific type has a problem that it takes a long time to construct a platform because the platform must be reconfigured by hand even when customization is required.

SUMMARY OF THE INVENTION It is an object of the present invention to overcome the above-mentioned problems by providing a method and apparatus for providing a convergence service platform having a scale corresponding to the purpose of a convergence service platform user and including a feature.

According to an embodiment of the present invention, there is provided a platform providing method performed by a platform providing apparatus, the method comprising: receiving platform installation information; Receiving data from an external device according to the platform installation information and storing the received data in a storage; And installing the platform on the installation target server using the data stored in the repository and the platform installation information.

The installing the platform on the installation target server using the data stored in the repository and the platform installation information includes: connecting to the installation target server remotely; And installing the platform using the data stored in the repository and the platform installation information in the installation target server.

The installing the platform on the installation target server using the data stored in the repository and the platform installation information may include: selecting a type of platform to be installed on the installation target server using the platform installation information; And installing a platform corresponding to the selected platform type in the installation target server using at least one of a plurality of data preset to correspond to the type of the platform.

The step of installing a platform corresponding to the selected platform type on the installation target server using at least one of the plurality of pieces of the predetermined data corresponding to the type of the platform is classified into the repository according to the type of the platform constituting the data And installing the platform using the stored data.

Receiving the data from the external device according to the platform installation information and storing the data in the storage, the method comprising the steps of: receiving data constituting a platform from an external device; And classifying the input data according to a type of a platform constituted by the data and storing the classified data in a storage.

Wherein the step of installing the platform on the installation target server using the platform installation information includes the step of installing the platform on the installation target server by using at least one of the plurality of data in accordance with the feature selection information included in the platform installation information, As shown in FIG.

The platform providing method may further include receiving feature selection information for selecting a feature to be included in the platform, and storing the feature selection information in a repository according to a user, wherein the platform installation information is stored in the repository And may include stored feature selection information.

According to another aspect of the present invention, there is provided a platform providing method performed by a platform providing apparatus, the method comprising the steps of: Receiving platform installation information including selection information and type information of the platform; And installing a platform on the installation target server using the platform installation information.

Wherein installing the platform on the installation target server using the platform installation information includes receiving from the external device data constituting a platform to be installed in the installation target server using the feature selection information; Categorizing and storing the received data in a repository according to type information of the platform; And installing a platform on the installation target server using data stored in the repository.

The installing the platform on the installation target server using the data stored in the storage may include: connecting to the installation target server remotely; And installing the platform using the data stored in the repository to the remotely connected installation target server.

According to another aspect of the present invention, there is provided a platform providing apparatus including: an input unit for receiving platform installation information and data; And a platform installation unit for installing the platform on the installation target server by using the platform installation information, which is input from the external device and stored in the repository, according to the platform installation information.

The platform installation unit may perform remote connection to the installation target server and install the platform to the installation target server using the data stored in the storage and the platform installation information.

Wherein the platform installation unit selects a type of a platform to be installed in the installation target server using the platform installation information and transmits the installation target server to the installation target server using at least one of a plurality of data set in advance corresponding to the type of the platform You can install the platform corresponding to the selected platform type.

The platform installation unit may install the platform using data classified and stored in the repository according to the type of the platform constituting the data.

The platform providing apparatus may further include a repository for classifying and storing the input data according to a type of a platform constituted by the data.

The platform installing unit may install a platform that performs the feature on the installation target server using at least one of a plurality of data according to the feature selection information included in the platform installation information.

Wherein the input unit receives feature selection information for selecting a feature, and the platform providing apparatus further includes a repository for storing the feature selection information according to a user, and the platform installation information includes feature selection information stored in the repository .

According to another aspect of the present invention, there is provided a platform providing apparatus that includes feature selection information indicating whether a feature to be included in a platform to be installed in a platform to be installed is selected, An input unit for inputting platform installation information including information; And a platform installation unit for installing the platform on the installation target server using the platform installation information.

Wherein the platform providing apparatus further includes a repository, and the input unit receives data constituting a platform to be installed in the installation target server from the external apparatus using the feature selection information, and the repository transmits the received data to the platform And the platform installer can install the platform on the installation target server using the data stored in the repository.

The platform installing unit may perform remote connection to the installation target server and install the platform using the data stored in the storage to the remote installation target server.

The method and apparatus for providing a platform according to one embodiment of the present invention may be configured to select one platform scale among a mini, a compact, and a rich platform scale for each scale of a convergence service platform, features, and provides a customized convergence service platform using the platform data collected according to the selected information, thereby providing a new type of convergence service platform including the functions required by the consumer in a customized manner .

1 is a flowchart illustrating a platform providing method performed by a platform providing apparatus according to a first embodiment of the present invention.
2 is a flowchart illustrating a platform providing method performed by the platform providing apparatus according to the second embodiment of the present invention.
FIG. 3 is a flowchart illustrating the installation step of the platform of FIG. 2 in more detail.
4 is a block diagram illustrating a platform provision system 400 according to a third embodiment of the present invention.
5 is a flowchart illustrating a platform providing method performed by the platform providing apparatus according to the third embodiment of the present invention.
Figs. 6 and 7 are flowcharts illustrating the platform providing step of Fig. 5 in more detail.
FIG. 8 is a flowchart illustrating the step of generating the temporary storage described in FIG. 6 in greater detail.
FIG. 9 is a flowchart illustrating the temporary storage generation step described in FIG. 7 in more detail.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail.

It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

The terms first, second, etc. may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

The terminology used in this application is used only to describe a specific embodiment and is not intended to limit the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprises" or "having" and the like are used to specify that there is a feature, a number, a step, an operation, an element, a component or a combination thereof described in the specification, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the relevant art and are to be interpreted in an ideal or overly formal sense unless explicitly defined in the present application Do not.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In order to facilitate the understanding of the present invention, the same reference numerals are used for the same constituent elements in the drawings and redundant explanations for the same constituent elements are omitted.

The service platform refers to an application development environment and an execution environment based on a Web service component in the form of an Open API (Application Programming Interface) in a cloud environment.

A web application server (WAS) is a type of middleware that is located between the Web and the enterprise system, assists in the development of Web-based distributed systems and ensures stable transaction processing. WAS acts as an application server in the existing client / server environment in a three-tier web computing environment and performs transaction processing and management and application interworking between different types of systems in a client and server environment.

Web Services Description Language (WSDL) is a standard language based on eXtensible Markup Language (XML), which is used to describe a Web service and provide a way for businesses to approach each other electronically.

Simple Object Access Protocol (SOAP) is a communication protocol for invoking data or services on another computer based on extensibility creation language (XML) and hypertext transfer protocol (HTTP).

  REST (REpresentational State Transfer) A protocol that reads information from an XML file and collects the desired information. You can obtain information by reading only the URL of the desired information. It is a structured form using web technologies and protocols including HTTP and XML, and is easier to use than the SOAP protocol.

Web services are software and technologies that support distributed computing between different computers connected to the network using standard technologies such as SOAP, REST, and WSDL, and are generally described in WSDL and communicate using SOAP messages.

A feature is a special function or operation of the system that the user perceives.

Hereinafter, the present invention will be described in detail with reference to the accompanying drawings.

1 is a flowchart illustrating a platform providing method performed by a platform providing apparatus according to a first embodiment of the present invention. The platform providing apparatus according to the first embodiment of the present invention first receives platform installation information (S110). The platform providing device receives the platform installation information from the user who intends to install the platform using the graphical user interface. The input platform installation information can be stored in the platform providing device.

Next, the platform providing apparatus receives the data used for platform installation from the external device according to the platform installation information, and stores the received data in the storage (S120).

Next, the platform providing apparatus installs the platform on the installation target server using the data stored in the repository and the platform installation information (S120). A platform providing apparatus according to an embodiment of the present invention installs a platform on an installation target server using data stored in a repository using platform installation information input from a user or platform installation information stored in a platform providing apparatus.

2 is a flowchart illustrating a platform providing method performed by the platform providing apparatus according to the second embodiment of the present invention. The platform providing apparatus according to the second embodiment of the present invention first receives platform installation information including feature selection information indicating whether a feature to be included in a platform to be installed in a platform to be installed in the platform and platform type information is present in operation S210. Next, the platform providing apparatus installs the platform on the installation target server using the platform installation information (S220).

3 is a flowchart illustrating a method of installing a platform on a server to be installed using platform installation information in a method of providing a platform according to a second embodiment of the present invention described with reference to FIG. The platform providing apparatus receives the data constituting the platform to be installed on the installation target server from the external apparatus using the feature selection information (S310). Next, the platform providing apparatus classifies the received data into the repository according to the type information of the platform and stores the classified data (S320). Next, the platform providing apparatus installs the platform on the installation target server using the data stored in the repository (S330).

4 is a block diagram illustrating a platform provision system 400 according to a third embodiment of the present invention. The platform providing system according to the third embodiment of the present invention can provide the platform at various scales according to the needs of the user and can provide the user with the necessary features. The platform providing system can provide a convergence service platform having the above characteristics.

Referring to FIG. 4, a platform provision system 400 according to a third embodiment of the present invention includes a command repository 410 and a platform provision device 490. The platform providing device 490 may include a platform data store 440, a platform provider 450, an input 460, and a feature profile data store 470. The platform data store 440 may include a platform repository manager 420 and a platform repository 430. The feature profile data store 470 may include a feature profile store 472 and a feature profile manager 474.

The data repository 410 is a repository for storing data necessary for platform installation. The data store 410 includes commands or files necessary for platform creation. For example, the data store 410 can hold all the files needed to install the platform. The data store 410 may store the latest version of all the files needed to install the platform. The data storage 410 may be configured as an on-line archive server configured separately from the platform providing apparatus, so that the data repository and the platform providing apparatus can exchange data by performing data communication. The data provided by the data store 410 includes commands or files necessary for platform creation. For example, if the platform providing device 490 sends a request for a particular command or file to the data store 410, the data store 410 may send a specific command or file to the platform providing device 490 in response have. Meanwhile, in other embodiments, the data store 410 may be comprised of a portion included in the platform providing device 490. In this case, the data store 410 may send data to the platform data store 440 at the request of the platform data store 440.

Table 1 below shows a storage structure of files stored in the data storage 410.

folder Explanation An example of a saved file was / 'Small / Medium / Large' web application server installation file storage location geronimo.tgz
glassfish.tgz
tomee + .tgz builtinapps Convergence Service Platform Built-in Application Storage Location cocoGateWeb-geronimo.war
cocoGateWeb-glassfish.war
cocoTask-mini.war mini / shared Small platform common file location meter-mini.jar
logging-mini.jar
... mini / features / ... Implementation components of small platform features ac / serviceAC-mini.jar
ac / idMgr-mini.jar
proMgt / prfmgt-mysql.jar
proMgt / prfmgt-postsql.jar
... compact / shared Medium platform common file repository meter-compact.jar
logging-compact.jar
... compact / reatures / ... Implementation Components of Medium Platform Features scvMgt / manager-compact.jar
svcMgt / client-compact.jar
call / tcp-rest-compact.war
call / tcp-woap-compact.jar
... rich / shared Large platform common file storage meter-rich.jar
logging-rich.jar
... rich / teatures / ... Implementation Components of Large Platform Features appMgt / appManager-rich.jar
appMgt / appClient-rich.jar
sms / sms-rest-rich.war
sms / sms-soap-rich.jar
...

As shown in Table 1, files necessary for platform installation may be classified according to types and stored in the data repository 410 separately from each other. For example, files may be stored separately in separate folders according to classification according to type. For example, the web application server installation file can be stored in the was folder. The web application server file can be divided into small, medium, and large sub-categories according to the size type of the web application server and can be separately stored in each folder. For example, in the was folder, small, medium, and large application servers (WAS, Web Application Server) installation files can be stored as shown in Table 1. The was folder stores geronimo.tgz as a large platform WAS installation file, glassfish.tgz as a medium platform WAS installation file, and tomee + .tgz as a small platform WAS installation file.

In the same way, converged service platform built-in applications can be stored separately in the builtinapps folder. For example, builtinapps can store the default applications for each platform: cocoGateWeb-geronimo.war, cocoGateWeb-glassfish.war, and cocoTask-mini.war.

Likewise, referring to Table 1, common files that make up a small platform can be stored separately in a mini / shared folder, and implementation components of small platform features can be stored separately in a mini / features folder. In the same way, common files and implementation components of medium and large platforms can be stored separately in each folder. For example, for features of a small platform, files associated with a separate folder for each feature are stored in mini / features / subfolders, and files commonly used by features of the mini platform may be stored in mini / shared . For the features of the medium platform, files related to separate folders are stored in compact / features / subfolders, and files commonly used by features of medium platform can be stored in compact / shared. For large platform features, files related to separate folders are stored in rich / features / subfolders, and files commonly used by features of large platforms can be stored in rich / shared.

Table 2 below shows the feature model of a multiscale custom convergence service platform.

Mini platform Compact platform The rich platform Customized platform mandatory features Service execution,
Service access control,
Profile and identity management,
The third call control web service component,
Email web service components,
SMS Web service component Service execution,
Service access control,
Service lifecycle management,
Application service life cycle management,
Profile and identity management Service execution,
Service access control,
Service composition,
Service lifecycle management,
Profile and identity management
Service composition test Optional platform features Manage logs Log management,
The third call control web service component,
Email web service components,
SMS Web service component,
Presence web service component,
Directory Web service components,
Following Web service component,
The note web service component,
Group and discussion activity Web service components,
Bulletin board web service component,
Wiki Web service component,
File Cloud Web Service component,
Integrated Search Web Service Component Log management,
QoE guaranteed delivery,
The third call control web service component,
Email web service components,
SMS Web service component,
Presence web service component,
Directory Web service components,
Following Web service component,
The note web service component,
Group and discussion activity Web service components,
Bulletin board web service component,
Wiki Web service component,
File Cloud Web Service component,
Integrated Search Web Service Component Chice feature - Select PostgreSQL and MySQL DBMS in profile and identity management features
- Select the SOAP and REST interface in the third call control web service component feature
- Select interface between SOAP and REST in email web service component
- Select interface between SOAP and RESP in SMS Web service component
- Selecting SOAP and REST interfaces in the prejones web service component

As shown in Table 2, a multiscale custom convergence service platform may have mandatory features and optional features for small, medium, and large platforms. Essential features are essential features that must be installed when platform creators choose between small, medium, and large. For example, when installing a small platform, service execution, service access control, profile and identity management, third call control web service components, email web service components, and SMS web services components may be mandatory features that must be installed. An optional feature is a feature to install by the installer's needs. For example, if the installer installs a small platform, the log management feature can optionally be installed if a log management feature is required on a small platform.

On the other hand, when different technologies can be used to implement a feature among the features installed on small, medium, and large platforms, there is a choice feature in which one of the technologies must be selected. For example, profile and identity management features must choose between PostgreSQL and MySQL Database Management System (DBMS), the Simple Object Access Protocol (SOAP) and the REST (REST) ) Must be selected.

Referring again to FIG. 4, the platform repository manager 420 analyzes the data received from the feature profile data repository 470 and receives files necessary for installation from the data repository 410. For example, the platform repository management unit 420 may receive each file from the data repository 410 using FTP (File Transfer Protocol).

The data received by the platform repository management unit 420 from the feature profile data repository 470 may be platform installation information including at least one of platform type information and feature selection information. For example, the platform repository manager 420 may receive platform type information from the feature profile data repository 470. The platform type information may include scale information of a platform to be installed in the installation target server. In addition, the platform repository management unit 420 may receive the feature selection information indicating the features that the platform to be installed should include.

In the above description, platform type information and feature selection information are included in the platform installation information. However, only platform type information may be transmitted instead of the platform installation information, or only feature selection information may be transmitted. On the other hand, feature selection information may be included in the platform type information and transmitted, and the platform type information may be transmitted in the feature selection information. In addition, the platform type information and the feature selection information may be respectively transmitted, so that the platform repository management unit 420 may receive platform type information and feature selection information from the feature profile repository 470, respectively. Hereinafter, for convenience of description, the platform installation information defines at least one of platform type information and feature selection information, platform type information, and feature selection information.

The platform repository management unit 420 stores data received from the data repository 410 in the platform repository 430. For example, the platform repository management unit 420 may store an instruction or a file received from the data repository 410 in the platform repository 430 according to a type of a command or a platform constituted by the file.

The platform repository 430 may include a small platform repository 431, a medium platform repository 432, and a large platform repository 433. The small platform repository 431 is a repository for storing files necessary for a small platform installation. The medium platform repository 432 is a repository for storing files necessary for medium platform installation. The large platform repository 433 is a repository for storing files necessary for a large platform installation. Each platform repository can store each file temporarily.

For example, the platform repository management unit 420 manages the files received from the data repository 410 into a small platform repository 431, a medium platform repository 432, and a large platform repository 433, depending on the size of the platform that each file comprises. And the like.

The platform providing unit 450 provides the platform to the installation target server using the platform installation information and the platform data. For example, the platform providing unit 450 may provide a platform to be installed to the installation target server using at least one of platform type information and feature selection information and platform data.

For example, the platform providing unit 450 analyzes the platform installation information stored in the feature profile data storage 460, determines the installation order between the platform installation files, and stores the installation order in the platform data store 440 By using the stored platform installation files, you can provide the platform to the target server by installing the platform on the target server to be installed in the remote location.

The input unit 460 receives platform installation information from the user. For example, the input unit 460 receives the type information of the platform to be provided in the platform providing unit 450 and the selection information of the feature to be included in the platform to be provided from the user. The input unit 460 can receive the platform type information from the user using the feature selection user interface. For example, the input unit 460 may receive a scale of a platform desired to be provided to the installation target server from a user and a feature to be included in the platform as a platform installation information by using a graphical user interface.

The input unit 460 transmits the platform installation information received from the user to the feature profile data storage 470. The feature profile data store 470 stores platform installation information received from the input unit 460. The feature profile data store 470 can store the input platform installation information according to the user. For example, the feature selection information may be stored in the feature profile storage 472 according to the user.

The feature profile repository 472 is a repository, such as a memory or a database, that stores at least one of the platform type information and feature selection information received from the input 460. The feature profile management unit 474 performs the function of creating, adding, changing, and deleting platform installation information to the feature profile storage 472. The feature profile store 472 and the feature profile manager 474 may build one feature profile data store.

5 is a flowchart illustrating a platform providing method performed by the platform providing apparatus according to the third embodiment of the present invention. First, the platform providing apparatus registers data in the data repository (S510). For example, the platform providing device may register the latest version of all the implementation components associated with the convergence service platform feature in a data store that resides on the network.

Next, the platform providing apparatus receives the platform installation method (S520). The platform providing apparatus can receive the platform installation method from the user. Alternatively, the platform providing device may use the platform installation information stored in the feature profile data store as an input. Generally, if you are a beginner of platform creation, you can choose one-click installation method, and if you are an expert, you can choose custom installation.

Finally, the platform providing apparatus provides the platform to the installation target server in accordance with the entered platform installation method (S530). 6 and 7, the platform providing step S530 will be described in more detail.

FIGS. 6 and 7 are flowcharts illustrating the platform providing step S530 of FIG. 5 in more detail. FIG. 6 is a flowchart for explaining installation steps of the pre-production type platform in detail, and FIG. 7 is a flowchart illustrating the installation steps of the user-customized platform in detail.

Referring to FIG. 6, a description will be given of a step in which a platform providing apparatus according to a third embodiment of the present invention provides a prefabricated platform. First, the platform providing apparatus creates a temporary storage according to basic platform installation information (S610). If you choose to install the pre-production platform as a platform installation method, the platform-provisioning device sets the default features without the intervention of the installer's feature selection, finds the files required to install the platform from the data store, Build a temporary repository. This step will be described in more detail with reference to FIG.

Next, the platform providing apparatus installs the WAS according to the pre-production type platform (S620). The platform providing device receives the address of the installation target server and the directory location. If the pre-production platform type is small, install TomEE + WAS (Web Application Server). On the other hand, if the pre-built platform type is medium, install GlassFish WAS. On the other hand, if the pre-production platform type is large, install Geronimo WAS.

Next, the platform providing apparatus analyzes the dependency relationship between the files to be installed and determines the installation order of the files constituting the platform (S630). This is the step in determining the order in which the platform is installed. The platform providing device can determine the installation order of the platform by analyzing the dependency of the files to be installed on the installation target server according to the selected features.

Next, the platform providing apparatus installs an implementation component, a library, and an initialization file (S640). This is the step of installing the platform according to the above platform installation order. The platform providing device can install the implementation component, the library, and the initial configuration file using the command line interface (CLI) command of the installed WAS according to the platform installation order determined above.

Next, the platform providing apparatus generates initial data and establishes a database connection (S650). Platform-supplied devices can execute database scripts to generate initial data and establish database connection settings.

Next, the platform providing apparatus determines whether an error has occurred during the installation of the platform. The platform-supplied device can retry the platform installation from the point of failure by finding the point where the installation failed if an error occurs during the platform installation. For example, the platform providing device ends the platform provisioning step if no error occurs during the platform installation. However, if an error occurs during platform installation, you can return to the platform installation failure point and retry the platform installation. The platform-supplied device can issue an error message and terminate the platform installation if the platform installation fails despite having retried the platform installation more than three times.

Referring to Fig. 7, steps for providing a platform for providing a platform according to the third embodiment of the present invention will be described.

First, the platform providing apparatus generates a temporary storage according to platform installation information selected by the user or platform installation information recorded in the platform providing apparatus (S710). If a custom platform installation is selected, the platform provisioning device selects the required features and optional features of the platform, either small, medium, or large, according to the input platform installation information, and then creates a temporary storage do. This step will be described later in more detail with reference to FIG.

Next, the platform providing apparatus installs the WAS according to the customized platform type according to the platform installation information (S720).

The platform providing device receives the address of the installation target server and the directory location. And, if the customized platform type is small, install TomEE + WAS. On the other hand, if the pre-built platform type is medium, install GlassFish WAS. On the other hand, if the pre-production platform type is large, install Geronimo WAS.

Next, the platform providing apparatus analyzes the dependency relationship between the files to be installed and determines the installation order of files constituting the platform (S730). The platform providing device can determine the installation order of the platform by analyzing the dependency of the files to be installed on the installation target server according to the selected features.

Next, the platform providing apparatus installs an implementation component, a library, and an initialization file according to the determined installation order (S740). The platform providing device can install the implementation component, the library, and the initial configuration file using the command line interface (CLI) command of the installed WAS according to the platform installation order determined above.

Next, the platform providing apparatus generates initial data and establishes a database connection (S750). Platform-supplied devices can execute database scripts to generate initial data and establish database connection settings.

Next, the platform providing apparatus judges whether or not an error has occurred during the installation. If an error occurs, the platform installation is retried from the point where the error occurred. For example, the platform providing device ends the platform provisioning step if no error occurs during the platform installation. However, if an error occurs during platform installation, you can return to the platform installation failure point and retry the platform installation. The platform-supplied device can issue an error message and terminate the platform installation if the platform installation fails despite having retried the platform installation more than three times.

FIG. 8 is a flowchart illustrating the step S610 of creating the temporary storage described in FIG. 6 in more detail. The temporary storage creation step will be described in more detail with reference to FIG. The platform providing apparatus stores the data required in the platform installation in the temporary storage, in order to install the platform corresponding to the type of the prefabricated platform. In the following, the mandatory features and optional features can use the criteria of Table 2 described above.

First, the platform providing apparatus determines whether the type of the prebuilt platform is small (S810). If the type of the prebuilt platform to be installed is small, the platform providing device creates a temporary storage for the small platform (S820). If the prefabricated platform type is small, you can select only the essential features and not the optional feature portions in the feature model for small platforms. In an optional feature, the DBMS can select PostgreSQL and download the installation files for the selected small platform features from the data repository and store them in a small platform repository.

On the other hand, if the type of the prebuilt platform to be installed is not small, the platform providing device determines whether the type of the prebuilt platform is medium (S830). If the type of the prebuilt platform to be installed is medium, the platform providing device creates a temporary storage for the medium platform (S840).

The platform delivery device can select both the required and optional features in the feature model for the mid-platform platform if the pre-built platform type is medium, and select PostgreSQL as the DBMS in the optional feature. In addition, the platform providing apparatus can select REST as the interface of the Web service component features, download the installation files corresponding to the selected medium platform features from the data repository, and store them in the medium platform repository.

On the other hand, if the type of the prebuilt platform to be installed is not medium, the platform providing apparatus determines whether the type of the prebuilt platform is large (S850). The platform providing device creates a temporary storage for a large platform when the type of the pre-built platform to be installed is large (S860).

The platform provisioning device can select both the required and optional features in the feature model for large platforms if the pre-production platform type is large, and select PostgreSQL as the DBMS in the optional features. And the platform providing device can select REST as an interface of Web service component features and download the installation files corresponding to large platform features from the data repository and store them in the large platform repository.

On the other hand, when the type of the pre-production platform to be installed is not large, the type of the platform to be installed is not specified as any of small, medium, and large, so that the platform providing device uses a predetermined error processing technique Or create a temporary repository of the default platform. The default platform may be preconfigured on any of the small, medium and large platforms.

9 is a flowchart illustrating the temporary storage creation step (S710) described in FIG. 7 in more detail. The temporary storage creation step will be described in more detail with reference to FIG. The platform providing device stores the data required in the platform installation in the temporary storage in order to install the platform corresponding to the type of the customized platform.

First, the platform providing apparatus determines whether the type of the customized platform is small (S910). If the type of the customized platform to be installed is small, the platform providing device creates a temporary storage for the small platform (S920).

The platform-providing device presents the necessary features and optional features to the user through the user interface according to the small platform feature model when the customized platform type is small. The platform providing device can receive input of essential features and whether to use optional features. The platform providing device generates platform installation information for the small platform according to the input of the user and stores it in the feature profile storage. Then, the platform providing apparatus analyzes the platform installation information for the stored small platform, downloads the installation target files from the data repository, and stores the files in the small platform repository.

On the other hand, if the type of the customized platform to be installed is not small, the platform providing apparatus determines whether the type of the customized type platform is medium (S930). If the type of the customized platform to be installed is medium, the platform providing device creates a temporary storage for the medium platform (S940).

The platform-provisioning device presents essential and optional features to the user through the user interface according to the medium platform feature model when the customized platform type is medium. The platform providing device can receive input of essential features and whether to use optional features. The platform providing device generates platform installation information for the medium platform according to the input of the user and stores it in the feature profile storage. The platform providing apparatus analyzes platform installation information for the stored medium platform, downloads the installation target files from the data repository, and stores the files in the medium platform repository.

On the other hand, if the type of the customized platform to be installed is not medium, the platform providing device determines whether the type of the customized type platform is large (S950). The platform providing device creates a temporary storage for a large platform if the type of the customized platform to be installed is large (S960).

Platform-delivered devices display essential and optional features to the user through the user interface, depending on the large platform feature model when the custom platform type is large. The platform providing device can receive input of essential features and whether to use optional features. The platform providing device generates the platform installation information for the large platform according to the user's input and stores it in the feature profile storage. Then, the platform providing device analyzes the platform installation information for the stored large platform, downloads the installation target files from the data repository, and stores the files in the large platform repository.

On the other hand, if the type of the customized platform to be installed is not large, the type of the platform to be installed is not specified as any of small, medium, and large. Therefore, the platform providing apparatus uses a predetermined error processing technique Or create a temporary repository of the default platform. The default platform may be preconfigured on any of the small, medium and large platforms.

While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. It will be apparent to those skilled in the art that the present invention can be carried out without departing from the spirit and scope of the invention.

The combination of the above-described embodiments is not limited to the above-described embodiment, and various combinations of types as well as the above-described embodiments may be provided according to implementation and / or necessity.

In the above-described embodiments, the methods are described on the basis of a flowchart as a series of steps or blocks, but the present invention is not limited to the order of steps, and some steps may occur in different orders or in a different order than the steps described above have. It will also be understood by those skilled in the art that the steps depicted in the flowchart illustrations are not exclusive and that other steps may be included or that one or more steps in the flowchart may be deleted without affecting the scope of the invention You will understand.

The foregoing embodiments include examples of various aspects. While it is not possible to describe every possible combination for expressing various aspects, one of ordinary skill in the art will recognize that other combinations are possible. Accordingly, it is intended that the invention include all alternatives, modifications and variations that fall within the scope of the following claims.

Claims (20)

A platform providing method performed by a platform providing apparatus,
Receiving platform installation information;
Receiving data from an external device according to the platform installation information and storing the received data in a storage; And
Installing the platform on the installation target server using the data stored in the repository and the platform installation information.
The method according to claim 1,
Wherein installing the platform on the installation target server using the data stored in the repository and the platform installation information comprises:
Remote access to the target server; And
And installing the platform using the data stored in the repository and the platform installation information in the installation target server.
The method according to claim 1,
Wherein installing the platform on the installation target server using the data stored in the repository and the platform installation information comprises:
Selecting a type of platform to be installed in the installation target server using the platform installation information; And
And installing a platform corresponding to the selected platform type in the installation target server using at least one of a plurality of data preset to correspond to the type of the platform. The method of claim 3,
The step of installing a platform corresponding to the selected platform type in the installation target server using at least one of the plurality of predetermined data so as to correspond to the type of the platform
And installing the platform using the data classified and stored in the repository according to the type of the platform constituting the data. The method according to claim 1,
Receiving the data from the external device according to the platform installation information, and storing the received data in the storage,
Receiving data constituting a platform from an external device; And
Further comprising the step of classifying the input data according to a type of a platform constituted by the data and storing the classified data in a storage.
The method according to claim 1,
Wherein installing the platform on the installation target server using the platform installation information comprises:
And installing a platform for performing the feature on the installation target server using at least one of the plurality of data according to the feature selection information included in the platform installation information. The method according to claim 6,
The platform providing method includes:
Receiving feature selection information for selecting a feature to be included in the platform;
Further comprising the step of: storing the feature selection information in a storage in accordance with a user,
Wherein the platform installation information includes feature selection information stored in the repository. A platform providing method performed by a platform providing apparatus,
Receiving platform installation information including feature selection information indicating whether a feature to be included in a platform to be installed in a server to be installed is selected and type information of the platform; And
And installing a platform on the installation target server using the platform installation information. 9. The method of claim 8,
Wherein installing the platform on the installation target server using the platform installation information comprises:
Receiving data constituting a platform to be installed in the installation target server from an external device using the feature selection information;
Categorizing and storing the received data in a repository according to type information of the platform; And
And installing a platform on the installation target server using data stored in the repository. 10. The method of claim 9,
Wherein installing the platform on the installation target server using the data stored in the repository comprises:
Remotely accessing the installation target server; And
And installing the platform using the data stored in the repository to the remotely connected installation target server. A platform providing apparatus comprising:
An input unit for receiving platform installation information and data; And
And a platform installation unit for installing the platform on the installation target server by using the platform installation information inputted from the external device and stored in the repository according to the platform installation information.
12. The method of claim 11,
Wherein the platform installation unit performs remote connection to the installation target server and installs the platform using the data stored in the storage and the platform installation information to the installation target server.
12. The method of claim 11,
Wherein:
Selecting a type of a platform to be installed in the installation target server using the platform installation information and using at least one of a plurality of data set in advance corresponding to the type of the platform to correspond to the selected platform type Wherein the platform is installed on the platform. 14. The method of claim 13,
Wherein:
Wherein the platform is installed using data classified and stored in the repository according to the type of platform constituting the data.
12. The method of claim 11,
Wherein the platform providing apparatus further comprises a repository for classifying and storing the input data according to a type of a platform constituted by the data.
12. The method of claim 11,
Wherein the platform installation unit installs a platform for performing the feature on the installation target server using at least one of a plurality of pieces of data according to the feature selection information included in the platform installation information. 17. The method of claim 16,
The input unit receives feature selection information for selecting a feature,
The platform providing apparatus may further include a storage for storing the feature selection information according to a user,
And the platform installation information includes feature selection information stored in the repository. A platform providing apparatus comprising:
An input unit for inputting platform installation information including feature selection information indicating whether a feature to be included in a platform to be installed in the installation target server is selected and type information of the platform; And
And a platform installation unit for installing the platform on the installation target server using the platform installation information. 19. The method of claim 18,
Wherein the platform providing device further comprises a storage,
Wherein the input unit receives data constituting a platform to be installed in the installation target server from an external device using the feature selection information,
Wherein the repository categorizes and stores the received data according to type information of the platform,
Wherein the platform installation unit installs a platform on the installation target server using data stored in the repository. 20. The method of claim 19,
Wherein:
Wherein the remote management server performs a remote connection to the installation target server and installs the platform using the data stored in the storage to the remotely connected installation target server.

Images