Web Development – Creative Website Designs http://www.creativewebsitedesigns.com.au Creative for your online success! Wed, 03 Jan 2018 02:48:28 +0000 en-US hourly 1 https://wordpress.org/?v=4.9.1 http://www.creativewebsitedesigns.com.au/wp-content/uploads/2015/05/logo.jpg Web Development – Creative Website Designs http://www.creativewebsitedesigns.com.au 32 32 Frontend Code Standards and Best Practice http://www.creativewebsitedesigns.com.au/frontend-code-standards-best-practice/ Tue, 19 Apr 2016 02:23:16 +0000 http://www.creativewebsitedesigns.com.au/?p=3220 This post primary motivation is two- fold:

  1. code consistency and using best practices.

Markup

 Frontend Code Standards and Best PracticeThe starting blocks of any website is HTML. There was some discussions around XHTML, but industry has accepted that HTML is the future of the web.

Markup defines the structure and outline of a document and offers a structured content. Markup is not intended to define the look and feel of the content on the page beyond rudimentary concepts such as headers, paragraphs, and lists. The presentation attributes of HTML have all been deprecated and style should be contained in style sheets.

HTML5

HTML5 is a new version of HTML and XHTML. The HTML5 draft specification defines a single language that can be written in HTML and XML. It attempts to solve issues found in previous iterations of HTML and addresses the needs of web applications, an area previously not adequately covered by HTML. (source).

We will use the HTML5 Doctype and HTML5 features when appropriate.

We will test our markup against the W3C validator, to ensure that the markup is well formed. 100% valid code is not a goal, but validation certainly helps to write more maintainable sites as well as debugging code. Isobar does not guarantee code is 100% valid, but instead assures the cross-browser experience is fairly consistent.

Doctype

A proper Doctype which triggers standards mode in your browser should always be used. Quirks mode should always be avoided.

A nice aspect of HTML5 is that it streamlines the amount of code that is required 5mg cialis online. Meaningless attributes have been dropped, and the DOCTYPE declaration has been simplified significantly. Additionally, there is no need to use CDATA to escape inline JavaScript, formerly a requirement to meet XML strictness in XHTML.

Character Encoding

All markup should be delivered as UTF-8, as its the most friendly for internationalization. It should be designated in both the HTTP header and the head of the document.

Setting the character set using <meta> tags.

General Markup Guidelines

The following are general guidelines for structuring your HTML markup. Authors are reminded to always use markup which represents the semantics of the content in the document being created.

  • Use actual P elements for paragraph delimiters as opposed to multiple BR tags.
  • Make use of DL (definition lists) and BLOCKQUOTE, when appropriate.
  • Items in list form should always be housed in a UL, OL, or DL, never a set of DIVs or Ps.
  • Use label fields to label each form field, the for attribute should associate itself with the input field, so users can click the labels. cursor:pointer; on the label is wise, as well. note 1 note 2
  • Do not use the size attribute on your input fields. The size attribute is relative to the font-size of the text inside the input. Instead use css width.
  • Place an html comment on some closing div tags to indicate what element you’re closing. It will help when there is lots of nesting and indentation.
  • Tables shouldn’t be used for page layout.
  • Use microformats and/or Microdata where appropriate, specifically hCard and adr.
  • Make use of THEAD, TBODY, and TH tags (and Scope attribute) when appropriate.
  • Always use title-case for headers and titles. Do not use all caps or all lowercase titles in markup, instead apply the CSS property text-transform:uppercase/lowercase.

Quoting Attributes

The HTML5 specification defines quotes around attributes as optional. For consistency with attributes that accept whitespace, all attributes should be quoted.

]]>
Installing SharePoint Application and Site Templates http://www.creativewebsitedesigns.com.au/installing-sharepoint-application-site-templates/ Tue, 05 Apr 2016 03:31:22 +0000 http://www.creativewebsitedesigns.com.au/?p=3215 Uploading .stp Site Templates
  1. Download the site template EXE file to your computer.
  2. Run the EXE file to unpack the template file to a location on your computer.
  3. Select the template file, <template_name>.stp, from the extracted distribution for the application template you wish to install.
  4. Log into your SharePoint site as the site Administrator.
  5. From the Site Actions drop-down menu in the top right, select Site Settings.
  6. Under the Galleries section, select Site templates.
  7. Select Upload to load an application template into this SharePoint site.
  8. Browse to the <template_name>.stp file from the distribution and select Open. If you have several application templates to load into your site, you can use the Upload Multiple Files… option to load them all at once.
  9. Click Ok to complete the upload of the application template to your SharePoint site.

