02 Sep 10 Website Speed Booster

The Website Speed Booster is a feature unique to Gossimer, and is available ONLY with the Linux Web Hosting Package. This tool automatically enhances the speed of your website by up to 20 times and more!

How does it work?

The Website Speed Booster works by compressing the content delivered to the client when it is sent across the Internet, making use of the browser’s ability to uncompress this data seamlessly. The tool does not require any changes in website code, nor does it require any additional software on the user’s end. All browsers starting from Internet Explorer 4.0, Netscape 4.06, Opera 5, Lynx 2.6 support this feature. Besides, this solution will simply not compress the data if the visitor has a non-compliant browser, so it presents no risk to your website at all.

Using this tool from your Control Panel, you can boost the speed of all of the following:

All static pages i.e. html, js, css files etc
All dynamic pages i.e. php, perl, cgi, python files etc
All images and downloadable files, such as .gif, .jpg, .png, .doc, .pdf, .xls and so on.

Specifying Speed Booster settings

Follow the process mentioned below to specify your Website Speed Booster settings:

1. Login to your Control Panel and search for the domain name for which you have purchased this hosting package. Click here to read how >>

2. In the search results view, click on the domain name. This will take you to the order details view.

3. Click on Manage Web Hosting Service in the lower toolbar.

4. In the Website Management interface pop-up that follows, go to Manage Website -> Web Server Manager -> Website Speed Booster.

5. On this page, select Yes from the drop-down adjacent to the type of content you wish to optimize. You can choose to boost

Static Content
Dynamic Content
Images and other downloadable articles

For disabling the feature, you need to select No from the drop-down.

6. Click on Submit.

IMPORTANT

In order to complete the action, the Web Server needs to be restarted. Random restarts affect other services running on the Server. In order to avoid this, the Server has been scheduled to restart at intervals of 20 minutes. Hence, the change might take upto 20 minutes to be effective.

Tags: Additional Software, Content Images, Css Files, Details View, Doc Pdf, Downloadable Articles, Gif Jpg, Gt 2, Gt Web, Internet Explorer, Linux, Linux Web, Manage Web Hosting Service, Management Interface, Manager Gt, Opera 5, Pdf Xls, Perl, Php, Speed Booster, View 3, Web Hosting package, Web Hosting Service, Web Server, Web Server Manager, Website Management

Filed in Linux Hosting Specific Features with 0 Comments

29 Aug 10 Debugging Perl/CGI Scripts

Hosting servers are configured to store error logs for CGI/Perl scripts, encountered during the course of operation. By default, error messages are sent to STDERR.

Most HTTPD servers direct STDERR to the server’s error log, which stores information for all the websites hosted on a shared hosting environment. As this, this file cannot be accessed by individual website owners. You may wish to keep private error logs, distinct from the server’s error log, or may wish to direct error messages to to a web browser.

This can be accomplished by coding your scripts accordingly during the development phase.

Sending error messages to a private log file

The carpout() function can be used to achieve this. Since carpout() is not exported by default, you must import it explicitly as -

use CGI::Carp qw(carpout);

The carpout() function requires one argument, which should be a reference to an open filehandle for writing errors. It should be called in a BEGIN block at the top of the CGI application so that compiler errors will be caught. Example:

BEGIN {
use CGI::Carp qw(carpout);
open(LOG, “>>/domains/domain.com/logs/cgi-error.log”) or
die(“Unable to open cgi-error.log: $!n”);
carpout(LOG);
}

carpout() does not handle file locking on the log for you at this point.

Sending error messages to a Web Browser

Fatal (die, confess) errors can be sent to a web browser by importing the special “fatalsToBrowser” subroutine:

use CGI::Carp qw(fatalsToBrowser);
die “Couldn’t open log file”;

Fatal errors will now be echoed to the browser as well as to the log file. CGI::Carp arranges to send a minimal HTTP header to the browser so that even errors that occur in the early compile phase will be seen. Nonfatal errors will still be directed to the log file only (unless redirected with carpout).

Sample Script

#!/usr/bin/perl -wT

# In the first line above, T causes Perl to check
# for “tainted” data, that is, data from outside the
# script (i.e. user input) that is going to be used
# to affect something else outside the script
# (i.e. writing to a log file)

# You can untaint data by parsing it for unwanted
# characters then saving it to another variable.

# If you are having trouble with a script, try removing
# the T switch to see if that is the problem.

# The w switch in the first line causes warnings about
# script syntax to be printed, if there are any.

# This script does 2 things:
#
#1. It directs fatal errors to the browser,
# so when the script is invoked via the Web,
# a meaningful error message is returned.
# This is useful when developing a script;
# but should be disabled when the script
# is made publicly available.
#
# 2. It will direct any error message the script
# generates to an error log that resides in
# the user’s home directory. The file must
# already exist and be “other” writeable.

# Notice that the following is enclosed in a BEGIN { }
# block that causes it to execute before the rest of
# the script is read.

# This block should be placed in the main script,
# as near the top as practical. Do not place it in
# subroutines or libraries. Always test
# subroutines thoroughly before placing them
# in libraries.

