Authorize.net CIM PHP Class 1.2 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Authorize.net CIM PHP Class 1.2 (Default branch)
# 1  
Old 01-19-2008
Authorize.net CIM PHP Class 1.2 (Default branch)

The Authorize.net CIM PHP Class allows you to interact with the Authorize.Net Customer Information Manager (CIM), which can be used to store your customers? sensitive payment information on secure servers, simplifying payments for returning customers and recurring transactions. It can also help you to comply with the Payment Card Industry (PCI) Data Security Standard, since customer data is no longer stored locally. It is an ideal tool for businesses that need to securely save customer data and provide convenience for their customers. License: GNU General Public License v2 Changes:
The error handling logic for some functions was incorrect. The refId element is now implemented. The Wells Fargo SecureSource eCheck.Net implementation was incorrect. echeck (bankAccount element) implementation was incorrect. getCustomerShippingAddress() was modified and renamed to getCustomerShippingAddressRequest(). order_purchaseOrderNumber() had an incorrect element name. Some examples were incorrect. Better examples for each method were added, with full details and all possible parameters. A Godaddy proxy option for curl was added.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
init.wbem(1M)						  System Administration Commands					     init.wbem(1M)

NAME
init.wbem - start and stop the CIM Boot Manager SYNOPSIS
/etc/init.d/init.wbem start | stop | status DESCRIPTION
The init.wbem utility is run automatically during installation and each time the system is rebooted. This utility manipulates the CIM Object Manager (CIMOM) and the Solaris Management Console server, both of which run combined in a single process. init.wbem can be used to start, stop, or retrieve status from the server. CIM Object Manager The CIM Object Manager manages CIM objects on a WBEM-enabled system. A CIM object is a computer representation, or model, of a managed resource, such as a printer, disk drive, or CPU. CIM objects are stored internally as Java classes. When a WBEM client application accesses information about a CIM object, the CIM Object Manager contacts either the appropriate provider for that object or the CIM Object Manager Repository. Providers are classes that communicate with managed objects to access data. When a WBEM client application requests data from a managed resource that is not available from the CIM Object Manager Repository, the CIM Object Manager forwards the request to the provider for that managed resource. The provider dynamically retrieves the information. At startup, the CIM Object Manager performs the following functions: o Listens for RMI connections on RMI port 5987 and for XML/HTTP connections on HTTP port 5988. o Sets up a connection to the CIM Object Manager Repository. o Waits for incoming requests. During normal operations, the CIM Object Manager performs the following functions: o Performs security checks to authenticate user login and authorization to access namespaces. o Performs syntactical and semantic checking of CIM data operations to ensure that they comply with the latest CIM Specification. o Routes requests to the appropriate provider or to the CIM Object Manager Repository. o Delivers data from providers and from the CIM Object Manager Repository to WBEM client applications. A WBEM client application contacts the CIM Object Manager to establish a connection when it needs to perform WBEM operations, such as cre- ating a CIM class or updating a CIM instance. When a WBEM client application connects to a CIM Object Manager, it gets a reference to the CIM Object Manager, which it then uses to request services and operations. Solaris Management Console Server The Solaris Management Console server is the back end to the front end console, smc(1M). It provides tools for the console to download and performs common services for the console and its tools to use, such as authentication, authorization, logging, messaging, and persistence. System Booting The init.wbem script is installed in the /etc/init.d directory. OPTIONS
The following options are supported: start Starts the CIMOM and Solaris Management Console server on the local host. stop Stops the CIMOM and Solaris Management Console server on the local host. status Gets the status of the CIMOM and Solaris Management Console server on the local host. NOTES
When the init.wbem script is run, it does not run the CIMOM and Solaris Management Console server directly. The server process is in Java and is too heavyweight to be run immediately at system boot time. Instead, three lightweight processes listen on three different ports that the CIMOM and the Solaris Management Console server normally use. This acts similarly to inetd(1M). Because Java programs cannot inherit file descriptors as other programs can, there is a small time period from when the first connection is made until the server is fully operational where client connections may be dropped. WBEM clients are immune to this, as they will retry until the server comes online. Solaris Management Console clients are not immune, and it may be necessary to manually reconnect, though this should not happen in the common case. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWwbcor | +-----------------------------+-----------------------------+ SEE ALSO
inetd(1M), mofcomp(1M), smc(1M), smcconf(1M), wbemadmin(1M), wbemlogviewer(1M), attributes(5) SunOS 5.10 2 Jan 2002 init.wbem(1M)