Applying the new Site Template:

  1. Log into your SharePoint site as the site Administrator.
  2. From the Site Actions drop-down menu in the top right, select Site Settings.
  3. Under the Site Administration section, select Sites and Workspaces.
  4. Select Create to create a new site using a site template.
  5. Complete the new SharePoint site information. In the Template Selection section, select the Custom tab. Any application templates that have been uploaded will be listed here.
  6. Select the template to use for this site and click Create.
  7. A site has now been created using the application template.

Uploading .wsp Site Templates

To install the Application Template Core solution:

To deploy the Application Template Core solution on a server running Windows SharePoint Services, follow these instructions.

Note: To complete the following installation, you must have Administrator rights to both the Windows SharePoint Services site and server on which it is to be installed.

  1. Download the solution EXE file to your computer.
  2. Run the EXE file to unpack the template file to a location on your computer.
  3. Select the solution file, ApplicationTemplateCore.wsp, from the extracted distribution. This solution file will be added to the Windows SharePoint Services solution store.
  4. Via command line, run
    stsadm –o addsolution –filename ApplicationTemplateCore.wsp
  5. Next, run
    stsadm –o deploysolution –name ApplicationTemplateCore.wsp -allowgacdeployment
    Additional attributes may be required based on your Windows SharePoint Services configuration.
  6. Finally, run
    stsadm -o copyappbincontent
  7. The Application Template Core solution has now been added to the solution store, and deployed on the server.

To install an Application Template:

This server admin template is deployed in the Windows SharePoint Services environment as a solution. To deploy a solution on a server running Windows SharePoint Services, follow these instructions.

Note: To complete the following installation, you must have Administrator rights to both the Windows SharePoint Services site and server on which it is to be installed.

  1. Before installing any Application Template, you must first install the Application Template Core solution, ApplicationTemplateCore.wsp. If you have already installed this solution, proceed to Step 2.Otherwise, browse to the following URL to download the Application Template Core solution.
    http://go.microsoft.com/?LinkId=5922037
  1. Download the application template solution EXE file to your computer.
  2. Run the EXE file to unpack the template file to a location on your computer.
  3. Select the solution file, <template_name>.wsp, from the extracted distribution. This solution file will be added to the Windows SharePoint Services solution store.
  4. Via command line, run
    stsadm –o addsolution –filename <template_name>.wsp
  5. Next, run
    stsadm –o deploysolution –name <template_name>.wsp -allowgacdeployment
    Additional attributes may be required based on your Windows SharePoint Services configuration.
  6. The Application Template solution has now been added to the solution store, and deployed on the server.

Instructions for use:

  1. Log into your SharePoint site as the site Administrator.
  2. From the Site Actions drop-down menu in the top right, select Site Settings.
  3. Under the Site Administration section, select Sites and Workspaces.
  4. Select Create to create a new site using a site template.
  5. Complete the new SharePoint site information. In the Template Selection section, select the Application Templates tab. All deployed Application Template will be listed in this tab.
  6. Select the template to use for this site and click Create.
  7. A site has now been created using the application template.

To remove an Application Template solution:

This server admin template is deployed in the Windows SharePoint Services environment as a solution. To remove
a solution on a server running Windows SharePoint Services, follow these instructions.

Note: To complete the following installation, you must have Administrator rights to both the Windows SharePoint Services site and server on which it is to be installed.

  1. As Administrator, access the server. Removal is done via the command line utility stsadm.
  2. To retract a solution from being available to SharePoint sites, run
    stsadm –o retractsolution –name <template_name>.wsp
    Additional attributes may be required based on your Windows SharePoint Services configuration.
    Note: sites created from a solution will not function after the solution has been retracted.
  3. To delete a solution from the Windows SharePoint Services solution store, run
    stsadm –o deletesolution –name <template_name>
    Additional attributes may be required based on your Windows SharePoint Services configuration.
  4. The Application Template solution has been retracted and deleted from the solution store.
]]>
OpenText Management Server Useful Tips http://www.creativewebsitedesigns.com.au/opentext-management-server-useful-tips/ Mon, 11 Jan 2016 04:33:43 +0000 http://www.creativewebsitedesigns.com.au/?p=3203 Delivery Server Application Restart Procedure

The following steps can be followed when wanting to restart the OpenText Delivery Server Services
1. Logon to the associated server
2. Open Services interface
3. Find the service Verity K2 6.1 Administration Server and stop it
4. Find the service Apache Tomcat DeliveryServer and restart this service
5. Go back and restart Verity K2 6.1 Administration Server
6. After a couple minutes the Delivery Server should be fully functional again*

Note: For a full reboot nothing needs to be done as all items run as services*

Management Server Application Restart Procedure