BEGIN {

# define an error log in YOUR home directory
# this is an example where the
# home directory is /domains/domain.com/

my $error_log = “/domains/domain.com/logs/cgi-error.log”;

# “my” in the line above makes the variable $error_log
# local so it only has meaning inside this block.
# See your text for more on variable scope.

# load the CGI::Carp module;
# fatalsToBrowser directs fatal errors to the browser
# carpout is for directing errors to the error log

use CGI::Carp qw(fatalsToBrowser carpout);

open (LOG,”>>$error_log”) ||
die “couldn’t open log file: $!”;
carpout(LOG);

# open(…) is used to open a file.
# >> means the new input will be appended what’s
# already in the file.

# LOG is a nickname (properly called a “file handle”)
# that is given to the file so it is easy to refer to
# it later, i.e. carpout(LOG) sends the error
# message to the file with the nickname LOG

# || means “or” (as in do this or that)
# die means stop executing the program. You can add
# a message in quotes after the die command.

# $! is a special variable that contains the current error info

}

# The following line will cause an error.
# It is a call to a sub-routine that does not exist.
# After you have tried this script and received the error message,
# comment out the following line so no error occurs
# and “Hello world!” is printed.

&non_existent_subroutine();

print <<EOT;
Content-type: text/htmlnn

<HTML>
<BODY>
Hello world!
EOT

print “</BODY></HTML>”;

Tags: CGI, Cgi Application, Cgi Hosting, Cgi Perl Scripts, Compiler Errors, Default Error Messages, Development Phase, Domain, Error Logs, Hosting Servers, HTML, http, Http Header, Httpd Servers, Perl, Perl Cgi Scripts, Script Perl, Subroutine, Web Browser, Wt

Filed in Linux Hosting related Caveats with 0 Comments

22 Aug 10 Read this FIRST: Reseller Account Startup Guide

As a Reseller, you need to make the following settings within your Reseller Control Panel to begin selling Products and Services to your Customers and Sub-Resellers.

1. Select your Selling and Accounting Currency

At the time of sign-up, you MUST select your desired Selling and Accounting Currency.

Click here to see a video on setting your Selling and Accounting Currency >>
Click here to read an article on setting your Selling and Accounting Currency >>

2. Add Funds in your Reseller Account

To let your Customers and Sub-Resellers buy Products and Services through you, you need to add sufficient Funds in your Reseller Account with . How? >>

3. Understand the relationship between Resellers, Customers, Sub-Resellers and Orders

Click here to see a video on an Introduction to Customers, Sub-Resellers and Orders >>

4. Decide which Products and Services to sign-up for, and configure them

Gossimer offers a wide-array of Products and Services that you can choose to sell. Select the services that you wish to sell, and sign-up for them from your Control Panel. How? >>

Once you have signed up for these Products and Services, you need to configure various settings before you get started

Click here to see a video on setting up your Domain Registration Business >>
Click here to read the Domain Registration Reseller Setup Guide >>

Click here to read the Domain/Mail Forwarding and Managed DNS Reseller Setup Guide >>

Click here to read the Web Hosting Reseller Setup Guide >>

Click here to read the Email Hosting Reseller Setup Guide >>

Click here to read the Website Builder Reseller Setup Guide >>

Click here to read the Live Chat Reseller Setup Guide >>

Click here to read the Digital Certificate Reseller Setup Guide >>

5. Configure your website

Gossimer offers you various methods of setting up your own Website to sell various Products and Services integrating your Sales process with our system. You could either

Use our ready-made private labeled SuperSite for all your retail business

Click here to read the SuperSite Guide >>

You MUST do the following if you are using the SuperSite -

Change the URL for your SuperSite. How? >>
Customize the header/footer of Supersite. How? >>
Specify the Additional Payment Options for your Customers/Resellers in the SuperSite. How? >>
Customize the content of the Static bar on your SuperSite. How? >>
Customize the content of the Contact Us page on your SuperSite. How? >>

AND/OR

Use our ready-made private labeled PartnerSite for all your wholesale business

Click here to read the PartnerSite Guide >>

You MUST do the following if you are using the PartnerSite -

Change the URL for your PartnerSite. How? >>
Customize the header/footer of PartnerSite. How? >>
Customize the content of the Static bar on your PartnerSite. How? >>
Customize the content of the Contact Us page on your PartnerSite. How? >>

OR

Create your own website using our API

Along with your Reseller account you get a comprehensive API with FREE client kits in PHP, Java, Perl and .NET. All Resellers have API access to the system. Every functionality of the system is available as an API CALL.

Click here to learn more about the API >>

NOTE: The API Integration method is recommended only if you have a proficient development team.

6. Configure Control Panels for your Customers and Sub-Resellers

provides you with comprehensive private-labeled control panels for your Customers and Sub-resellers in order to manage the products and services they purchase from you. You can either -

Use our ready-made private labeled Control Panels

The Control Panels allow your Customers and Sub-Resellers to place, manage, upgrade, downgrade, use, renew, delete, suspend/unsuspend, lock their Orders for various Products and Services from a single management window.

You MUST do the following if you are using the Control Panels -

