주의:이 페이지 정보는 9월 2008에 종료되었습니다

최신 정보는 밑의 링크를 참고하세요.

Categories

• 소프트웨어 라이센스 (13)
• Web서비스 (10)

또는 이 상품의 특정 라이센스를 구입하실 경우는, 가격 및 제품 취급 상황에 관해서는 이쪽 으로 연락 주시기 바랍니다.

이 페이지에 표시된 정보는 최신정보가 아닐 경우가 있습니다.

주의 : 이 제품정보에는 한글안내가 포함되어 있지 않습니다.
A Web Service designed specifically for locking shared resources, such as a user-license, a suite of data, an installation process. ARCS, which stands for Application Resource Control Service, is installed as an NT Service and interfaces with your application as a Web Service. ARCS has no dependencies on other software infrastructures, e.g. client-networking software, a DBMS, IIS, or any runtime prerequisites. Where your application resides, no installation for ARCS is required; your application just has to be able to communicate via HTTP. ARCS meets the standard of "full recovery", which basically means that it maintains its state through anything short of pulling the power plug.

What's New in ARCS V2.01.03?

• New methods have been added to the Web Service that are very useful for quickly storing and retrieving arbitrary data, e.g. storing session state data across a server farm.

ARCS runs on a single Windows machine as an "NT Service". Your application can make simple requests to ARCS via HTTP. ARCS is a type of software that is commonly known as a "web service" (though using the SOAP protocol is optional). ARCS can be communicated with over an intranet or the internet.

Network file byte-locking is not utilized. DBMS table/record locking is not utilized. Both of those methodologies have known limitations. ARCS is a standalone service that is ideally suited for resource control and does not utilize or depend on any of the myriad of historical methodologies.

ARCS can be installed on any Microsoft Windows OS version that Microsoft supports.

• No runtime prerequisites are necessary, e.g. Java Runtime, .NET Framework.
• No networking software is necessary, e.g. Microsoft Networks Client, Novell Client.
• No DBMS is necessary, e.g. SQL Server.
• No webserver-like software is necessary, e.g. IIS.
• There are no minimum requirements for processor speed, RAM, etc.

There is no installation required on the client machines (where your application is installed). A client machine can run any type of operating system and it may be an end-user workstation or a server of any kind. The client machine may indeed be a server hosting multiple users itself, e.g. a web server. The client machine simply has to be equipped to make HTTP requests. On Windows machines, this is easily accomplished using a "built-in" COM object such as "MSXML2.ServerXMLHTTP".