Gossimer’s Premier Web Hosting and Domain Registration Knowledgebase.
Follow the below mentioned process to install the PHP-Nuke Power Tool on your website:
1. Login to your Control Panel and search for the domain name for which you have purchased a Linux hosting package. Click here to know how >>
2. In the search results view, click on the domain name. This will take you to the Order details view.
3. Click on the Manage Web Hosting Service button in the lower toolbar.
4. Go to Manage Website -> Power Tools. This will present you with a list of Power Tools offered.
IMPORTANT
If you have already installed the PHP-Nuke Power Tool, then instead of the Install link, the Uninstall link would be visible. You may view the details of the existing installation by clicking on the View link under the Details column.
5. In order to install PHP-Nuke, click on Install link under the Status column.
6. In order to install the PHP-Nuke Power Tool you would need to simply input the following details -
i. Database Name – select the database from the drop-down list.
ii. Database Username – select (one of) the Database User(s) whom you have associated with this database, from the drop-down list.
iii. Database User’s Password – provide the password of the Database User, you selected above.
iv. Directory Name – you need to input a new sub-directory name where you want the PHP-Nuke Power Tool to be installed on your website. This sub-directory will be directly under your web directory. You need to provide the directory name without any trailing forward-slash (/).
IMPORTANT
Confirm that you have sufficient Web Space and Database Space before continuing the PHP-Nuke installation, by referring the information provided in the interface.
Should you not have enough Web and/or Database Space, you would need to upgrade your package. Click here to read how to upgrade your package >>
7. Click on the Install button to complete the PHP-Nuke installation.
Besides the above information, you need to provide a few details about the PHP-Nuke Administrator:
1. Admin Name – This is the name of the person who will be administering the PHP-Nuke installation.
2. Password – This is the Administrator’s Password.
3. Confirm Password – Re-enter the Administrator’s Password to confirm the same.
4. Admin Email – Mention the Administrator’s Email Address where important notifications will be sent by the PHP-Nuke Power tool.
Once PHP-Nuke is installed, you can click on the View link under the Details column, to view the details related to PHP-Nuke.
IMPORTANT
URL of the PHP-Nuke Image Gallery Management System: http://<yourdomainname>/<directoryname>/index.php
URL of the PHP-Nuke Admin Control Panel: http://<yourdomainname>/<directoryname>/admin/index.php
Tags: administrator, Control Panel, Database Hosting, Database Manager, Database Name, Database Tool, Database User, Details View, Domain Name, Driven Power, Drop Down List, Gt 2, Gt Power, http, Linux, Linux Hosting, Manage Web Hosting Service, Manager Interface, Password Database, Php, PHP-Nuke Administrator, PHP-Nuke installation, Power Tool, Power Tools, Service Button, Status Column, sufficient Web Space, View 3, Web Directory, Web Hosting Service
Follow the below mentioned process to install the WordPress Power Tool on your website:
1. Login to your Control Panel and search for the domain name for which you have purchased a Linux hosting package. Click here to know how >>
2. In the search results view, click on the domain name. This will take you to the Order details view.
3. Click on the Manage Web Hosting Service button in the lower toolbar.
4. Go to Manage Website -> Power Tools. This will present you with a list of Power Tools offered.
IMPORTANT
If you have already installed the WordPress Power Tool, then instead of the Install link, the Uninstall link would be visible. You may view the details of the existing installation by clicking on the View link under the Details column.
5. In order to install WordPress, click on Install link under the Status column.
6. In order to install the WordPress Power Tool you would need to simply input the following details -
i. Database Name – select the database from the drop-down list.
ii. Database Username – select (one of) the Database User(s) whom you have associated with this database, from the drop-down list.
iii. Database User’s Password – provide the password of the Database User, you selected above.
iv. Directory Name – you need to input a new sub-directory name where you want the WordPress Power Tool to be installed on your website. This sub-directory will be directly under your web directory. You need to provide the directory name without any trailing forward-slash (/).
IMPORTANT
Confirm that you have sufficient Web Space and Database Space before continuing the WordPress installation, by referring the information provided in the interface.
Should you not have enough Web and/or Database Space, you would need to upgrade your package. Click here to read how to upgrade your package >>
7. Click on the Install button to complete the WordPress installation.
Besides the above information, you need to provide a few details about the WordPress Administrator:
1. Admin Name – This is the name of the person who will be administering the WordPress installation.
2. Password – This is the Administrator’s Password.
3. Confirm Password – Re-enter the Administrator’s Password to confirm the same.
4. Admin Email – Mention the Administrator’s Email Address where important notifications will be sent by the WordPress Power tool.
Once WordPress is installed, you can click on the View link under the Details column, to view the details related to WordPress.
IMPORTANT
URL of the WordPress Image Gallery Management System: http://<yourdomainname>/<directoryname>/index.php
URL of the WordPress Admin Control Panel: http://<yourdomainname>/<directoryname>/admin/index.php
Tags: administrator, Control Panel, Database Hosting, Database Manager, Database Name, Database Tool, Database User, Details View, Domain Name, Driven Power, Drop Down List, Gt 2, Gt Power, http, Linux, Linux Hosting, Manage Web Hosting Service, Manager Interface, Passwor, Password Database, Php, Power Tool, Power Tools, Service Button, Status Column, sufficient Web Space, View 3, Web Directory, Web Hosting Service, WordPress Administrator, WordPress installation
Gossimer allows you the ability to completely change the look and feel of your SuperSite and PartnerSite through the use of Themes.
What is a Theme?
A Theme is a set of design elements and color schemes that you apply to pages to give them a consistent and attractive appearance. Using a Theme is a quick and easy way to add interest to pages and give them a professional look.
A Theme allows you to alter the appearance of your SuperSite/PartnerSite by modifying its:
- Cascading Style Sheets. By tweaking individual CSS files in your Theme you can modify the fonts, colors, spacing, etc., being displayed on your SuperSite/PartnerSite.
- Images. You can replace the default set of images within your SuperSite/PartnerSite Theme. This is especially useful when you have translated your SuperSite/PartnerSite content and would want to display images with embedded text in that language.
- Javascript. The style of the Javascript Menu within your SuperSite/PartnerSite Theme can be equally easily modified, to suit your customized SuperSite/PartnerSite.
By applying a Theme you can immediately apply a predetermined set of design elements to your SuperSite/PartnerSite content. When you choose one theme to be the default theme for your website, the theme is applied to all existing pages and to new pages that you add later.
How to Add/Modify a Theme or How do I edit the CSS, Images, Javascript of my SuperSite/PartnerSite?
IMPORTANT
- To modify the CSS, Images and Javascript of your SuperSite/PartnerSite, you need to first add a NEW Theme.
- While adding a Theme, you need to select the Default Theme from where you want the default CSS, Images and Javascript to be initially loaded. As you modify these elements, your changes become a part of your new Theme.
Adding a Theme
You can create your own Themes using the default Theme as mentioned below -
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
IMPORTANT
The Default SuperSite/PartnerSite Theme cannot be edited. If you wish to change the look and feel of your SuperSite/PartnerSite, you need to create your own Theme and modify the same.
- In order to create your own Theme, click on the Create Custom Theme link on the top right-hand corner of this page.
- Provide a unique name for your Theme and click Create My Theme. The Theme thus created will be listed under Your SuperSite/PartnerSite Theme(s) section.
- Click on the Browse link next to the Theme to view the contents of the Theme.
- Here you will find folders for CSS (Cascading Style Sheet) files, Images and JavaScript files.
Modifying your Theme (editing your SuperSite/PartnerSite CSS, Images, Javascript)
You can modify the CSS files (Cascading Style Sheets) for different sections of SuperSite and PartnerSite, by following the process outlined below:
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
- Click on Browse besides the Theme which you need to modify.
- Now click on Browse next to the CSS folder.
- This interface lists all the sections. Click on Browse, adjacent to the section for which you wish to modify the style sheets.
- The following page lists all the CSS files used in the section you have chosen. Click on Edit, adjacent to the CSS file you wish to modify.
- You will be presented with two textboxes; one on the left-hand side of the page with the title as Original Content and the other on the right-hand side with the title as My Modified Content. You can make the required modifications in the My Modified Content text box.
- Click on the Save Changes button beneath after completing the modification.
IMPORTANT
If you are not satisfied with the modifications and wish to revert to the earlier setting, simply click on Reset to Default from the Edit page, to restore the default settings for that file.
Virtually every image in SuperSite and PartnerSite is customizable – should you not find any to your liking, you can replace it with another at any time.
IMPORTANT
- In order to modify an image file in SuperSite or PartnerSite, you need to note its name. To get the name of the image, simply right-click on the image in your browser, and select Properties. Here, you would find the address for the image. For example, http://<prefix>.SuperSite/PartnerSite.myorderbox.com/getImage.php?src=image-name.gif, or
http://<prefix>.partnersite.myorderbox.com/getImage.php?src=image-name.gif
where image-name.gif is the name that you require.
- Also, there are some image files which are a part of the CSS itself; you would not be able to retrieve the filenames in the above manner. To retrieve the names of such image files, you need to check the style sheets for the section containing the image in question, and retrieve the image file name from there. Click here to find instructions on how to edit your SuperSite/PartnerSite/PartnerSite CSS files >>
- : You can follow the process mentioned below to replace the default header logo with the logo of your company. To do so, you need to replace the image named yourbrand.gif.
Follow the process outlined below to modify any Image files in your SuperSite/PartnerSite:
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
- Click on Browse besides the Theme which you need to modify.
- Click on Browse link next to the Images folder.
- This interface lists all the images used by the SuperSite/PartnerSite.
- In the list, look for the name of the image you wish to modify. Click on Edit, adjacent to it.
- Click on Browse, and select the image you wish to upload in place of the default.
- Click on Upload Image. This will replace the default Image with the one you have provided, such that every page where the old image file was being displayed, would now display your uploaded image file.
In addition to the default images, you can add/edit your own images as mentioned below:
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
- Click on Browse besides the Theme which you need to modify.
- Click on Browse link next to the Images folder.
- Click on Browse next to the MyUploadedImages folder.
Adding your own Images
- Click on the Add your own Images button on the top right-hand corner of this page.
- Click on Browse, and choose the image that you want to upload.
- Once the image is selected, click on Upload button.
Editing Images added by you
- Click on the Edit link next to the image you wish to modify.
- Click on Browse, and choose the image that you want to upload.
- Once the image is selected, click on Upload Image button.
After uploading an image using the above tool, you would need to link it from some HTML page on your SuperSite/PartnerSite.
IMPORTANT
- If you have translated your SuperSite/PartnerSite content to multiple languages, then you may want to have images with text embedded on them in that particular language itself. To accomplish this you would need to associate different languages to separate Themes and within each Theme have Images related to only that language.
- If you are not satisfied with the modifications and wish to revert to the earlier setting, simply click on Reset to Default from the Edit page, to restore the default settings for that file.
The manner in which the menu is displayed, can be modified just as easily:
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
- Click on Browse besides the Theme which you need to modify.
- Click on Browse next to the JS folder.
- Click on Edit, adjacent to the menu_style.js file.
- You will be presented with two textboxes; one on the left-hand side of the page with the title as Original Content and the other on the right-hand side with the title as My Modified Content. You can make the required modifications in the My Modified Content text box.
- Click on the Save Changes button beneath after completing the modification.
How do I apply a Theme to my SuperSite/PartnerSite?
You can display your SuperSite/PartnerSite in either the Default Theme provided by Gossimer or use any one of the Themes you have recently added. Follow the below mentioned process to accomplish this:
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin Area, click on the Configure Languages and Themes link.
- Here you may either set your Theme for the Default English Language or any other language added by you, by selecting the Theme from the Associated Themes drop-down.
- Click on the Save button to associate the selected Theme to a particular language.
IMPORTANT
The Theme you have selected will be applied to your SuperSite/PartnerSite ONLY after you have enabled that particular language.
Click here to know how to configure Multiple Language support to your SuperSite/PartnerSite >>
Tags: above tool, Attractive Appearance, Cascading Style Sheets, Choose One, Color Schemes, Colors, Css Files, Css Images, Default Theme, Design Elements, Editing Images, Gif, Gossimer, HTML, http, Javascript Menu, Language Javascript, Supersite, Tweaking
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
The Managed DNS, Web Hosting, Email Hosting, Live Chat and Website Builder Orders reside on separate servers from the ones you connect to, via the API Kits. Due to this, your Customers need to login into their (individual) Control Panels, for managing such Orders.
Gossimer now provides you with another method of directly allowing access to your Customer, to manage their Managed DNS, Web Hosting, Email Hosting, Live Chat and Website Builder Orders from your interfaces itself.
To accomplish this, you need to use either of these 2 methods and pass the following parameters to the mentioned URL, via an HTTP POST method:
Method 1 (recommended)
URL – http://<Your_Control Panel_Branded_URL>/servlet/ManageServiceServletForAPI
- orderid – the Managed DNS/Web Hosting/Email Hosting/Live Chat/Website Builder Service Order Id that your Customer wants to manage
- loginid – you need to generate a Login ID, that you need to pass as the value of this parameter for allowing the Customer to manage his Order. This can be accomplished by calling the API method generateLoginID in the Customer class. In order to call generateLoginID, you will have to pass ipAddress as a parameter. This Login ID generated will be valid for a very short period of time and you should use it immediately upon generating it.
- viewdns – the value of this parameter can be either true or false. If you do not pass any value for this parameter, then it is interpreted as false.Pass true – if the Order is Web Hosting or Mail Hosting and you want to allow your Customer to manage the DNS Records of that particular Order.
Pass false – if the Order is Web Hosting or Mail Hosting and you want your Customer to manage only the Web or Mail Hosting Order.
This method is the most secure method of allowing your Customers to manage their Managed DNS, Web Hosting, Email Hosting, Live Chat and Website Builder Orders, since it does not expose the Customer’s Username and Password in your interface.
If you choose to use this method, then you would need to create an intermediate interface to which you can provide the required parameters, and which in-turn generates a valid URL and redirects your Customer.
You need to provide orderid and any authentication details (optional) to this interface. This interface would then call the API method generateLoginID of the Customer class and build a URL with loginid, viewdns and orderid as parameters, and then redirect the Customer to this URL.
Example
Let us call this interface a servlet named ManageOrderBoxControlPanel (assuming that you are using our JAVA API Kit).
- This interface would accept Managed DNS/Web Hosting/Email Hosting/Live Chat/Website Builder Service Order Id as a parameter. So, in order to manage a Service, you will call this interface with http://<Your-Server-URL>/ManageOrderBoxControlPanel?orderid=<orderid>.
- Now this servlet would need to call the API method generateLoginID of the Customer class like -String loginid = API call to “generateLoginID(username,password,resellerid,langpref,role,ipAddress) ;
where,
- username – the Username of the Customer, to whom the Order belongs
- password – the Password of the Customer, to whom the Order belongs
- resellerid – the Reseller Id associated with your Reseller account. This is obtainable from Settings -> Personal Information -> Primary Profile in your Reseller Control Panel.
- role – customer
- The final URL to which you would then redirect your Customer to, would look like - http://<Your_Branded_URL>/servlet/ManageServiceServletForAPI?loginid=<loginid>&orderid=<orderid>&viewdns=<true/false>
The pseudo code for accomplishing the above is as follows:
public class ManageOrderBoxControlPanel extends HttpServlet
{
authentication params = Get Authentication parameters;
orderid = Get OrderBox orderid;
classname = Customer class;
viewdns = false;
set ipaddress with authentication parameters to call “generateLoginID”;
try
Unknown macro: { loginid = API method call “generateLoginID” of Customer class. }
catch()
Unknown macro: { handle exceptional condition. }
url = “http://<Your_Branded_URL>/servlet/ManageServiceServletForAPI?loginid=” + loginid + “&orderid=” orderid + “&viewdns=” + viewdns ;
response.sendRedirect(url);
}
Method 2
URL – http://<Your_Control Panel_Branded_URL>/servlet/ManageServiceServletForAPI
- orderid – the Managed DNS/Web Hosting/Email Hosting/Live Chat/Website Builder Service Order Id that your Customer wants to manage
- username – the Username of the Customer, to whom the Order belongs
- password – the Password of the Customer, to whom the Order belongs
- resellerid – the Reseller Id associated with your Reseller account. This is obtainable from Settings -> Personal Information -> Primary Profile in your Reseller Control Panel.
- viewdns – the value of this parameter can be either true or false. If you do not pass any value for this parameter, then it is interpreted as false.Pass true – if the Order is Web Hosting or Mail Hosting and you want to allow your Customer to manage the DNS Records of that particular Order.
Pass false – if the Order is Web Hosting or Mail Hosting and you want your Customer to manage only the Web or Mail Hosting Order.
The disadvantage of using this method is that it is a bit less secure as the Customer Username and Password along with your Reseller Id can be viewed in the source of the page, from where you post to the ManageServiceServletForAPI servlet.
IMPORTANT
Do not send the above mentioned as parameters as part of a URL, or else this information will be displayed in your Customer’s Browser Address Bar.
Tags: Api, Browser Address Bar, Control Panel, Customer Class, DNS, Dns Hosting, Dns Records, Email Hosting, Hosting Website, http, Individual Control, Java, Live Chat, Login, Lt, Mail Hosting, Mail Order, Managed Hosting, Parameters, Period Of Time, Servers, Short Period, Url, Web Email, Web Hosting, Web Hosting/Email Hosting/Live, Web Hosting/Email Hosting/Live Chat/Website Builder Service Order Id, Web Mail
Follow the instructions below to begin integration with the API using PHP -
Make sure you have read the General API Integration Instructions first. If you have already integrated the PHP API Kit at your end, read the Change Log first to know what has changed since.
Reference:
General API Integration Instructions >>
Change Log >>
IMPORTANT
The PHP API Kit is not compatible with version PHP5. You need to use version PHP4 in order to integrate the API Kit at your end.
Step 1. Download the API Kit
Click the link below to download the relevant API kits (updated on 6th March, 2008).
PHP_CoreKIT_v3_10.zip
PHP_DomainsKIT_v3_10.zip
PHP_HostingKIT_v3_10.zip
PHP_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
IMPORTANT
Since “list” is a keyword in the PHP language, the “list()” methods in the various classes (in the PHP Kit) has been renamed to “listOrder().” However, the documentation still mentions the method name as “list” since the documentation is JAVA specific.
Instructions to pass parameters to functions using the PHP Kit
Since PHP 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 PHP.
|
Java Data
|
Types Assigning values in PHP
|
| String |
“firstname@secondname.com” |
| int |
123 |
| HashMap (Datatype for storing name-value pair) |
array(“domain.com”=>”1″) |
| Array and Vector (Datatype for storing more than one value) |
array(“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
public java.util.HashMap function2(java.util.HashMap domainHash, java.lang.String[] orderby, int[] resellerId)
and domainHash is accepting the domainname and the number of years as name value pair
$result = $obj->function2(array(“domain1.com”=>1,”domain2.com”=>2),array(“column1″,”column2″),array(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(array(“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
examples/ – Pre-written examples. You can directly run these examples to test API functionality
lib/ – The PHP class files, 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 PHP scripts. Make sure that both these folders are uploaded to the same parent folder.
2. You must have PHP 4 installed on the server
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 “constants.php” in the “examples” folder, by putting in the values for your “SERVICE_USERNAME”, “SERVICE_PASSWORD”, “SERVICE_PARENTID”. The remaining settings have already been made for you in this file. You may only need to change the path for the “lib” folder if you have uploaded the lib folder elsewhere
5. The URL to which the call is made is maintained in the “config.php” file inside the “lib” folder. By default all calls are made to the demo server URL using HTTP. You can make changes to this file and redirect your calls to the appropriate server
IMPORTANT
If you are using HTTPS calls you MUST have the extension for CURL installed and enabled in your PHP installation.
6. Another important parameter maintained in the “config.php” file is the variable $DEBUG. If this variable is set to “true”, then for each call you will see the entire XML Request and Response in the output. You should keep it to “true” during testing, but set it to false on the live environment.
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 .php file in the examples 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 PHP Class file as below
include($LIB_DIR.”Order.class.php”);
(ii) Obtain a pointer to the required Class. This is done by using the code below
$serviceObj = new Order($LIB_DIR . “wsdl/Order.wsdl”);
(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
$AssociativeArray = $serviceObj->setCustomerLock($SERVICE_USERNAME, $SERVICE_PASSWORD, $SERVICE_ROLE, $SERVICE_LANGPREF, $SERVICE_PARENTID, $orderId);
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
IMPORTANT
Remember, when passing numerical data in hashtables, please ensure that the number is passed as a String.
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. The URL that you make your calls to also needs to change to the LIVE Server URL. You will make this change in the “config.php” file in the “lib” folder
Once again note, if you are using the HTTPS URL you MUST have the extension for CURL installed and enabled in your PHP installation.
Tags: Api, Api Documentation, Api Guide, Api Kit, appropriate server, Datatype, Datatypes, Demo Server, Docs, Explanations, http, Integers, Integration Guide, Java, Java Data Types, Javadocs, Parameters, Php, Php Guide, PHP installation, Php Java, Php Kit, Php Language, Php4, Platforms, Reference, Step 1, Step 2, Variables, Web Server, Xml
Gossimer allows you the ability to completely change the look and feel of your SuperSite and PartnerSite through the use of Themes.
What is a Theme?
A Theme is a set of design elements and color schemes that you apply to pages to give them a consistent and attractive appearance. Using a Theme is a quick and easy way to add interest to pages and give them a professional look.
A Theme allows you to alter the appearance of your SuperSite/PartnerSite by modifying its:
- Cascading Style Sheets. By tweaking individual CSS files in your Theme you can modify the fonts, colors, spacing, etc., being displayed on your SuperSite/PartnerSite.
- Images. You can replace the default set of images within your SuperSite/PartnerSite Theme. This is especially useful when you have translated your SuperSite/PartnerSite content and would want to display images with embedded text in that language.
- Javascript. The style of the Javascript Menu within your SuperSite/PartnerSite Theme can be equally easily modified, to suit your customized SuperSite/PartnerSite.
By applying a Theme you can immediately apply a predetermined set of design elements to your SuperSite/PartnerSite content. When you choose one theme to be the default theme for your website, the theme is applied to all existing pages and to new pages that you add later.
How to Add/Modify a Theme or How do I edit the CSS, Images, Javascript of my SuperSite/PartnerSite?
IMPORTANT
- To modify the CSS, Images and Javascript of your SuperSite/PartnerSite, you need to first add a NEW Theme.
- While adding a Theme, you need to select the Default Theme from where you want the default CSS, Images and Javascript to be initially loaded. As you modify these elements, your changes become a part of your new Theme.
Adding a Theme
You can create your own Themes using the default Theme as mentioned below -
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
IMPORTANT
The Default SuperSite/PartnerSite Theme cannot be edited. If you wish to change the look and feel of your SuperSite/PartnerSite, you need to create your own Theme and modify the same.
- In order to create your own Theme, click on the Create Custom Theme link on the top right-hand corner of this page.
- Provide a unique name for your Theme and click Create My Theme. The Theme thus created will be listed under Your SuperSite/PartnerSite Theme(s) section.
- Click on the Browse link next to the Theme to view the contents of the Theme.
- Here you will find folders for CSS (Cascading Style Sheet) files, Images and JavaScript files.
Modifying your Theme (editing your SuperSite/PartnerSite CSS, Images, Javascript)
You can modify the CSS files (Cascading Style Sheets) for different sections of SuperSite and PartnerSite, by following the process outlined below:
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
- Click on Browse besides the Theme which you need to modify.
- Now click on Browse next to the CSS folder.
- This interface lists all the sections. Click on Browse, adjacent to the section for which you wish to modify the style sheets.
- The following page lists all the CSS files used in the section you have chosen. Click on Edit, adjacent to the CSS file you wish to modify.
- You will be presented with two textboxes; one on the left-hand side of the page with the title as Original Content and the other on the right-hand side with the title as My Modified Content. You can make the required modifications in the My Modified Content text box.
- Click on the Save Changes button beneath after completing the modification.
IMPORTANT
If you are not satisfied with the modifications and wish to revert to the earlier setting, simply click on Reset to Default from the Edit page, to restore the default settings for that file.
Virtually every image in SuperSite and PartnerSite is customizable – should you not find any to your liking, you can replace it with another at any time.
IMPORTANT
- In order to modify an image file in SuperSite or PartnerSite, you need to note its name. To get the name of the image, simply right-click on the image in your browser, and select Properties. Here, you would find the address for the image. For example, http://<prefix>.SuperSite/PartnerSite.myorderbox.com/getImage.php?src=image-name.gif, orhttp://<prefix>.partnersite.myorderbox.com/getImage.php?src=image-name.gif
where image-name.gif is the name that you require.
- Also, there are some image files which are a part of the CSS itself; you would not be able to retrieve the filenames in the above manner. To retrieve the names of such image files, you need to check the style sheets for the section containing the image in question, and retrieve the image file name from there. Click here to find instructions on how to edit your SuperSite/PartnerSite/PartnerSite CSS files >>
- : You can follow the process mentioned below to replace the default header logo with the logo of your company. To do so, you need to replace the image named yourbrand.gif.
Follow the process outlined below to modify any Image files in your SuperSite/PartnerSite:
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
- Click on Browse besides the Theme which you need to modify.
- Click on Browse link next to the Images folder.
- This interface lists all the images used by the SuperSite/PartnerSite.
- In the list, look for the name of the image you wish to modify. Click on Edit, adjacent to it.
- Click on Browse, and select the image you wish to upload in place of the default.
- Click on Upload Image. This will replace the default Image with the one you have provided, such that every page where the old image file was being displayed, would now display your uploaded image file.
In addition to the default images, you can add/edit your own images as mentioned below:
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
- Click on Browse besides the Theme which you need to modify.
- Click on Browse link next to the Images folder.
- Click on Browse next to the MyUploadedImages folder.
Adding your own Images
- Click on the Add your own Images button on the top right-hand corner of this page.
- Click on Browse, and choose the image that you want to upload.
- Once the image is selected, click on Upload button.
Editing Images added by you
- Click on the Edit link next to the image you wish to modify.
- Click on Browse, and choose the image that you want to upload.
- Once the image is selected, click on Upload Image button.
After uploading an image using the above tool, you would need to link it from some HTML page on your SuperSite/PartnerSite.
IMPORTANT
- If you have translated your SuperSite/PartnerSite content to multiple languages, then you may want to have images with text embedded on them in that particular language itself. To accomplish this you would need to associate different languages to separate Themes and within each Theme have Images related to only that language.
- If you are not satisfied with the modifications and wish to revert to the earlier setting, simply click on Reset to Default from the Edit page, to restore the default settings for that file.
The manner in which the menu is displayed, can be modified just as easily:
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin Area, click on the Add/Modify Content and Themes link. Then, click on Browse adjacent to the Themes folder.
- Click on Browse besides the Theme which you need to modify.
- Click on Browse next to the JS folder.
- Click on Edit, adjacent to the menu_style.js file.
- You will be presented with two textboxes; one on the left-hand side of the page with the title as Original Content and the other on the right-hand side with the title as My Modified Content. You can make the required modifications in the My Modified Content text box.
- Click on the Save Changes button beneath after completing the modification.
How do I apply a Theme to my SuperSite/PartnerSite?
You can display your SuperSite/PartnerSite in either the Default Theme provided by Gossimer or use any one of the Themes you have recently added. Follow the below mentioned process to accomplish this:
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- In the Admin Area, click on the Configure Languages and Themes link.
- Here you may either set your Theme for the Default English Language or any other language added by you, by selecting the Theme from the Associated Themes drop-down.
- Click on the Save button to associate the selected Theme to a particular language.
IMPORTANT
The Theme you have selected will be applied to your SuperSite/PartnerSite ONLY after you have enabled that particular language.
Click here to know how to configure Multiple Language support to your SuperSite/PartnerSite >>
Tags: above tool, Attractive Appearance, Cascading Style Sheets, Choose One, Color Schemes, Colors, Css Files, Css Images, Default Theme, Design Elements, Editing Images, Gif, Gossimer, HTML, http, Javascript Menu, Language Javascript, Partn, Supersite, Tweaking
Follow the below mentioned process to install the Nucleus Power Tool on your website:
1. Login to your Control Panel and search for the domain name for which you have purchased a Linux hosting package. Click here to know how >>
2. In the search results view, click on the domain name. This will take you to the Order details view.
3. Click on the Manage Web Hosting Service button in the lower toolbar.
4. Go to Manage Website -> Power Tools. This will present you with a list of Power Tools offered.
IMPORTANT
If you have already installed the Nucleus Power Tool, then instead of the Install link, the Uninstall link would be visible. You may view the details of the existing installation by clicking on the View link under the Details column.
5. In order to install Nucleus, click on Install link under the Status column.
6. In order to install the Nucleus Power Tool you would need to simply input the following details -
i. Database Name – select the database from the drop-down list.
ii. Database Username – select (one of) the Database User(s) whom you have associated with this database, from the drop-down list.
iii. Database User’s Password – provide the password of the Database User, you selected above.
iv. Directory Name – you need to input a new sub-directory name where you want the Nucleus Power Tool to be installed on your website. This sub-directory will be directly under your web directory. You need to provide the directory name without any trailing forward-slash (/).
IMPORTANT
Confirm that you have sufficient Web Space and Database Space before continuing the Nucleus installation, by referring the information provided in the interface.
Should you not have enough Web and/or Database Space, you would need to upgrade your package. Click here to read how to upgrade your package >>
7. Click on the Install button to complete the Nucleus installation.
Besides the above information, you need to provide a few details about the Nucleus Administrator:
1. Admin Name – This is the name of the person who will be administering the Nucleus installation.
2. Password – This is the Administrator’s Password.
3. Confirm Password – Re-enter the Administrator’s Password to confirm the same.
4. Admin Email – Mention the Administrator’s Email Address where important notifications will be sent by the Nucleus Power tool.
Once Nucleus is installed, you can click on the View link under the Details column, to view the details related to Nucleus.
IMPORTANT
URL of the Nucleus Image Gallery Management System: http://<yourdomainname>/<directoryname>/index.php
URL of the Nucleus Admin Control Panel: http://<yourdomainname>/<directoryname>/admin/index.php
Tags: administrator, Control Panel, Database Manager, Database Name, Database Tool, Database User, Details View, Domain Name, Driven Power, Drop Down List, Gt 2, Gt Power, http, Linux, Linux Hosting, Manage Web Hosting Service, Manager Interface, Nucleus, Nucleus Administrator, Nucleus installation, Php, Power Tool, Power Tools, Service Button, Status Column, sufficient Web Space, View 3, Web Directory, Web Hosting Service
Gossimer provides you with Partially Branded URLs for your SuperSite and PartnerSite. You can choose to direct visitors to your SuperSite to this URL. Alternatively, you can maintain complete anonymity from Gossimer, by setting up a fully branded URL.
IMPORTANT
The fully branded URL of your SuperSite can not be the same as that of your PartnerSite, or your Storefront. You must create different branded URLs for these interfaces, in order to have the SuperSite, PartnerSite as well as your Storefront functional at all times.
Follow the process mentioned below to set your branded URLs:
Partially Branded URLs
By default, you have a Partially Branded URL of the form – http://<prefix>.supersite.myorderbox.com. Now, you can select the prefix of your choice. Ideally it should be your Company Name or your Brand Name. You would then have to submit your selected prefix from your Control Panel. Follow the process outlined below to change the prefix:
- Login to your Reseller Control Panel from http://manage.gossimer.biz/reseller.
- In the Control Panel you need to go to Settings -> SuperSite and PartnerSite -> URL
- Scroll down to the Partially Branded URL Settings section. Here, you need to enter your selected prefix. On submitting the same, the prefix would be assigned to you, and would be common to all your partially branded URLs, i.e. SuperSite URL, PartnerSite URL, Control Panel URL, etc.In case this prefix is not available, you would have to select another.
IMPORTANT
- Even after your partially branded prefix is changed, the old prefix cannot be used by anyone else except you for a period of 30 days. After 30 days, however, the prefix would become available for anyone to utilize.
- If upon changing your prefix, you wish to revert to the same (within this 30 day period), you may do so by following the process outlined above.
Fully Branded URLs
Besides partially Branded URLs, you can point your own URLs to our servers and use those as your Fully Branded URLs. Gossimer allows you to have as many Fully Branded URLs as you wish; however, you would have to create the relevant DNS Record for each of the URL you select.
Setting up your Fully Branded SuperSite URL
This involves the following two steps -
-
Adding relevant DNS record If you have the partially Branded SuperSite URL in the form http://mybrandname.supersite.myorderbox.com and wish to set your fully Branded SuperSite URL as http://products.mybrandname.com, you need to create a CNAME record for products.mybrandname.com to point to partially Branded SuperSite URL mybrandname.supersite.myorderbox.com. The CNAME record would be products.mybrandname.com IN CNAME mybrandname.supersite.myorderbox.com Click here to read how to create a CNAME record >> However, if you wish to point mybrandname.com also to your SuperSite, the process would be slightly different. You need to buy Domain Forwarding for mybrandname.com and point it to products.mybrandname.com, with the URL Masking option enabled. Click here to read about Domain Forwarding service >> This is because if you create a CNAME record for mybrandname.com, you would not be able to use mybrandname.com for email purposes. In other words, it is not possible to have a CNAME record for mybrandname.com and at the same, use mybrandname.com for email purposes. If you wish to have your fully Branded SuperSite URL as http://mybrandname.com and would also like to create email addresses of the type example@mybrandname.com, you need to use the Domain Forwarding option instead of a CNAME record.
- Setting the URL within the Control Panel Follow the process outlined below to enter your fully Branded SuperSite URLs through the Control Panel -
- Login to your Reseller Control Panel from http://manage.gossimer.biz/reseller.
- In the Control Panel you need to go to Settings -> SuperSite and PartnerSite -> URL.
- Click on SuperSite URL.
- Here, you will be prompted to enter the fully Branded URL which you intend to use for your SuperSite.
- Next, you may specify any additional URLs you wish to point to your SuperSite. However, for each of these you would have to create a separate CNAME record pointing to Gossimer Servers as created for the Primary SuperSite URL.
- Click on Update.
Setting up your Fully Branded PartnerSite URL
This involves the following two steps -
- Adding relevant DNS record If you have the partially Branded URL in the form http://mybrandname.myorderbox.com and wish to set your fully Branded PartnerSite URL as http://some-name.mybrandname.com, you need to create an A record for some-name.mybrandname.com to point to 67.15.184.29. The A record would be -some-name.mybrandname.com IN A 67.15.184.29
IMPORTANT
67.15.184.29 is the actual IP address to which the A record for the fully Branded PartnerSite URL needs to be mapped.
Click here to read how to create an A record >>
- Setting the URL within the Control Panel Follow the process outlined below to enter your fully Branded PartnerSite URLs through the Control Panel -
- Login to your Reseller Control Panel from http://manage.gossimer.biz/reseller.
- In the Control Panel you need to go to Settings -> SuperSite and PartnerSite -> URL.
- Click on PartnerSite URL.
- Here, you will be prompted to enter the fully Branded URL which you intend to use for your PartnerSite.
- Next, you may specify any additional URLs you wish to point to your PartnerSite. However, for each of these you would have to create a separate A record pointing to Gossimer Servers as created for the Primary PartnerSite URL.
- Click on Update.
IMPORTANT
The SuperSite and PartnerSite contain information about your Partially/Fully Branded SuperSite and PartnerSite URLs. This data is downloaded to your SuperSite and PartnerSite from your Control Panel and stored on the SuperSite and PartnerSite Server respectively. Therefore, after making any change to the SuperSite or PartnerSite URLs, you would need to refresh cache of your SuperSite and PartnerSite. You can accomplish this from within your Control Panel itself by clicking on Tools -> Reload SuperSite & PartnerSite Cache -> SuperSite & PartnerSite Reseller Branding.
Tags: Anonymity, Biz, Brand Name, DNS, Domain Forwarding, Gossimer, http, Lt, Prefix, Reseller Control Panel, Servers, Storefront, Supersite, Tho, Urls
Integrating the WorldPay Credit Card Gateway with our system is pretty simple. You do not have to write ANY Code. You simply have to fill in a form specifying your preferences and account details.
Before you Start
You will need to gather the following details about your WorldPay Merchant Account before you start:
-
WorldPay Installation Id – Each WorldPay account user is assigned a unique Customer Account ID, along with one or more Installation IDs, for use in setting up and testing their integration with the WorldPay payment system. This Installation ID always needs to be included in each online transaction information sent to the WorldPay processing system. Installation IDs are unique numbers exclusive to your account and can not be changed.
-
Secret Word – This should be a string (spaces are permitted) of up to 16 characters. This secret must be sent to the WorldPay Technical Support Team at support@worldpay.com, so they can add it to the MD5 secret for transactions in the configuration settings of your installation.
-
Enable Callback – To redirect your Customers and Sub-Resellers back to their Control Panels after transacting through your WorldPay Payment Gateway, you would need to configure a few things in your WorldPay Merchant interface.
1. Login into your Production/Live WorldPay interface from https://support.worldpay.com/admin/
2. In the Installations for Your Company Name, search for your Installation ID and click on the Configuration options button.
3. On the following page, mention the following details and click on the SAVE CHANGES button -
a. Select the Callback enabled? and Use callback response? checkboxes
b. Mention the Callback URL as http://<Your Branded Storefront URL>/reseller/paymentgateway/generic/PostFormGateway.jsp?PGNAME=worldpay
Adding the WorldPay Credit Card Gateway into your Reseller account
1. Login into your Reseller Control Panel from http://manage.gossimer.biz/reseller
2. Click on Settings -> Finance & Billing -> Payment Gateway -> List / Add
3. Click on the Add Payment Gateway button and then on the Add an WorldPay Credit Card Gateway link.
4. Enter the following details and save your changes by clicking on the Submit button.
Gateway Name - This Gateway Name would be shown to your Customers/Sub-Resellers, when they are about to make Payment. You can use something like “Credit Card Payment” or “Visa/Master Card“, etc..
WorldPay Installation Id - Each WorldPay account user is assigned a unique Customer Account ID, along with one or more Installation IDs, for use in setting up and testing their integration with the WorldPay payment system. This Installation ID always needs to be included in each online transaction information sent to the WorldPay processing system. Installation IDs are unique numbers exclusive to your account and can not be changed.
Secret Word – This should be a string (spaces are permitted) of up to 16 characters. This secret must be sent to the WorldPay Technical Support Team at support@worldpay.com, so they can add it to the MD5 secret for transactions in the configuration settings of your installation.
Currency – Select the currency in which you want to charge your customers credit cards. Your Merchant Account needs to support the currency that is selected.
Currency Exchange Rate – If the Currency you selected in the previous option varies from your Selling Currency, we will have to convert the Invoice Value to the WorldPay Currency, BEFORE we send your Customer/Sub-Reseller’s Details to WorldPay. For this purpose the system needs an exchange rate between the two.
You may choose to maintain this exchange rate yourselves or let us maintain it for you. We download forex rates on a daily basis from a recognized source and update exchange rates for you. If however you wish to update the rates yourselves then you may do so by selecting the “I would like to Maintain the currency exchange rate myself” checkbox AND entering your own conversion rates.
Select the types of CREDIT CARDS that your merchant account supports - You need to select the types of Credit Card that are supported by your Bank. The credit card types available are – Visa, Master, Amex. You can also decide the sequence in which you want your Customers / Sub-Resellers to view these Card types on the payment page.
Payment Gateway Access Level for Customers and Sub-Resellers – Click here to know more about Payment Gateway Transaction types and Access Levels for your Customers and Sub-Resellers >>
Deciding whether a Sub-Reseller and Customer is Credited with the Gross Amount or Net – Your WorldPay deducts a fee on a per transaction basis. There are two types of Transactions that can pass through your WorldPay integration – Invoice/Debit Note Payment, and Add Funds. Click here to know more about Payment Gateway Transaction types and Access Levels for your Customers and Sub-Resellers >>
In case of an Add Funds Transaction, you have the option of crediting your Customers/Sub-Resellers with the NET Amount that WorldPay credits you with, or choose to credit them with the gross funds and bear the charges yourselves. The NET Amount is calculated by subtracting the per transaction charges from the Transaction Amount. The per transaction charges are calculated by adding the Total Fixed fee charged per transaction and the Total Variable fee charged per transaction.
Total Fixed fee charged per transaction for your merchant account (Per Transaction Fixed Fee charged by your Bank + Per Transaction Fixed Fee charged by the WorldPay Credit Card Gateway) - Enter the total fixed fee that is charged per transaction in the given textbox. This information is primarily used to calculate the Net Amount that your merchant account is credited with, if you choose to credit your customer / sub-reseller with the Net Amount in an Add funds Transaction. Your bank and/or your gateway may be charging you a different amount of fixed fee per transaction for different credit card types e.g. a certain fixed fee per transaction for Visa cards and a different fixed fee for American Express cards. In case, the amount of fixed fee is different per credit card type, then enter the highest amount of fixed fees charged per transaction to your account e.g. if the total fixed fee for Visa Cards is 25 cents per transaction and the total fixed fee for American Express cards is 30 cents per transaction, then enter 0.30 in the textbox. If there is no fixed fee charged per transaction then enter 0.
Total Variable fee charged per transaction for your merchant account - Enter the total variable fee that is charged per transaction in the given textbox. This information is primarily used to calculate the Net Amount that your merchant account is credited with, if you choose to credit your customer / sub-reseller with the Net Amount in an Add funds Transaction. Your bank and/or your gateway may be charging you a different amount of variable fee per transaction for different credit card types e.g. a certain variable fee per transaction for Visa cards and a different variable fee for American Express cards. In case, the amount of variable fee is different per credit card type, then enter the highest amount of variable fees charged per transaction to your account e.g. if the total variable fee for Visa Cards is 2.50% per transaction and the total variable fee for American Express cards is 3.00% per transaction, then enter 3.00 in the textbox. If there is no variable fee charged per transaction then enter 0.
IMPORTANT
If you have selected to credit a Customer/Sub-Reseller with the Net Amount in an Add Funds transaction, then you must submit either a Fixed Transaction fee (greater than 0) or a Variable Transaction fee (greater than 0).
Send me a Reminder if a transaction is pending for more than x days – In case you have not yet accepted a payment sent to you via the WorldPay Payment Gateway, you can get e-mail reminders sent across to you from our system, after every x number of days, until you either Approve or Decline these payments. Click here to know how to Approve / Decline Payment Gateway transactions >>
Display Position – If you plan on adding Multiple Gateways you can select the position in which you wish to display this Gateway on your Payment Page.
IMPORTANT
The SuperSite contains information about the various Payment options you offer to your Customers and also presents these options at the time of purchasing Products and Services. This data is downloaded to your SuperSite from your Control Panel and cached (stored) on the SuperSite Server. Hence, you would need to refresh the cache of your SuperSite once you have completed the above process. You can accomplish this from within your Control Panel itself by clicking on Tools -> Reload SuperSite & PartnerSite Cache -> SuperSite Payment Preferences. Click here to know what is SuperSite >>
Tags: Account Details, Account Id, American Express, bank, cent, Company Name Search, Configuration Options, Configuration Settings, Credit Card Gateway, Customer Account, http, Installation, Installation Id, Jsp, Merchant Account, Merchant Interface, online transaction information, Options Button, Payment Gateway, Processing System, Reseller Account, Reseller Control Panel, Resellers, Secret Word, Storefront, Worldpay Credit
To monitor your data transfer limit you can use the Web Statistics for your website, which Gossimer provides you free of cost. The web statistics, or webstats, provide you detailed information about visits to your website, including the data transfer generated by them (bandwidth). These statistics are generated once a day, and are maintained on an hourly, weekly and monthly basis.
You can view your web stats at http://<yourdomainname>/webstats.
Alternatively, you can monitor your data transfer overages through your Website management interface. To do so, follow the steps mentioned below:
1. Login to your Control Panel and search for the domain name for which you have purchased this hosting package.
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, you will see Usage statistics for your website, which also includes the data transfer (in Mb/month).
Tags: 3 Web, Bandwidth, Control Panel, Details View, Domain Name, http, Lt, Manage Web Hosting Service, Management Interface, Usage Statistics, View 3, Web Hosting Service, Web Service, Web Statistics, web stats, Website Management
When a user attempts to connect to a Web site and an HTTP error occurs, a generic message is sent back to the client browser with a brief description of what happened during the attempt to establish a connection. For example, if a user attempts to connect to a page that no longer exists on the Web site, an HTTP error will be returned in the form of an HTML page that contains the statement The requested URL was not found on this server.
You can use the Custom Error Pages view to customize HTTP errors that are sent to clients when Web server errors occur. Following is a list of HTTP errors you can customise:
401 – Authorization Failed
The request requires user authentication, typically a Username/Password credential pair. If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials.
403 - Permission Denied/Forbidden
You tried to access a URL for which you don’t have permission.
404 – File / Resource Not Found
Your browser cannot locate the document corresponding to the URL you entered. An improperly typed URL is usually the cause.
406 - Resource Not Acceptable
It’s possible you have requested a page that contains files which your browser has indicated to the server that it cannot accept, e.g. a multimedia file that your browser cannot process. Your browser sends information about what files it can accept to the server (in the HTTP header) as part of a request. You might check the preferences settings of your browser to see if there are file types it is not accepting.
500 – Internal Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
To customize the error messages, follow the procedure below:
1. Create your custom Error message and upload it to your website.
2. Login to your Control Panel and search for the domain name for which you have purchased this hosting package. Click here to read how >>
3. In the search results view, click on the domain name. This will take you to the order details view.
4. Click on Manage Web Hosting Service in the lower toolbar.
5. In the Website Management interface pop-up that follows,
go to Manage Website -> Custom Error Pages, if you have a Windows web hosting package
or
go to Manage Website -> Web Server Manager -> Custom Error Pages, if you have a Linux web hosting package
6. For the HTTP error that you wish to customize, you can
- select the radio button adjacent to Local URL, and enter the path to the file that you have uploaded, or
- select the radio button adjacent to Text/HTML Message, and fill in a suitable text/html message.
If for some reason you wish to disable custom error message for a particular error, select the radio button adjacent to Set To Default for that error.
7. Click on Submit to save the settings.
IMPORTANT
In order to complete the action in case of Linux Hosting, 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 changes might take upto 20 minutes to be effective.
Tags: HTML, http, Linux, Manage Web Hosting Service, Microsoft Windows, Web Hosting package, Web Server, Web server errors, Web Server Manager
In addition to the modifying the default HTML pages, you can as mentioned below:
- Login to your SuperSite or PartnerSite Admin Area. Click here to learn how >>
- Under the My Languages SuperSite/PartnerSite section, click on the Manage Site button besides the Language SuperSite/PartnerSite, where you wish to add/edit your HTML pages.
- Click on the Edit Content button. Then click on the Browse link besides the MyUploadedPages folder.
Adding your own HTML pages
- Click on the Add your own HTML page button on the top right-hand corner of this page.
- Here, enter a name for the file/page that you are adding, and add the HTML content of your page in the text-field provided.
- Once you have entered the content, click on Save Changes button. The page will be uploaded to your site, can now be viewed from http://<your supersite url>/content.php?action=mypages&page=<page name> or http://<your partnersite url>/content.php?action=mypages&page=<page name>, as appropriate.
- After uploading your own HTML page, you would need to link it from some existing HTML page on your SuperSite/PartnerSite using the Advanced HTML editing mode.
Editing HTML pages added by you
- Click on the Edit link next to the HTML page you wish to modify.
- Make changes to the original content of your file as desired.
- Click on Save Changes.
IMPORTANT
- An HTML page added by you will be specific to the Language SuperSite/PartnerSite under which it has been added.
- If you have multiple Language SuperSites/PartnerSites and wish to display your HTML page in each Language SuperSite/PartnerSite, you need to add the page (with language specific content) under each Language SuperSite/PartnerSite.
- If a specific HTML page added by you (in a particular Language SuperSite/PartnerSite) is no longer required, the same can be deleted by clicking the Delete button next to that HTML page in individual Language SuperSite/PartnerSite. Even if you have added your own page in multiple Language SuperSites/PartnerSites with the same file name, deleting the page under a particular Language SuperSite/PartnerSite will not affect the page in the other Language SuperSites/PartnerSites.
| Tags: Admin Area, Advanced Html, Amp, HTML, Html Button, Html Editing, Html Pages, http, Language Supersite, Languages, Lt, Page Button, Php, Url
FTP exists primarily for the transfer of data between two end points. FTP differs from HTTP (Hyper Text Transfer Protocol, used for serving websites via web browsers) fundamentally as it is an application made up of two distinct TCP connections:
1. Control connection: This TCP-based connection is used to provide a communications channel for the delivery of commands and replies. This is effectively the mechanism that enables the user to tell the server which file is being requested, which directory it is in, and so forth.
2. Data connection: The second TCP-based connection is used for the actual transfer of user data. Once the Control connection has been used to exchange information on which file is required, the Data connection is used to transfer the file between the client and server.
Using these two communication connections, two distinct modes of operation determine in which direction the connections are established: Active mode and Passive mode.
FTP is a TCP based service exclusively. There is no UDP (User Datagram Protocol transports data as a connectionless protocol, using packet switching) component to FTP. FTP is an unusual service in that it utilizes two ports, a Data port and a Command port (also known as the Control port). Traditionally these are port 21 for the Command (Control) port and port 20 for the Data port. The confusion begins however, when we find that depending on the mode, the data port is not always on port 20.
Active FTP
In active mode FTP the FTP client software connects from a random unprivileged (unprivileged port is a port which is higher than 1023) port. Let’s say N is the FTP server’s command port, port 21.
Then, the client starts listening to port N+1 and sends the FTP command PORT N+1 to the FTP server. The server will then connect back to the client’s specified data port from its local data port, which is port 20.
Here in this mode of FTP, Gossimer doesn’t need to open any additional non-secure ports on our servers firewall and hence is secure from the server-side.
Passive FTP
In passive mode FTP, the FTP client initiates both connections to the server. When opening an FTP connection, the client opens two random unprivileged ports, lets say N and N+1. The first port contacts the server on port 21, but instead of then issuing a PORT command and allowing the server to connect back to its data port, the client will issue the PASV command. The result of this is that the server then opens a random unprivileged port lets say P and sends the PORT command back to the client. The client then initiates the connection from port N+1 to port P on the server to transfer data.
This method of FTP is insecure, as a random unprivileged port is opened on the Server. This is a potential security issue and it isn’t advisable to use the Passive mode of FTP.
IMPORTANT
All Gossimer Windows and Linux web servers support both Active as well as Passive modes.
All popular FTP software allow users to select the data connection mode (Active or Passive), when uploading/downloading data to a web server.
Reference:
Click here to read how to set data connection mode in CuteFTP >>
Click here to read how to set data connection mode in 3D-FTP >>
Click here to read how to set data connection mode in CoreFTP >>
Click here to read how to set data connection mode in SmartFTP >>
Click here to read how to set data connection mode in WS_FTP >>
Tags: Client Software, Command port, Communication Connections, Communications Channel, Confusion, Connectionless Protocol, Control port, Data port, Distinct Modes, Firewall, Ftp Client Software, Ftp Command, Ftp Port, Ftp Server, Ftp Software, Gossimer, http, Hyper Text Transfer, Hyper Text Transfer Protocol, Linux, Microsoft Windows, Modes Of Operation, packet switching, Passive Mode Ftp, Ports, Tcp Connections, Text Transfer Protocol, Transports, UDP, User Datagram Protocol, Web Browsers, Web Server, Web Servers
A sub-domain is a subdivision of a Domain Name. While Domain Names need to be Registered with a Registrar, sub-domains are not and an unlimited number of sub-domains can be created through Managed DNS service. For example, a sub-domain news.yourdomain.com can be created on the Domain Name yourdomain.com.
Gossimer allows you to create unlimited sub-domains with your Linux Web Hosting package, by adding a Star (*) Address (DNS) Record for your Domain Name through the Managed DNS Order (that is included for free with your Web Hosting package). When a visitor reaches http://<sub-domain>.yourdomain.com, he is served the content from http://yourdomain.com/sub-domain/. Let’s discuss this with a few examples:
- If someone types http://news.yourdomain.com in the browser, then our web server will try to fetch the content from http://yourdomain.com/news/
So you need to ensure that you have created a folder called news within your website and have an index file (within this folder).
- If someone types http://news.yourdomain.com/php/ in the browser, then our web server will try to fetch the content from http://yourdomain.com/news/php/So you need to ensure that you have created a folder called news within your website and within that folder, a sub-folder called php with an index file (within php folder).
IMPORTANT
If someone typed http://news.yourdomain.com/php (without the trailing forward slash), he would receive a Page not found error.
- If someone types news.yourdomain.com/weather-report.jpg/i/index.html> in the browser, then our web server will try to fetch the content from yourdomain.com/news/weather-report.jpg/i/index.html> So you need to ensure that you have created a folder called news and have weather-report.jpg (within this folder).
IMPORTANT
1. If you are using our Managed DNS Service, then we have already created the appropriate Star Record to allow sub-domains on your Web Hosting package to begin working, once you modify your Name Servers to ours. Click here to find information about which Name Servers to use for activating your sub-domain hosting >>
If you are not planning to use our Managed DNS Service, then you need to add a Star Record to allow sub-domains on your Web Hosting package to begin working. Click here to find information about what DNS Records to add on your own Name Servers for activating your sub-domain hosting >>
2. If you have created an Alias for your Web Hosting package and want sub-domains of each alias to also point just like your hosted Domain Name, then you need to create a Star DNS Record for each aliased Domain Name, to point to your hosted Domain Name.
Example:
Suppose you have a Linux Web Hosting package for yourdomain.com and also a sub-domain news.yourdomain.com. Then say, you decide to set an alias for this package as yourotherdomain.com. To accomplish this, all you need to do is create an Address Record (DNS) for yourotherdomain.com to point to the IP Address of yourdomain.com.
yourotherdomain.com IN A 86400 1.1.1.1 (assuming that this is the IP Address of yourdomain.com)
But say you want news.yourotherdomain.com to function as well, then you would instead need to create a Star Address Record (DNS) for yourotherdomain.com
*.yourotherdomain.com IN A 86400 1.1.1.1 (assuming that this is the IP Address of yourdomain.com)
The Managed DNS Service for yourotherdomain.com could either be purchased through Gossimer or with your current DNS Service Provider.
Reference:
Click here to know what a Domain Alias is >>
Click here to know how to add Domain Aliases to your Web Hosting package >>
Click here to know the IP Address of your Web Hosting package where your Aliased Domain Name needs to point >>
3. If someone types http://php.news.yourdomain.com in the browser, then our web server will try to fetch the content from http://yourdomain.com/php.news/
If you want http://php.news.yourdomain.com to forward to http://yourdomain.com/news/php/, then you would need to add an alias for yourdomain.com as news.yourdomain.com (assuming that the Star Address Record for yourdomain.com exists).
Reference:
Click here to know what a Domain Alias is >>
Click here to know how to add Domain Aliases to your Web Hosting package >>
Tags: DNS, HTML, http, Linux, Managed DNS Service, Php, Registrar, the Star, Web Hosting package, Web Server
Using a PHP script you may accept feedback from your website visitors and get the results emailed to you. You can use the sample script provided by Gossimer and tweak it a bit to suit your requirements.
You would need to change the Email address in the field $from to any Email address on the domain name on which you are incorporating this script. For example, if your Domain Name is 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 $from field has to be yours. You may use an Email address such as Do_Not_reply@abc.com.
The value in the $mailto field needs to be changed to the Email address, where email containing the data submitted through the form needs to be delivered.
Once the visitor provides feedback, he/she can then be re-directed to another page on your website. In order to achieve this, you need to mention the path to the HTML file in the $file field in the script. 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.
Sample Script
<?
$mailto=”xyz@abc.com”;
$file=”thanks.htm”;
$pcount=0;
$gcount=0;
$subject = “Mail from Enquiry Form”;
$from=”some-name@abc.com“;
while (list($key,$val)=each($HTTP_POST_VARS))
{
$pstr = $pstr.”$key : $val n “;
++$pcount;
}
while (list($key,$val)=each($HTTP_GET_VARS))
{
$gstr = $gstr.”$key : $val n “;
++$gcount;
}
if ($pcount > $gcount)
{
$message_body=$pstr;
mail($mailto,$subject,$message_body,”From:”.$from);
include(“$file”);
}
else
{
$message_body=$gstr;
mail($mailto,$subject,$message_body,”From:”.$from);
include(“$file”);
}
?>
Tags: Abc, Domain Name, Feedback Script, Form Mail, Gossimer, HTML, http, List Key, Lt, Mail Feedback, Mail Form, Mail Script, Mail Server, Mailto Subject, Message Body, Path, Php, Php Form, Php Mail, Php Script, Script Php, Website Visitors, Xyz
Follow the below mentioned process to install the 4Images Power Tool on your website:
1. Login to your Control Panel and search for the domain name for which you have purchased a Linux hosting package. Click here to know how >>
2. In the search results view, click on the domain name. This will take you to the Order details view.
3. Click on the Manage Web Hosting Service button in the lower toolbar.
4. Go to Manage Website -> Power Tools. This will present you with a list of Power Tools offered.
IMPORTANT
If you have already installed the 4images Power Tool, then instead of the Install link, the Uninstall link would be visible. You may view the details of the existing installation by clicking on the View link under the Details column.
5. In order to install 4images, click on Install link under the Status column.
6. In order to install the 4images Power Tool you would need to simply input the following details -
i. Database Name – select the database from the drop-down list.
ii. Database Username – select (one of) the Database User(s) whom you have associated with this database, from the drop-down list.
iii. Database User’s Password – provide the password of the Database User, you selected above.
iv. Directory Name – you need to input a new sub-directory name where you want the 4images Power Tool to be installed on your website. This sub-directory will be directly under your web directory. You need to provide the directory name without any trailing forward-slash (/).
IMPORTANT
Confirm that you have sufficient Web Space and Database Space before continuing the 4images installation, by referring the information provided in the interface.
Should you not have enough Web and/or Database Space, you would need to upgrade your package. Click here to read how to upgrade your package >>
7. Click on the Install button to complete the 4images installation.
Besides the above information, you need to provide a few details about the 4images Administrator:
1. Admin Name – This is the name of the person who will be administering the 4images installation.
2. Password – This is the Administrator’s Password.
3. Confirm Password – Re-enter the Administrator’s Password to confirm the same.
4. Admin Email – Mention the Administrator’s Email Address where important notifications will be sent by the 4images Power tool.
Once 4Images is installed, you can click on the View link under the Details column, to view the details related to 4Images.
IMPORTANT
URL of the 4images Image Gallery Management System: http://<yourdomainname>/<directoryname>/index.php
URL of the 4Images Admin Control Panel: http://<yourdomainname>/<directoryname>/admin/index.php
Tags: 4images Administrator, administrator, Control Panel, Database Manager, Database Name, Database User, Details View, Domain Name, Driven Power, Drop Down List, Gt 2, Gt Power, http, Linux, Manage Web Hosting Service, Manager Interface, Php, Power Tool, Power Tools, Service Button, Status Column, sufficient Web Space, View 3, Web Directory, Web Hosting Service
Follow the below mentioned process to install the Joomla! Power Tool on your website:
1. Login to your Control Panel and search for the domain name for which you have purchased a Linux hosting package. Click here to know how >>
2. In the search results view, click on the domain name. This will take you to the Order details view.
3. Click on the Manage Web Hosting Service button in the lower toolbar.
4. Go to Manage Website -> Power Tools. This will present you with a list of Power Tools offered.
IMPORTANT
If you have already installed the Joomla! Power Tool, then instead of the Install link, the Uninstall link would be visible. You may view the details of the existing installation by clicking on the View link under the Details column.
5. In order to install Joomla!, click on Install link under the Status column.
6. In order to install the Joomla! Power Tool you would need to simply input the following details -
i. Database Name – select the database from the drop-down list.
ii. Database Username – select (one of) the Database User(s) whom you have associated with this database, from the drop-down list.
iii. Database User’s Password – provide the password of the Database User, you selected above.
iv. Directory Name – you need to input a new sub-directory name where you want the Joomla! Power Tool to be installed on your website. This sub-directory will be directly under your web directory. You need to provide the directory name without any trailing forward-slash (/).
IMPORTANT
Confirm that you have sufficient Web Space and Database Space before continuing the Joomla! installation, by referring the information provided in the interface.
Should you not have enough Web and/or Database Space, you would need to upgrade your package. Click here to read how to upgrade your package >>
7. Click on the Install button to complete the Joomla! installation.
Besides the above information, you need to provide a few details about the Joomla! Administrator:
1. Admin Name – This is the name of the person who will be administering the Joomla! installation.
2. Password – This is the Administrator’s Password.
3. Confirm Password – Re-enter the Administrator’s Password to confirm the same.
4. Admin Email – Mention the Administrator’s Email Address where important notifications will be sent by the Joomla! Power tool.
Once Joomla! is installed, you can click on the View link under the Details column, to view the details related to Joomla!.
IMPORTANT
URL of the Joomla! Content Management System: http://<yourdomainname>/<directoryname>/index.php
URL of the Joomla! Admin Control Panel: http://<yourdomainname>/<directoryname>/admin/index.php
Tags: administrator, Content Management System, Control Panel, Database Manager, Database Name, Database User, Details View, Domain Name, Driven Power, Drop Down List, Gt 2, Gt Power, http, Linux, Manage Web Hosting Service, Manager Interface, Php, Power Tool, Power Tools, Service Button, Status Column, sufficient Web Space, View 3, Web Directory, Web Hosting Service
Follow the process mentioned below to publish content for your website using Dreamweaver:
1. Open Dreamweaver. Click on Site and choose Manage Sites.

2. Click the New button and choose Site.

3. Under the Advanced Tab, fill in the Site name and HTTP Address (your domain name). Click the Remote Info category.

4. Set Access Type to FTP. The host is your domain name. Type web as the host directory. Also, type in your username and password and click OK at the bottom.

5. Click Done in the Manage Sites Window.

6. Now open your website and click Site and choose Put.

7. Dreamweaver will upload your files to the server.

Tags: Domain Name, Dreamweaver, Host Directory, http, New Button, Publishing Content, Type Web, Upload
Common API Examples
| Title: |
registerDomain method under DomOrder class of Domains kit |
| Description: |
The registerDomain method accepts complex variable/parameters whose usage cannot be easily illustrated using HTML forms. Hence, this feature cannot emulated from within your Reseller Control Panel through the Settings -> API -> Emulate API Calls -> Domains API Kit Emulator interface. |
| Solution: |
An example of XML sent and received for this method is provided below for reference. |
| Example XML: |
XML Sent:
<?xml version=”1.0″ encoding=”UTF-8″?>
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:SOAP-ENC=”http://schemas.xmlsoap.org/soap/encoding/” xmlns:si=”http://soapinterop.org/xsd” xmlns:impl=”com.logicboxes.foundation.sfnb.order.DomOrder” xmlns:apachesoap=”http://xml.apache.org/xml-soap”>
<SOAP-ENV:Body>
<impl:registerDomain>
<userName xsi:type=”xsd:string”>xxxxx@zzz.com</userName>
<password xsi:type=”xsd:string”>xxxxx4</password>
<role xsi:type=”xsd:string”>reseller</role>
<langpref xsi:type=”xsd:string”>en</langpref>
<parentid xsi:type=”xsd:int”>1</parentid>
<addParamList xsi:type=”apachesoap:Vector”>
<item xsi:type=”apachesoap:Map”>
<item>
<key xsi:type=”xsd:string”>domainhash</key>
<value xsi:type=”apachesoap:Map”>
<item>
<key xsi:type=”xsd:string”>apitest.com</key>
<value xsi:type=”xsd:int”>1</value>
</item>
</value>
</item>
<item>
<key xsi:type=”xsd:string”>contacthash</key>
<value xsi:type=”apachesoap:Map”>
<item>
<key xsi:type=”xsd:string”>registrantcontactid</key>
<value xsi:type=”xsd:int”>123456</value>
</item>
<item>
<key xsi:type=”xsd:string”>admincontactid</key>
<value xsi:type=”xsd:int”>123456</value>
</item>
<item>
<key xsi:type=”xsd:string”>technicalcontactid</key>
<value xsi:type=”xsd:int”>123456</value>
</item>
<item>
<key xsi:type=”xsd:string”>billingcontactid</key>
<value xsi:type=”xsd:int”>123456</value>
</item>
</value>
</item>
</item>
</addParamList>
<nameServersList xsi:type=”apachesoap:Vector”>
<item xsi:type=”xsd:string”>ns11.zzz.com</item>
<item xsi:type=”xsd:string”>ns12.zzz.com</item>
<item xsi:type=”xsd:string”>
</item>
<item xsi:type=”xsd:string”>
</item>
</nameServersList>
<customerId xsi:type=”xsd:int”>123456</customerId>
<invoiceOption xsi:type=”xsd:string”>OnlyAdd</invoiceOption>
<enablePrivacyProtection xsi:type=”xsd:boolean”>false</enablePrivacyProtection>
<validate xsi:type=”xsd:boolean”>true</validate>
<extraInfo xsi:type=”apachesoap:Map”>
</extraInfo>
</impl:registerDomain>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
XML Received:
<?xml version=”1.0″ encoding=”UTF-8″?>
<soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
<soapenv:Body>
<ns1:registerDomainResponse soapenv:encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” xmlns:ns1=”com.logicboxes.foundation.sfnb.order.DomOrder”>
<ns2:Map href=_quot;#id0_quot; xmlns:ns2=”http://xml.apache.org/xml-soap”/>
</ns1:registerDomainResponse>
<multiRef id=”id0″ soapenc:root=”0″ soapenv:encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” xsi:type=”ns3:Map” xmlns:soapenc=”http://schemas.xmlsoap.org/soap/encoding/” xmlns:ns3=”http://xml.apache.org/xml-soap”>
<item>
<key xsi:type=”xsd:string”>apitest.com</key>
<value href=_quot;#id1_quot;/_gt;
</item>
</multiRef>
<multiRef id=”id1″ soapenc:root=”0″ soapenv:encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” xsi:type=”ns4:Map” xmlns:ns4=”http://xml.apache.org/xml-soap” xmlns:soapenc=”http://schemas.xmlsoap.org/soap/encoding/”>
<item>
<key xsi:type=”xsd:string”>actiontypedesc</key>
<value xsi:type=_quot;xsd:string_quot;_gt;Registration of apitest.com for 1 years</value>
</item>
<item>
<key xsi:type=”xsd:string”>status</key>
<value xsi:type=”xsd:string”>Success</value>
</item>
<item>
<key xsi:type=”xsd:string”>entityid</key>
<value xsi:type=”xsd:string”>123456</value>
</item>
<item>
<key xsi:type=”xsd:string”>eaqid</key>
<value xsi:type=”xsd:string”>123456</value>
</item>
<item>
<key xsi:type=”xsd:string”>invoiceid</key>
<value xsi:type=”xsd:string”>123456</value>
</item>
<item>
<key xsi:type=”xsd:string”>actionstatus</key>
<value xsi:type=_quot;xsd:string_quot;_gt;PendingExecution_lt;/value_gt;
</item>
<item>
<key xsi:type=”xsd:string”>customercost</key>
<value xsi:type=”xsd:string”>00.00</value>
</item>
<item>
<key xsi:type=”xsd:string”>actiontype</key>
<value xsi:type=_quot;xsd:string_quot;_gt;AddNewDomain_lt;/value_gt;
</item>
<item>
<key xsi:type=”xsd:string”>description</key>
<value xsi:type=”xsd:string”>apitest.com</value>
</item>
<item>
<key xsi:type=”xsd:string”>actionstatusdesc</key>
<value xsi:type=_quot;xsd:string_quot;_gt;Order waiting to be executed.</value>
</item>
<item>
<key xsi:type=”xsd:string”>orderid</key>
<value xsi:type=”xsd:string”>123456</value>
</item>
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
|
Common API Errors and their Solution
| Title: |
Sending Integers as numbers rather than as strings |
| Description: |
Due to the limitations of Java, we cannot accept integers (e.g. 1) as numbers in a hash, rather they must be sent to us as strings (i.e. “1″). This is a recurrent problem when using the PHP Kit since PHP puts in Integers as plain numbers (in a hash). |
| Solution: |
Ensure that you’re sending in numbers as strings |
| Example XML: |
XML Sent:
POST /anacreon/servlet/rpcrouter HTTP/1.0 User-Agent: NuSOAP/0.6.7 (1.7) Host: www.myorderbox.com Content-Type: text/xml; charset=ISO-8859-1 SOAPAction: “” Content-Length: 1543
<?xml version=”1.0″ encoding=”ISO-8859-1″?><SOAP-ENV:Envelope SOAP-ENV:encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/” xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:SOAP-ENC=”http://schemas.xmlsoap.org/soap/encoding/” xmlns:si=”http://soapinterop.org/xsd” xmlns:impl=”com.logicboxes.foundation.sfnb.order.DomOrder” xmlns:apachesoap=”http://xml.apache.org/xml-soap”><SOAP-ENV:Body><impl:regis terDomain xmlns:impl=”com.logicboxes.foundation.sfnb.order.DomOrder”><userName xsi:type=”xsd:string”>xxxxx@zzz.com</userName><password xsi:type=”xsd:string”>xxxxx4</password><role xsi:type=”xsd:string”>reseller</role><langpref xsi:type=”xsd:string”>en</langpref><parentid xsi:type=”xsd:int”>1</parentid><domainHash xsi:type=”apachesoap:Map”><item><key xsi:type=”xsd:string”>fbc-elroy.com</key><value xsi:type=”xsd:int”>1</value></item></domainHash><ns xsi:type=”apachesoap:Vector”><item xsi:type=”xsd:string”>ns11.zzz.com</item><item xsi:type=”xsd:string”>ns12.zzz.com</item></ns><registrantContactId xsi:type=”xsd:int”>1548641</registrantContactId><adminContactId xsi:type=”xsd:int”>1548641</adminContactId><techContactId xsi:type=”xsd:int”>1548641</techContactId><billingContactId xsi:type=”xsd:int”>1548641</billingContactId><customerId xsi:type=”xsd:int”>321841</customerId><invoiceOption xsi:type=”xsd:string”>NoInvoice</invoiceOption></impl:registerDomain></SOAP- ENV:Body></SOAP-ENV:Envelope>
XML Received:
HTTP/1.0 500 Internal Server Error Server: Resin/3.0.s041002 Content-Type: text/xml; charset=utf-8 Date: Fri, 10 Jun 2005 16:40:04 GMT
<?xml version=”1.0″ encoding=”UTF-8″?> <soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”> <soapenv:Body> <soapenv:Fault> <faultcode>soapenv:Server.userException</faultcode> <faultstring>com.logicboxes.error.LogicBoxesException#~#com.logicboxes.util. Util#~#java.lang.Integer#~#error#~#</faultstring> <detail/> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope>
|
| Title: |
Incorrect Parent ID |
| Description: |
An incorrect parent id is passed when trying to connect to the server |
| Solution: |
Pass the correct parent id. You might be passing the one for demo while connecting to the live environment, or vice-versa. |
| Example XML: |
Error Received:
Error Code: 2, SOAP raised an error.
Error Details:
com.logicboxes.error.AuthenticationException#~#com.logicboxes.foundation.sfnb.Authentication#~#You are not allowed to perform this action#~#warn#~#
|
| Title: |
Maximum Number of Connections to the Registry Exceeded |
| Description: |
When too many users send commands to the same Registry using a particular Registrar’s connections, then an error would be displayed |
| Solution: |
This is a temporary issue and you need to simply try after sometime. Since the Registry provides each Registrar with a set number of connections, when these get exhausted an exception is thrown. |
| Example XML: |
Error Received:
01-jul-2005 16:43:31 org.apache.axis.client.Call invoke
INFO: Mapping Exception to AxisFault
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultString:
com.logicboxes.rtk.RegistryException#~#com.logicboxes.rtk.AbstractFactory#~#Object Not Available for registrar_domorgrrp Pool#~#error#~#
faultActor: null
faultDetail:
stackTrace: AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultString:
com.logicboxes.rtk.RegistryException#~#com.logicboxes.rtk.AbstractFactory#~#Object Not Available for registrar_domorgrrp Pool#~#error#~#
faultActor: null
faultDetail:
|
| Title: |
Error received when making https calls using the .NET API Kit |
| Description: |
You may receive an error when trying to make an https call using our .NET API Kit since your .NET API Client needs to set a system security property to allow the system to accept SSL certificates. |
| Solution: |
You need to add a class in your project (or the .NET Examples that we provide) having the following lines of code:
Imports System.Security.Cryptography.X509CertificatesPublic Class TrustAllCertificatePolicy
Implements System.Net.ICertificatePolicy
Public Sub New()
End Sub
Public Function CheckValidationResult(ByVal srvPoint As System.Net.ServicePoint, ByVal certificate As System.Security.Cryptography.X509Certificates.X509Certificate, ByVal request As System.Net.WebRequest, ByVal certificateProblem As Integer) As Boolean Implements System.Net.ICertificatePolicy.CheckValidationResult
Return True
End Function
End Class
The code will allow the system to accept all kinds of certificates whatsoever. If you want the system to accept only a specific certificate, then you need to modify the code of the function “CheckValidationResult” above accordingly.
Also the user needs to include the following line of code before making the any function call to the https URL:
System.Net.ServicePointManager.CertificatePolicy = New TrustAllCertificatePolicy
We would suggest that you include the above line in the NetAPI.vb class constructor.
After performing all the above steps, you would be able to make the https calls using the .NET API Kit without any error.
|
| Example XML: |
Error Received
System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. —> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
|
Tags: Api, Api Calls, Api Examples, C Ommon, CheckValidationResult(ByVal srvPoint As System.Net.ServicePoint ByVal certificate As System.Security.Cryptography.X509Certificates.X509Certificate ByVal request As System.Net.WebRequest ByVal certific, Class TrustAllCertificatePolicy Implements System.Net., Cryptography, HTML, Html Forms, http, Impl, Interface Solution, Java, Kit Description, Lt Xml, Parent, particular Registrar, Php, Reference Example, Registerdomain, Registrar, Reseller Control Panel, Schemas, Sfnb, SSL, System.Net., Utf 8, Variable Parameters, Vector, www.myorderbox.com, Xml, Xml Soap, Xsi, Xxxxx, Zzz