Set your company logo on top of your Customer/Sub-Reseller Control Panels. How? >>
Customize the Footer of your Customer/Sub-Reseller Control Panels. How? >>

Build your own Control Panels using our API

If you are already selling several other products and services to your existing customer-base through another interface/control panel and do not want to add the burden of introducing the new Control Panels to them, you could use the OrderBox API to integrate provisioning and management of all OrderBox Products and Services in your existing interfaces and Control Panels.

Gossimer provides you comprehensive API kits in Java, PHP, Perl and .Net. You can use any of these to integrate with the system. More on API >>

The API Integration method is recommended only if you have a large Customer base and employ the services of a proficient development team.

7. Integrate your Website and Shopping Cart with your Customer Control Panel

Once you have configured your website and Control Panels for your Customers in steps 5 and 6 above, you should configure the integration between your Customer Control Panels and your website, so that your Customers can jump from their Control Panels to your website to make any purchases. Click here to learn how you can do this >>

8. Update your Contact Information

Personal Details: Personal Information such as your Personal details, your Brand Name, your Website URL, your personal Language preferences, can be easily reviewed and modified from your Reseller Control Panel. How? >>

Company Contact Information: The system automatically sends emails to your Customers and Sub-Resellers from the e-mail addresses and From Names specified in your Contact Information section.

You should update the contact details of various departments in your company, to ensure that all communication with your Customers and Sub-resellers is carried out using your branded email addresses and email signatures. How? >>

9. Configure your Payment Collection options

Setup your Online Credit Card Payment Gateway: The system allows you to integrate any Payment Gateway of your choice to collect money online from your Customers and Sub-Resellers.

Click here to read the Payment Gateway Integration Guide for more details >>
Click here to learn ho you can define the Minimum Transaction Amount for a Payment Gateway Transaction >>

Specify offline Payment Collection Methods for the SuperSite: Apart from collecting funds via a payment gateway, you should also describe other offline means of receiving funds from your Customers, during their shopping process, within the SuperSite. How? >>

Specify offline Payment Collection Methods for the Control Panel: You may also present other offline means of receiving funds to Customers/Sub-Resellers who wish to pay you from within the Control Panels e.g. your Bank details for receiving Bank/Wire Transfers, your Company Details to receive Check/Draft payments. How? >>

Configuring Payment Collection Parameters: You can let OrderBox assist you in collecting payments from your Customers by specifying appropriate Payment Collection Parameters for every Product and Service, that you are selling through OrderBox. How? >>

10. Configure Other Miscellaneous Options

Set your Funds Threshold Level: You should ensure that you always have a healthy balance in your Advance Account with to allow execution of your Customers and Sub-Resellers orders, by defining your Funds Threshold Level from inside your Control Panel, so that OrderBox can remind you via e-mail when your balance falls below this level. How? >>

Company Users: Create special logins for your (sales, support etc.) company users to enable them manage your business efficiently. Control all access for these accounts; and restrict specific menus from being viewed through them. More >>

Sub-Reseller Sign-up options: OrderBox lets you control Sub-Reseller sign-ups under you. More >>

Tags: Accounting, Api, Array, Bank/Wire Transfers, Control Panels, Currency, Digital Certificate, DNS, Domain Mail, Domain Registration Business, Email, Email Hosting, Email Setup, Gossimer, Gt 2, Gt 4, Gt 5, Java, Live Chat, Mail Forwarding, Online Credit Card Payment, Perl, Php, Read Email, Read Mail, ready-made private, Relationship, Reseller Account, Reseller Control Panel, Resellers, retail, Setting Up Your Own Website, Startup Guide, Static Bar, Web Hosting, Web Hosting Reseller Setup Guide, Website Builder

Filed in Reseller Guides with 0 Comments

21 Aug 10 Read This FIRST – General API Integration Instructions

The API is exposed using SOAP, a common web services protocol. SOAP is extremely simple to use and debug since it is an XML based protocol. While SOAP is a standardized protocol, we are using certain complex data types which are not completely compatible across all platforms. However we have written our own wrappers to handle this and we offer direct integration kits in various platforms which you can directly download and use.

IMPORTANT

When our System receives a request, it tries to complete the action immediately. If the System is unable to complete the action for some reason, it will return an error response and try to complete the action again after sometime. This ensures a high level of fault tolerance.

Due to this, it is imperative that when you encounter an error response (especially for commands that have financial implications like Registering or Renewing orders), you MUST check whether the command eventually failed or succeeded. To do this, you will have to issue additional API commands (depending on the command for which you received an error response) to check the final status of the original command.

It is recommended that you implement this querying process to check the status of API commands as a scheduled task/cron/batch process. Alternately, you can also check the status of the command by logging into your Reseller Control Panel.

Currently integration kits are available in PHP, Java, Perl and .NET. Our Server exposes all relevant methods using SOAP. SOAP is a simple XML-HTTP based protocol whose client implementations are available in EVERY language. Follow the steps below to begin making calls to the API -

Step 1. Sign up for a Demo Reseller Account
You will initially test your API scripts on our demo Server. Click here to read how to sign up for a demo Reseller account >> .