For the Management Server (CMS) best to restart the whole server as there are several services involved in the CMS the list of services are:
• RedDot Data Service
• RedDot Object Service
• RedDot PageBuilder Service
• RedDot ProcessServer Service
• RedDot RQL Service
• RedDot WebClient Service

Note: In the event of a major outage ensure that the database servers are started first as the OpenText application and CMS servers all use the database for configuration and information.

Clearing of Cache in Delivery Server

This should only be done as directed by Developer or Web support.

  1. Login to the Delivery Server Web Interface
  2. Click Administer Delivery Server
  3. Expand Monitoring the expand Cache
  4. Click Show Component Cache
  5. Click clear all caches and then click back

Troubleshooting Web Site Running Slow

If the website is running extremely slow and often timing out (not responding/loading): Check CPU on server if this is peaking then possible causes are:

1a. Verity search engine has locked up.
a. Try restarting the Verity Service (won’t effect site except for search results while restarting)
b. If this fails then Restart the Apache Service (will kill current sessions and not allow access until loads the service up)

2b. If CPU not peaking then check if Apache Tomcat Service is running

  • If not then restart
  • if it is then access the admin interface and login as administrator, if this doesn’t load then restart the Apache service
  • If this loads then check the project locks and/or active sessions
  • If nothing strange then copy logs and restart Apache tomcat service, then raise an issue with OpenText and send them the logs.

User unable to login

1a. Check if locked in database table (there is an automated account unlock process in production that cleans this up after 15 minutes)

2b. If no data returned check if it exists and is locked in Delivery Server
a. Log on to Delivery Server web interface with Administration rights
b. Click Administer Delivery Server
c. Expand Users
d. Click Find
e. Enter the username and click Ok
f. If the user exists will appear in the list click the username (if not here then not currently registered for new site)
g. Check the current status
h. If Inactive or Locked then set to active and then click Ok (user should be able to login now)

]]>
Website Performance Testing http://www.creativewebsitedesigns.com.au/website-performance-testing/ Tue, 05 Jan 2016 04:37:14 +0000 http://www.creativewebsitedesigns.com.au/?p=3201 Purpose

The purpose of performance testing is to reduce risks to system performance and its impact on the Business.

For example, some common question performance testing can answer are:

  • Can the system process the expected number of transactions and load?
  • At the expected levels of load (average & peak) are the response times acceptable?
  • Is the system reliable?
  • What is the capacity of the system and has the capacity been correctly specified?
  • Will the system grind to a halt after the 10th user logs on and die 30 minutes after Go Live?

How is Performance different then Functional Testing?

Performance testing differs from functional testing in that it is focused on generating load on the back end of the system under test, and is not concerned with testing the functionality of the system beyond what is required to generate that load.

  • Often no Pass/Fail criteria, involves repeated testing and tuning
  • Requires a Production-like Test Environment
  • Requires a Large and Stable Production-like Test Data Set
  • Monitoring of Infrastructure and access to Various Domain Experts within an organization
  • Requires Functional Stability of Application

Business Goals and Risk

  • Performance test are designed and structured to mitigate a Business Risk
  • Usually one Performance Test type mitigates one Business Risk
  • Businesses have unique Business Risks that must be clearly defined so that Performance Test Scenarios can be constructed accordingly
  • Example: “We losing business when the system grinds to a halt after the 10th user logs on”

Business Process Transaction Mix

  • It is usually not cost effective to try and cover all of the functionality in a performance test
  • Performance Testing is not about code coverage, rather the aim is about application and infrastructure readiness for Business use.

Transaction Rates

  • To conduct an accurate load simulation, the number of transactions performed per hour must be determined for each Business Process
  • These are either Production figures (best), or Estimates of the expected load (next best)
  • These figures are used to select which transactions should be scripted, and to configure the resulting Performance Tests
  • At a minimum both Average and Peak (busiest hour) values are required

Performance testing Tools and script development

When a GUI based client application (thick client) or Web base application is running on a PC, typically only a single user can use that PC at a time. However, a performance testing tool must simulate hundreds or thousands of end-users, a different approach must be taken.

Performance test scripts are usually “recorded” using the application under test. During recording, the communication protocol between the client and the server is captured. Therefore, during playback the client application is not used. The script simulates the client by communicating directly with the system under test. With no client application running, many “Virtual Users” can be executed on the same PC, thus generating load with minimal hardware.

Results

  • After each test, the results can be analysed to try and identify where problems are occurring, and to extract Transaction Response Times, and server statistics for inclusion in the Test Report.
  • After the test it is common for some system remediation to take place to correct problems discovered.
  • The test cycle is then repeated to verify that problem or bottleneck has been removed.
]]>