Adopting EJB for Mass Data Handling OSS.
|
Accession number;03A0163622
|
| Title;Adopting EJB for Mass Data Handling OSS. |
| Author;
MINATO KENJI
(Nippon Telegraph and Telephone Corp. (NTT), Network Innovation Lab., JPN)
KAWABATA TAICHI
(Nippon Telegraph and Telephone Corp. (NTT), Network Innovation Lab., JPN)
IWASHITA KATSUSHI
(Nippon Telegraph and Telephone Corp. (NTT), Network Innovation Lab., JPN)
|
Journal Title;IEICE Transactions on Communications (Japanese Edition)
|
Journal Code:S0622C
|
ISSN:1344-4697
|
|
VOL.J86-B;NO.3;PAGE.353-361(2003)
|
| Figure&Table&Reference;FIG.15, TBL.2, REF.13 |
| Pub. Country;Japan |
| Language;Japanese |
| Abstract;Recent rapid advancement of internet technology and severe competition between service probiders brought diversification and shorter life of network service. To rapidly correspond to new technology and supply attractive network service for users, fast development and improvement of operational support system (OSS) are essential. For effective OSS, it is effective to make up components capable of separating database processing, transaction, and so on from business logic, and for a platform to realize it Enterprise Java Beans (EJB) is best popularized and hopeful. In this paper, was applied traffic informations with natures specific to OSS without web application to four kinds of adoptive patterns of EJB to judge if EJB could be applied to OSS, to carry out its measurement and evaluation. As a result, it was found that its results were dependent on its adopted patterns, but that its processing time was taken on proportion to data amounts of the traffic informations. Therefore, to effectively process a lot of data, here was proposed a method to summarize plural traffic informations by their gathering and serializing, to manage them. As a result, it was found that it had sufficient effects for every adopted patterns. And, it was also found that on their serialization it was more effective to enter the traffic informations as much as possible into a serialized data, but that retreival with less numbers of acquisition took more processing times on too much amounts. |
|
|
|
Related Articles;
|
|