You will need the following items before you proceed to the next step

Your Signup Username
Your Signup Password
Your Parent ID

The first two items would have been entered by you during the signup. For the last item simply login to your Demo Account and click on Settings -> Personal Information -> Primary Profile.

IMPORTANT

You can use these accounts to try out various aspects of the system. However, the demo accounts are reset every day. As such, any additional orders placed herein, or any modification done to these accounts, shall cease to exist after 24 hours.

Step 2. Proceed to the corresponding API kit for your platform
Click on the links below to refer to further instructions for the platform you are developing on -

Java API Kit >>
PHP API Kit >>
.NET API Kit >>
Perl API Kit >>

Step 3. Download the API Documentation
The complete documentation of all classes and methods available in the API can be found in the Docs below. The Docs below are javadocs, but the function names and explanations remain the same for all the platforms and the documentation is self explanatory. We recommend you download the docs and read through them completely once before you integrate your application:

Core Docs v3_10
Domains Docs v3_10
Hosting Docs v3_10
Other Products Docs v3_10

Step 4. Refer to the Parameter Validation details of different parameters passed in any API Calls
We have a detailed document on the Validation routines which you need to build in for the various parameters which you send to the API call. Failure to validate these fields on your side may result in an undecipherable error from the Server. Click here to read about Data Validation of Parameters passed in an API Method Call >>

Step 5. Refer to the Error format document and the common errors
The first time you run any example you are likely to encounter errors if you have not followed the steps perfectly. It is important to understand the format of an error. Click here to understand the format of an error that you will receive >>

IMPORTANT

Sometimes, you may receive a 302 HTTP Redirect response from our System. Your API implementation should be capable of following such a redirect.

Step 6. Run the examples
All the above kits contain examples which you can run and test the API functionality. Try these examples out to verify everything is working fine. You should first run these examples on the Demo Server. Use the demo sign up information gathered above and the Demo Server URL below to run the examples on the demo server.

Demo Server URLs for API Kits ver 3.x and above

Java and PHP API Kits

http://api.onlyfordemo.net/anacreon/servlet/APIv3
https://www.foundationapi.com/anacreon/servlet/APIv3

Perl and .NET API Kit

http://api.onlyfordemo.net/anacreon/servlet/APIv3-XML
https://api.onlyfordemo.net/anacreon/servlet/APIv3-XML

Demo Server URLs for older API Kits

Java and PHP API Kits

http://demo.myorderbox.com/anacreon/servlet/rpcrouter
https://demo.myorderbox.com/anacreon/servlet/rpcrouter

.NET and Perl API Kits

http://demo.myorderbox.com/anacreon/servlet/XMLrpcrouter
https://demo.myorderbox.com/anacreon/servlet/XMLrpcrouter

Step 7. Refer to common errors
In this documentation we have some answers covering common errors you can expect while integrating with the API. Click here to know details about common API errors >>

Step 8. Change the information to Live information when you are ready
Once you have followed the steps above and got the test programs to work successfully, you can duplicate the same code in your live application and replace the Demo Server and Reseller account information with your live username and password. You will also need to change the server URL to the live server URL.

LIVE Server URLs for API Kits ver 3.x and above

Java and PHP API Kits

http://www.myorderbox.com/anacreon/servlet/APIv3
https://www.myorderbox.com/anacreon/servlet/APIv3

Perl and .NET API Kit

http://www.myorderbox.com/anacreon/servlet/APIv3-XML
https://www.myorderbox.com/anacreon/servlet/APIv3-XML

LIVE Server URLs for older API Kits

Java and PHP API Kits

http://www.myorderbox.com/anacreon/servlet/rpcrouter
https://www.myorderbox.com/anacreon/servlet/rpcrouter

.NET and Perl API Kits

http://www.myorderbox.com/anacreon/servlet/XMLrpcrouter
https://www.myorderbox.com/anacreon/servlet/XMLrpcrouter

Refer to the corresponding kit and integration guide of the platform that you choose for further instructions.

IMPORTANT

As you duplicate your code on the live application environment, remember to change your Parent ID to the one associated with your Live Reseller account. You can find this from Settings -> Personal Information -> Primary Profile in your Reseller Control Panel.
You need to display the Registrar Registrant Agreement for Domain Names Legal document within the domain name registration buy process on your website.

It is compulsory to display this document AS IS to your Customers and get them to agree to the terms mentioned therein, before buying domain names through you. You can view this agreement from within your Reseller Admin Control Panel at Help >> Legal Agreements.

Tags: Api, Api Commands, Data Types, Demo Server, Exposed, Fault Tolerance, Financial Implications, http, Integration, Java, Java Perl, Net Server, Parent, Parent Id, Perl, Php, Platforms, Protocol, Registrar, Relevant Methods, Reseller Account, Reseller Control Panel, Soap Soap, standardized protocol, Test Scripts, web services protocol, www.foundationapi.com/anacreon/servlet/APIv3, www.myorderbox.com/anacreon/servlet/APIv3, www.myorderbox.com/anacreon/servlet/APIv3-XML, www.myorderbox.com/anacreon/servlet/rpcrouter, www.myorderbox.com/anacreon/servlet/XMLrpcrouter, Xml

