Realization. The Debtor acknowledges and agrees that the Secured Party may realize upon various securities securing the Obligations or any part thereof in such order as it may be advised and any such realization by any means upon any security or any part thereof will not bar realization upon any other security or the security hereby constituted or parts thereof.
Realization. CIBC or a Receiver may use, collect, sell, lease or otherwise dispose of, realize upon, release to the Customer or other Persons and otherwise deal with, the Collateral in such manner, upon such terms (including among other things by arrangement providing for deferred payment) and at such times as CIBC or the Receiver considers appropriate. CIBC or the Receiver may make any sale, lease or other disposition of the Collateral in the name of and on behalf of the Customer or otherwise.
Realization. 11.1 The Agent will not, nor will it be entitled to, demand payment pursuant to this Debenture or enforce the Security Interest unless and until an Event of Default occurs and is continuing, but thereafter the Agent, as agent for the Secured Party may at any time exercise and enforce all of the rights and remedies of a holder of this Debenture in accordance with and subject to the Note Documents as if the Agent was the absolute owner hereof, subject to Article 12 hereof and provided that the Agent will not be bound to exercise any such right or remedy.
Realization. The Agent is hereby authorized, upon the occurrence of an Event of Default under the Credit Agreement and for so long as such Event of Default continues, to demand payment, in accordance with the Credit Agreement, of the Senior Pledged Bond, Series 2, without notice to, consent of or control by the Issuer. Notwithstanding that the Senior Pledged Bond, Series 2 is expressed to be payable on demand, the Agent shall have no right to and shall not demand payment unless or until an Event of Default under the Credit Agreement shall have occurred and be continuing. No payment of principal on account of any of the obligations of the Issuer under the Credit Agreement shall reduce the principal amount of the Senior Pledged Bond, Series 2. Notwithstanding the principal amount of the Senior Pledged Bond, Series 2, or the rate of interest expressed to be payable thereon, or that the Senior Pledged Bond, Series 2 is expressed to be payable on demand, the Senior Pledged Bond, Series 2 shall constitute a liability of the Issuer to the Agent only to the extent of the lesser of (i) the Obligations of the Issuer under the Credit Agreement outstanding at the time of calculation, and (ii) the principal amount of the Senior Pledged Bond, Series 2 and interest accrued thereon, and such liability shall be payable only in accordance with the payment provisions of the Credit Agreement.
Realization. BKC may, if it deems it advisable to do so, restrict the prospective bidders or purchasers to Persons who will represent and agree that they are purchasing for their own account for investment and not with a view to the resale or distribution of any of the Collateral and, in particular may restrict the prospective bidders of purchasers to Persons which, in its judgment will have the capacity to perform the commitments required by an owner of IFFP as the holder of rights under any development or franchise agreement with BKC.
Realization. HTS may realize on the security interest granted hereunder upon failure by ExpressVu to pay any portion of the Purchase Price within 45 days of the due date thereof.
Realization. This chapter picks up the conceptual design and the specification work accomplished in the previous chapter and tries to verify the ideas by a prototypical Java implementation. The 52°North3 Web Processing Service implementation was used as the basis for the specified WPS extensions. This implementation is fully compatible to the OGC 1.0.0 standard and provides due to a modularized concept (Schaeffer and Foerster 2007) an ideal starting point. One goal was to alter the underlying 52°North WPS implementation as little as possible. Therefore, the logic for the two new operations was completely separated and bundled as a new servlet. This technical approach keeps the Transactional WPS extension optional as theoretically intended by section 3. Hence, the DeployProcess and UndeployProcess operations have to be called on a different endpoint than the original operation. This behaviour is supported by the OWS common (OGC, 2007c) specification in terms of allowing different URLs for every operation. In order to not only support predefined algorithms as it was originally implemented by the 52°North implementation, a dynamic concept had to be introduced in order to enable the WPS-T to register and unregister an algorithm at runtime. A static local repository provides access to predefined algorithms, which are available on the same machine as the WPS-T. Dynamic Repositories allow 3 52°North website: http://www.52North.orgthe registration and unregistration of processes at runtime. The BPELRepository in figure 10 is a sample implementation which implements the BPEL Profile specified in section 3.2 and acts as a dynamic wrapper for a BPEL engine. Figure 10: Basic WPS-T Architecture. Workflows deployed on a BPEL engine are accessed and wrapped as algorithms by this repository. The WPS-T servlet directly accesses the BPEL repository for deploying/undeploying processes which follows the BPEL deployment profile specified in section 3. Since the WPS servlet is responsible for executing the processes, it requests the repository manager to get access to all registered algorithms. By encapsulating algorithms from static and dynamic algorithm repositories behind this unified interface, the WPS servlet does not need to know what kind of repositories and algorithms are registered. It only needs a standardized way of fetching the necessary process which is delivered by the RepositoryManager. Therefore, the architecture is held open to support different repositories supporting diff...