Filed in Reseller API Guide with 0 Comments

13 Aug 10 Change Log

Changes in version 3.10

Java Docs updated

Changes related to classes and methods:

New Classes and Methods

Domains Kit

New Class Name New Method

ThirdLevelDotUk String invoiceOption

ThirdLevelDotUk String existingEndTime

New Parameters introduced in Existing Methods

Other Products Kit

Class Name Method Name New Parameters

EngageOrder renew String invoiceOption

EngageOrder renew String existingEndTime

Deprecated Parameters in Methods

Domains Kit

Class Name Method Name Deprecated Parameters

ZoneOrder add "No Of Records" in DomainHash

Deprecated Methods

Domains Kit

Class Name Deprecated Method Suggested Class Suggested Method

DomContact addDefaultContact DomContact addDefaultContacts

DomContact add DomContact addContact

DomContact list DomContact listByType

DomContactExt isValidRegistrantContact DomContactExt isValidContact

DomOrder transferDomain DomOrder addTransferDomain

DomOrder add DomOrder registerDomain

ZoneOrder mod ZoneOrder Functionality not required anymore

DotEu tradeDomain DotEu trade

DotEu transferDomain DotEu transfer

DotEu add DomOrder registerDomain

Core Kit

Class Name Deprecated Method Suggested Class Suggested Method

Customer addCustomer Customer signUp

Customer modDetails Customer mod

Reseller addReseller Reseller signUp

Reseller modDetails Reseller mod

Reseller addResellerWithStateId Reseller Functionality not required anymore

OrderSetup getResellerSlabPercentageForProducts OrderSetup Functionality not required anymore

OrderSetup getCustomerSlabPercentage OrderSetup Functionality not required anymore

Changes in version 3.9

Java Docs updated

Changes related to classes and methods:

The following method in the Domains Kit is deprecated and its use should be discontinued -

Deprecated method Class New method to be used

isValidRegistrantContact DomContactExt isValidContact

Changes in version 3.8

Java Docs updated

Changes related to classes and methods:

The following changes have been introduced under the DotEu class within the Domains Kit -
The following new methods have been introduced under DigitalCertificateOrder class within the Other Products Kit -
- enrollForThawteCertificate
- reissue
- renew
- checkDigitalCertificateStatus
- del
- cancelDigicertOrder
- changeDigicertPassword
- addAdditionalLicenses
- getDetails
- getDetailsByDomain
- getOrderIdByDomain

Changes in version 3.7

Java Docs updated

Changes related to classes and methods:

Some old parameters have been removed and new parameters introduced in their place under the following methods -

LinuxHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*, boolean ssl^#
mod	Hashtable orderParams	String packagekey^*, boolean ssl^#, int excessBandwidth^##
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##
getModPricing	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##

WindowsHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*, boolean ssl^#
mod	Hashtable orderParams	String packagekey^*, boolean ssl^#, int excessBandwidth^##
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##
getModPricing	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##

MailHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*
mod	Hashtable orderHash	String packagekey^, int additionalMailBoxes^*
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^, int additionalMailBoxes^*
getModPricing	Hashtable orderParams	String packageKey^, int additionalMailBoxes^*

SiteBuilder Class
Method	Old Parameter	New Parameters
mod	Hashtable orderParams	String packageKey^*
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*

NOTE:
^* packageKey will be the Identifier Key of the Plan (plan1, plan2, plan3, plan4) for which the Order needs to be added/modified.

^# ssl will be true or false depending whether the user wants Dedicated IP / SSL for the Order placed.

^## excessBandwidth is the Bandwidth which the user wants over and above the Bandwidth of the Order’s current plan.

^** additionalMailBoxes is the number of additional mail boxes over and above the existing ones in blocks of 100 accounts.

The following classes and their methods are removed:

LinuxHostingPlanOnlyOrder
WindowsHostingPlanOnlyOrder
MailHostingPlanOnlyOrder

The SiteBuilderLite class has been renamed to SiteBuilder.

Two new methods, mod and signUp, have been introduced under the Reseller and Customer classes.

Code for registerDomain method in PERL Domains Kit has been modified.

The return type of the ListByType method of DomContact class in the Domains Kit has been changed to Hashtable from Vector.

Changes in version 3.6

Java Docs updated

Changes related to classes and methods:

New methods have been added in the Core Kit under the following class:

getProductMetadata – Product class
New methods have been added in the Domains Kit under the following classes:
getDefaultContactId – DomContactExt class
listByType – DomContact class
addTransferDomain – DomOrder class
changePrivacyProtectionStatus – DomOrder class
registerDomain – DomOrder class
Changes to the DomOrder class in Domains Kit:

The following methods in the Domains Kit are deprecated and their use should be discontinued:

Deprecated method	Class	New method to be used

add	DomContact	addContact
addDefaultContact	DomContact	addDefaultContacts
list	DomContact	listByType
add	DomOrder	registerDomain
transferDomain	DomOrder	addTransferDomain
transferDomainWithoutValidation	DomOrder	addTransferDomain
addTransferDomainWithoutvalidation	DomOrder	addTransferDomain
add	DotEu	registerDomain in DomOrder class

IMPORTANT

While these methods are currently available, they are no longer supported and may be discontinued in the near future.

New methods have been added in the Hosting Kit under the following class:

getHostingMetaData – WebHostingOrderData class

Changes to classes in the Hosting Kit:

The invoiceOption parameter has been added to the add method of MailHostingPlanOnlyOrder, WindowsHostingPlanOnlyOrder and LinuxHostingPlanOnlyOrder classes

Changes in version 3.5

Java Docs updated

Changes related to classes and functions:

New functions have been added in the Core Kit under the following classes:

getList – Country class
getStateListForCountry – Country class
getDetails – Order class
addResellerWithStateId – Reseller class
An extra option called Supersite is added in the getDetails function of the Reseller class in the Core Kit.
A new class LegalAgreement is added with the following methods under the Core Kit:
getRegistrantAgreement
getProductCategory
getAgreement
getAllAgreements
A new function has been added in the Domains Kit under the following class:
addCoopContact – DotCoopContact class
The following functions in the DomOrder class in the Domains Kit are changed to show the Invoice options also:
validateDomainRegistrationParams
validateDomainTransferParams
addWithoutValidation

Changes in version 3.4

Java Docs Updated

New Classes introduced in all Kits:

Core Kit

TaxService
getApplicableTaxes
getHashedTaxRules
Domains Kit

DotEu
    getEUCountryList
    tradeDomain
    transferDomain
    add
    isEUCountry

DotEuContact
    mod
    add
    addEuDefaultContact

DomOrder
    validateDomainRegistrationParams
    validateDomainTransferParams
    addTransferDomainWithoutvalidation
    addWithoutValidation
Hosting Kit

WindowsHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount

LinuxHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount

MailHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount
    list

MailHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap

WindowsHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap

LinuxHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap
Other Products Kit

DigitalCertificateOrder
    add
    getCertPrice

SiteBuilderSetup
    getPricingKeyPricingParamMap

EngageSetup
    getPricingKeyPricingParamMap

Changes in version 3.3

3 new functions have been added in the Core Kit under the following classes:

authenticateCustomerId – Customer class
login – Customer class
getOrderIdByDomainAndProductCategory – Order class

Bug Fix – A minor Java Script problem was causing the frame links in the examples to not work in some browsers like Mozilla and Opera.

Changes in version 3.2.1

WSDL Endpoint changed

Changes in version 3.2

New methods added viz. Order.removeCustomerLock, Order.getLockList

Changes in version 3.1

Minor bugs in WSDL files fixed.

Version 3.0 Released

Extensive changes made. Please download the kit and read the appropriate Javadocs for details.

Changes in version 2.6

Added the method Customer.delete() which allows you to delete a Customer

Added the method DomOrder.cancelTransferRequest() which allows you to cancel the transfer-in request for a domain name

Added the method Order.sendRfa() which allows you to re/send the email asking for transfer-in approval for domain names.

Changes in version 2.5

Bug fix in Modify Customer Details and Modify Contact Details forms

More details in the Javadocs for DomOrder.getDetails()

Link to new Demo Server added.

Version 2.3

Perl API KIT added

Tags: Api, Java, Perl, SSL

Filed in Perl API Kit with 0 Comments

09 Aug 10 Perl-based Form Mail (Feedback) Script

Sample Script and its Configuration Options

Click here to download the sample script >>

IMPORTANT

It is recommended that you refer to the Readme file (available within the above sample script archive) to learn how to configure this script to work on your website.

Sample HTML Feedback Form

The following lines needs to be added in the form which connects to the FormMail.pl script:

Following is the explanation about the above mentioned variables:

recipient – Here you need to specify the Email address, where the email containing the data submitted through the form, needs to be delivered.
email – You would need to change the Email address in the field email to any Email address on the domain name, on which you are incorporating this script. For example, if you are deploying this script on your Domain Name abc.com, then you would define the From Email address as some-name@abc.com. This Email address need not be existing on the Mail Server of abc.com, however, the domain name in the email field has to be yours. This implies, that you may use an Email address such as Do_Not_reply@abc.com. This email address will appear as the From email address in the email sent by the script.
realname – The value here indicates the name mentioned in the From section of the email, that will be sent to the email address, upon submission of this form. This can be modified as per your requirement.
subject – The value in this field can be changed to indicate an appropriate subject for the mail to be sent. For example, you may set this as YourDomainName.com Feedback Form or any other subject that would allow you to uniquely identify from which form on your website this data has been received.
redirect – Once the visitor provides feedback, he/she can then be redirected to another page on your website. In order to achieve this, you need to mention the path to the HTML file in the redirect field. Alternately, you can display a message to the visitor thanking him/her for the feedback. Such messages can be displayed in a new page like thanks.htm. Such a page can also contain other information as deemed necessary.

Tags: Abc, Configuration Options, Domain Name, Email Address, Feedback Script, Form Mail, Formmail Script, HTML, Input Type, Lt, Mail Feedback, Mail Script, Mail Server, Perl, Perl Mail, Pl Script, Readme File, Recipient, Sample Html, Script Archive, Value Feedback, Variables

Filed in Feedback Forms with 0 Comments

09 Aug 10 Procedure To Retrieve XML Sent And Received

While using one of the API kits, if you encounter any error that you need to report to Gossimer, you would need to provide the XML sent and received for the call you were making. Following is the procedure that you need to follow to retrieve the XML, for the various API kits we provide:

1. PHP kit: Set the debug value to true in the lib/config.php file

2. Perl kit: Set the $debugMode to 1 in /examples/cgi-bin/constants.cgi/font/index.html>

3. .NET kit: Set the static property Properties.Debug = True in statics.aspx

Having retrieved the XML sent & received, please contact us at support@gossimer.com, along with the following details:

your Reseller Username
Service URL you were using
API kit Language

Tags: Api, HTML, Perl, Php, Xml

Filed in Reseller API Guide with 0 Comments

08 Aug 10 Fix File Permissions Manager

There are certain requirements to be met for the smooth functioning of your website such as

Certain files such as CGI and Perl scripts need to have a specific permission.
Similar permission needs to be set for the immediate parent directory containing these files.
Certain files/folders generated through scripts or power tools will have nobody as their owner and group. The primary FTP user and site group for your website needs to be the owner and group of such files/folders.

Gossimer Linux Hosting Control Panel provides a tool to fix permission issues with such files/folders.

Follow the process explained below to use this tool:

Login to your Control Panel, search for the domain name for which you have purchased this Linux Web Hosting package and proceed to the Order Details view. Click here to know how >>

Click Manage Web Hosting Service in the lower toolbar.

In the Website Management interface pop-up that follows, go to Manage Website -> Additional Tools -> Fix CGI Permissions. This will open the Fix File Permission Manager view.

Files/folders whose permission need to be fixed are listed here. Clicking Submit button will set the permission as listed against each file/directory displayed in this Fix File Permission Manager interface.

Tags: Additional Tools, CGI, Click Manage Web Hosting Service, Control Panel, Details View, Domain Name, File Folders, Fix File Permission Manager, Fix File Permissions Manager, Linux, Linux Web, Management Interface, Manager Interface, Manager View, Perl, Perl Scripts, Permission Issues, Power Tools, site group, Tool, Web Hosting package, Web Hosting Service, Website Management

Filed in Linux Hosting Specific Features with 0 Comments

07 Aug 10 Perl API Kit and Integration Guide

Follow the instructions below to begin integration with the API using Perl -

Make sure you have read the General API Integration Instructions first. If you have already integrated the PERL API Kit at your end, read the Change Log first to know what has changed since.

Reference:

General API Integration Instructions >>
Change Log >>

Step 1. Download the API Kit
Click the link below to download the relevant API kits (updated on 6th March, 2008).

PERL_CoreKIT_v3_10.zip
PERL_DomainsKIT_v3_10.zip
PERL_HostingKIT_v3_10.zip
PERL_OtherProductsKIT_v3_10.zip

Step 2. Download the API Documentation
The complete documentation of all classes and methods available in the API can be found in the Docs below. The Docs below are javadocs, but the function names and explanations remain the same for all the platforms and the documentation is self explanatory. We recommend you download the docs and read through them completely once before you integrate your application (updated on 6th March, 2008).

Core_Docs_v3_10.zip
Domains_Docs_v3_10.zip (updated on 1st April, 2008)
Hosting_Docs_v3_10.zip
OtherProducts_Docs_v3_10.zip

Instructions to pass parameters to functions using the Perl Kit

Since Perl uses typeless variables you will have to ignore the datatypes presented in the docs. But for assigning values to variable of types other than strings and integers special care will have to be taken. Below is the list of datatypes presented in the API Doc and their usage in Perl.

Java Data	Types Assigning values in Perl
String	“firstname@secondname.com”
int	123
HashMap (Datatype for storing name-value pair)	{“domain1.com”=>1,”domain2.com”=>1}
Array and Vector (Datatype for storing more than one value)	["ns1.domain.com","ns2.domain.com"]
boolean (Datatype for storing true or false)	TRUE / FALSE

Example:

For Calling a Function which takes a String datatype and an integer datatype as its paramters

public int function1(java.lang.String userName, int parentid)
$result = $obj->function1(“firstname@secondname.com”,1);
For Calling a Function which takes a HashMap, a String Array and an integer Array as its parameters, where domainHash contains the domainname and the number of years as name value pairs.

public java.util.HashMap function2(java.util.HashMap domainHash, java.lang.String[] orderby, int[] resellerId)
$result = $obj->function2({“domain1.com”=>1,”domain2.com”=>2},["column1","column2"],[22,33])
For Calling a Function which takes a Vector and a boolean as its parameters

public java.lang.String function3(java.util.Vector nameServers, boolean add)
$result = $obj->function3(["ns1.domain.com","ns2.domain.com"],TRUE)

Step 3. Extract the files from the API Kit archive
You should get the following directory & files structure

cgi-bin/ – Pre-written examples. You can directly run these examples to test API functionality
lib/ – The Perl classfiles, library files and wsdl files that you need to run your application

Step 4. Run the examples
You can run the pre-written examples provided in the “examples” folder. Note the following steps to do so -

1. Upload the “examples” and “lib” folders to your web server where you run your Perl scripts. Make sure that both these folders are uploaded to the same parent folder.

2. You must have a recent version of Perl installed on the server.

IMPORTANT

Please do NOT use a version of SOAP-Lite newer than 0.60, which is the current stable release.

3. You must have a Demo account ready the first time. Read the General instructions if you have not yet setup your demo account. Reference: General API Integration Instructions >>

IMPORTANT

The Demo server duplicates all functionality of the live server, however all Domain Names will appear as available on the Demo Server. It does not query the live registry and therefore names which are not available on the live registry will still appear as available on the Demo Server. At times connectivity to the DEMO Registry may be down resulting in errors.

4. Make the appropriate changes to the “constants.cgi” file in the “cgi-bin” folder, by putting in the values for your “username”, “password” and “parentid”. The remaining settings have already been made for you in this file. You may only need to change the path for the “wsdl” folder if you have uploaded the wsdl folder elsewhere.

5. The URL to which the call is made is maintained in the “config.sh” file inside the “lib” folder. You can make changes to this file and redirect your calls to the appropriate server.

6. Import and point to note is that you will have to execute the config.sh file from the cgi-bin directory after making any changes in this file to reflect the changes.

7. Every Example file has a set of functions which you can run.

8. Once you have modified the appropriate example file, access it over your webserver by putting in your URL such as http://yourserver/examples/html and choose the required function from the links given in the left frame.

IMPORTANT

In registering/managing any domain name on the demo server always use ns1.onlyfordemo.net and ns2.onlyfordemo.net as your nameservers. ANY OTHER Nameserver will result in an INVALID NAMESERVER error.

Step 5. Understanding Errors
Make sure you have read the General API Integration Instructions to obtain links to the error format and possible error documents. Reference: General API Integration Instructions >>

Step 6. Writing your own code
After running each example above, if you simply refer to the corresponding .Perl file in the lib folder you will easily be able to figure out the code snippet you need to write in order to make a similar call.

Making an API call to perform any action is a matter of three steps:

(i) Include the appropriate Perl package as below

use lib::Customer;

(ii) Obtain a pointer to the required Class. This is done by using the code below

our $Customer = new Customer($debugMode);

(iii) Call the required method on this object. A complete reference of all methods is available in the Docs folder. This can be achieved by using the code below

$Customer->wsdlURL($wsdlFile);
$Customer->StartServices()
my @param = ($SERVICE_USERNAME, $SERVICE_PASSWORD, $SERVICE_ROLE, $SERVICE_LANGPREF, $SERVICE_PARENTID, $customerUserName, $customerPassword, $name, $company, $address1, $address2, $address3, $city, $state, $country, $zip, $telNoCc, $telNo, $altTelNoCc, $altTelNo, $faxNoCc, $faxNo, $customerLangPref);

IMPORTANT

You will notice above that EVERY method in the docs takes the same first 5 parameters as below

String SERVICE_USERNAME, String SERVICE_PASSWORD, String SERVICE_ROLE, String SERVICE_LANGPREF, int SERVICE_PARENTID

In the examples these parameters have been put into a single constants file from which they are accessed by including the constants file. These parameters are common no matter which method you call. These parameters mean the following

String SERVICE_USERNAME: Your Username String SERVICE_PASSWORD: Your Password String SERVICE_ROLE: This will always be a string "reseller" String SERVICE_LANGPREF: The 2 letter code of the language in which you wish to receive errors and descriptions - "en" for English int SERVICE_PARENTID: The ID of your parent which you can get from your profile section

Step 7. Change the information to Live information when you are ready
Once you have followed the steps above and got the test examples to work successfully, you can duplicate the same code in your live application and replace the Demo Server and Reseller account information with your live username and password. You will make this change in the “config.sh” file in the “lib” folder

Tags: Api, appropriate server, Demo Server, Java, Perl, Web Server

Filed in Perl API Kit with 0 Comments

02 Sep 10 Website Speed Booster

22 Aug 10 Read this FIRST: Reseller Account Startup Guide

21 Aug 10 Read This FIRST – General API Integration Instructions

13 Aug 10 Change Log

09 Aug 10 Perl-based Form Mail (Feedback) Script

09 Aug 10 Procedure To Retrieve XML Sent And Received

08 Aug 10 Fix File Permissions Manager

07 Aug 10 Perl API Kit and Integration Guide

Recent Posts

Some good Links

Favorite Gossimer Links

Categories

Tags

Gossimer in the News

Gossimer Promotions and Announcements

Domains Kit
New Class Name	New Method
ThirdLevelDotUk	String invoiceOption
ThirdLevelDotUk	String existingEndTime

Other Products Kit
Class Name	Method Name	New Parameters
EngageOrder	renew	String invoiceOption
EngageOrder	renew	String existingEndTime