GOVARDHAN GUNNALA

"C:Program FilesMySQLMySQL Server 5.1binMySQLInstanceConfig.exe"

Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!

http://wordpress.org/about/requirements/

To run WordPress your host just needs a couple of things:

• PHP version 5.2.4 or greater
• MySQL version 5.0 or greater

The requirements have changed as of WordPress 3.2. The minimum requirements for WordPress 3.1 are PHP 4.3 and MySQL 4.1.2.

 

 

Installing Plugin: Jetpack by WordPress.com 2.9.3

Downloading install package from http://downloads.wordpress.org/plugin/jetpack.2.9.3.zip…

( ! ) Fatal error: Maximum execution time of 30 seconds exceeded in C:wampwwwWPTestwordpresswp-includesclass-http.php on line 973
Call Stack
#	Time	Memory	Function	Location
1	0.0019	352832	{main}( )	..update.php:0
2	1.6259	21625904	Plugin_Upgrader->install( )	..update.php:120
3	1.6261	21635128	WP_Upgrader->run( )	..class-wp-upgrader.php:498
4	1.6316	21850400	WP_Upgrader->download_package( )	..class-wp-upgrader.php:375
5	1.6328	21834272	download_url( )	..class-wp-upgrader.php:133
6	1.6349	21835712	wp_safe_remote_get( )	..file.php:497
7	1.6349	21836432	WP_Http->get( )	..http.php:70
8	1.6349	21837520	WP_Http->request( )	..class-http.php:396
9	1.6422	21844912	WP_Http->_dispatch_request( )	..class-http.php:249
10	1.6422	21844992	WP_Http_Streams->request( )	..class-http.php:333
11	2.6442	21856936	WP_Http::handle_redirects( )	..class-http.php:1035
12	2.6442	21859344	wp_remote_request( )	..class-http.php:735
13	2.6442	21859432	WP_Http->request( )	..http.php:163
14	2.6476	21868336	WP_Http->_dispatch_request( )	..class-http.php:249
15	2.6476	21868416	WP_Http_Streams->request( )	..class-http.php:333

 

 

Try Again:

Installing Plugin: Jetpack by WordPress.com 2.9.3

Downloading install package from http://downloads.wordpress.org/plugin/jetpack.2.9.3.zip…

Unpacking the package…

Installing the plugin…

Successfully installed the plugin Jetpack by WordPress.com 2.9.3.

Activate Plugin | Return to Plugin Installer

A description of the Web Proxy Auto Detect (WPAD) feature

The WPAD feature lets services locate an available proxy server by querying a DHCP option or by locating a particular DNS record. For more information about the advantages and disadvantages of using DNS instead of DHCP for WPAD, click the following article number to view the article in the Microsoft Knowledge Base:

816320 How to configure firewall and Web proxy client Autodiscovery in Windows Server 2003

 

The WPAD protocol works as follows:

1. Using the DHCP and/or DNS network protocols, the URL of a Proxy Auto-Configuration (PAC) file is discovered. The URL identifies a PAC file on the client’s local network. WinHTTP supports only "http:" and "https:" PAC URLs; it does not, for example, support "file:" URLS.
2. The PAC file is downloaded and optionally cached on the client’s computer. The PAC file is an executable script that generates a list of one or more proxy servers given a target host name and URL. WinHTTP supports only ECMAScript-based PAC files.
3. On each HTTP request, the PAC script code is executed, with the host name and URL of the HTTP request passed in as parameters. WinHTTP expects the PAC script code to contain a function called FindProxyForURL, in the form:

4. FindProxyForURL( url, host );

   This function computes a list of one or more proxy servers that can be used by the HTTP client in order to transmit the request. If the PAC script determines that the HTTP client can reach the target server directly without going through a proxy server at all, it indicates this using a special return value.

This is being employed in Windows Automatic Updates:

The Automatic Updates service is configured to download and install updates from the Microsoft Windows Update Web site

The Automatic Updates service can automatically download and install updates from the Windows Update Web site. The Automatic Updates service does not require user interaction because this service runs in the context of the Local System account. The Automatic Updates service does not have access to the user-specific proxy server settings that may be configured in Internet Explorer. WinHTTP has been employed, instead of WinInet in Internet Explorer, as the Automatic Updates service affects system wide level configuration and should require administrator level control. WinHTTP is considered as more appropriate in this type of usage scenario. The Automatic Updates service can only discover a proxy server by using one of the following methods:

• The proxy server is manually configured by using the Proxycfg.exe tool for Windows XP and Windows Server 2003. For Windows Vista and newer OS, Netsh command is available to manually configure the proxy server.  For more information about how to use the Proxycfg.exe tool, click the following article number to view the article in the Microsoft Knowledge Base:

  289481 You may need to run the Proxycfg tool for ServerXMLHTTP to work

• Web Proxy Auto Detect (WPAD) settings are configured in either of the following locations in the network environment:
  • The Domain Name System (DNS) options
  • The Dynamic Host Configuration Protocol (DHCP) options

  For more information about a related topic, click the following article number to view the article in the Microsoft Knowledge Base:

  816320 How to configure firewall and Web proxy client Autodiscovery in Windows Server 2003

References:

How the Windows Update client determines which proxy server to use to connect to the Windows Update Web site

How to change LAN Settings (proxy configuration) programmatically

If you look at the XenApp and XenDesktop deployments to date, you will notice that most of the users’ requirements fit into one of the following buckets:

· User requires access to a line of business application

· User requires access to a standardized desktop environment

· User requires access to a personalized desktop environment

· A combination of the above

Another thing you will notice with these 4 buckets is that “Users” “Access” a “Resource”, whether that resource is an app or a desktop or a combination. This is how you should start to think about your own XenApp and XenDesktop solution… What does your user need access to? This simple question is the basis for the XenApp and XenDesktop 7.5 blueprint.

The blueprint is based on the Citrix 5-layer model.

The top 3 layers are unique for each user group. There might be similarities between user groups, but the important aspect is that you walk through those three layers (users, access and resources) for each user group. Once those are defined, you design a single control layer running on your hardware platform for the entire solution.

The XenApp and XenDesktop 7.5 blueprint follows this model and defines each layer based on the most common design scenarios.

To get started, we begin with a standard conceptual architecture diagram for XenApp 7.5 and XenDesktop 7.5.

We continue the blueprint by:

1. Identifying the most common type of user groups and recommended resource

2. Defining authentication and security policies to gain access to the resources

3. Detailing the image, application and personalization settings for each resource catalog

4. Allocating the right number of control systems to support the overall solution

5. Determining how much hardware (CPU, RAM and storage) we will need in order to build the environment.

So grab a drink, sit down, get comfortable and grab the following blueprints

· XenApp 7.5 Blueprint

· XenDesktop 7.5 Blueprint

 

Source: XenApp 7.5 and XenDesktop 7.5 Blueprints Now Available

 

Login to the WordPress site as Administrator, Navigate to Appearance > Themes > Click “Add New”

Evaluate and decide on a Theme you’d like to have installed.

Press “Install”, to install a chosen Theme

Installing Theme: Suffusion 4.4.7

Downloading install package from http://wordpress.org/themes/download/suffusion.4.4.7.zip…

Unpacking the package…

Installing the theme…

Successfully installed the theme Suffusion 4.4.7.

Live Preview | Activate | Return to Theme Installer

Now, goto Themes and there you’ll find the new theme listed for you to have activated on the blog.

WordPress Updates

Last checked on April 18, 2014 at 3:52 am.   Check Again

Important: before updating, please back up your database and files. For help with updates, visit the Updating WordPress Codex page.

An updated version of WordPress is available.

• You can update to WordPress 3.9 automatically or download the package and install it manually:

  Download 3.9

While your site is being updated, it will be in maintenance mode. As soon as your updates are complete, your site will return to normal.

Plugins

Your plugins are all up to date.

Themes

Your themes are all up to date.

 

Click “Update Now”

 

Update WordPress

Downloading update from http://downloads.wordpress.org/release/wordpress-3.9.zip…

Unpacking the update…

Verifying the unpacked files…

Preparing to install the latest version…

Enabling Maintenance mode…

Copying the required files…

Disabling Maintenance mode…

Upgrading database…

 

 

Update Plugin

Downloading update from http://downloads.wordpress.org/plugin/akismet.3.0.0.zip…

Unpacking the update…

Installing the latest version…

Removing the old version of the plugin…

Plugin updated successfully.

Installing Plugin from uploaded file: jetpack.2.9.3.zip

Unpacking the package…

Installing the plugin…

Plugin installed successfully.

Activate Plugin | Return to Plugins page

Create Instance

Amazon Relational Database Service (RDS) makes it easy to set up, operate, and scale a relational database in the cloud. You can click the button below to launch a Database (DB) Instance in minutes with automated backups, turnkey Multi-AZ replication and free monitoring metrics. Amazon RDS gives you access to a familiar MySQL, PostgreSQL, Oracle, or SQL Server database to facilitate compatibility with existing code, applications, and tools.

Launch a DB Instance

Engine Selection

---

To get started, choose the DB Instance details below and click Select

	mysql MySQL Community Edition	Select
	postgres PostgreSQL	Select

	oracle-se1 Oracle Database Standard Edition One	Select
	oracle-se Oracle Database Standard Edition	Select

	oracle-ee Oracle Database Enterprise Edition	Select
	sqlserver-ex Microsoft SQL Server Express Edition Note that SQL Server Express Edition limits the storage of per database to a maximum of 10GB. Refer to this link for more details.	Select

	sqlserver-web Microsof t SQL Server Web Edition Note that in accordance with Microsofts licensing policies, SQL Server Web Edition can only be used to support public and internet accessible Web pages, Websites, Web applications and Web services. Refer to the AWS Service Terms for more details.	Select
	sqlserver-se Microsoft SQL Server Standard Edition	Select

sqlserver-ee Microsoft SQL Server Enterprise Edition

Select

Do you plan to use this database for production purposes?

---

For databases used in production or pre-production we recommend:

• Multi-AZ Deployment for high availability (99.95% monthly up time SLA)
• Provisioned IOPS Storage for fast, consistent performance

Billing is based upon the RDS pricing table.
An instance which uses these features is not eligible for the RDS Free Usage Tier.

Yes, use Multi-AZ Deployment and Provisioned IOPS Storage as defaults while creating this instanceNo, this instance is intended for use outside of production or under the RDS Free Usage Tier

To get started, choose a DB engine below and click Next Step
DB Engine:   
mysql
License Model:               
DB Engine Version:               
DB Instance Class:               
Multi-AZ Deployment:               
Auto Minor Version Upgrade:    YesNo           
Provide the details for your RDS Database Instance.
Allocated Storage:*    GB        (Minimum: 5 GB, Maximum: 3072 GB) Higher allocated storage may improve IOPS performance.   
Use Provisioned IOPS:               
DB Instance Identifier:*            (e.g. mydbinstance)   
Master Username:*            (e.g. awsuser)   
Master Password:*            (e.g. mypassword)   

 

Provide the optional additional configuration details below.
Database Name:            (e.g. mydb)   
Note: if no database name is specified then no initial MySQL database will be created on the DB Instance.
Database Port:               
Choose a VPC:               
DB Subnet Group:               
Publicly Accessible:    YesNo           
Availability Zone:            MultiAZ deployment selected   
Option Group:               
If you have custom DB Parameter Groups or DB Security Groups you would like to associate with this DB Instance, select them below, otherwise proceed with default settings.
Parameter Group:               
VPC Security Group(s)

 

dth="600" height="317" />

Management Options

---

Enabled Automatic Backups:

YesNo

The number of days for which automated backups are retained.

Please note that automated backups are currently supported for InnoDB storage engine only. If you are using MyISAM, refer to detail here.

Backup Retention Period:

1234567891011121314151617181920212223242526272829303132333435days

The daily time range during which automated backups are created if automated backups are enabled

Backup Window:

Select WindowNo Preference

The weekly time range (in UTC) during which system maintenance can occur.

Maintenance Window:

Select WindowNo Preference

 

 

Review

---

Please review the information below, then click Launch DB Instance .

Engine:

mysql

Engine Version:

MySQL 5.6.13

License Model:

general-public-license

Auto Minor Version Upgrade:

Yes

DB Instance Class:

db.t1.micro

Multi-AZ Deployment:

Yes

Allocated Storage:

5

Provisioned IOPS:

0

DB Instance Identifier:

TestDBIns

Master User Name:

root

Master User Password:

********

---

Database Name:

TestDB

Database Port:

3306

Availability Zone:

Using a Multi-AZ Deployment disables this preference.

Option Group:

default:mysql-5-6

DB Parameter Group:

default.mysql5.6

VPC Security Group(s):

Web-SRV-Access (sg-dfcfd6bd)

DB Subnet Group:

default

Publicly Accessible:

No

---

Backup Retention Period:

10

Backup Window:

No Preference

Maintenance Window:

No Preference

 

Your DB instance is being created.

Note: Your DB instances may take a few minutes to launch.

› View your DB instances on the DB Instances page

---

Other RDS Features

DB Security Group

You will be unable to connect to your database instance unless you have previously authorized access on your chosen DB Security Group. The DB Security Groups page allows you to authorize and revoke access based on CIDR/IP or EC2/VPC Security Group.

› Go to the DB Security Groups Page

DB Snapshots

Create a backup of your DB Instance by taking a snapshot.

› Go to the DB Snapshots Page

---

Related AWS Services

Amazon Elasticache

Add a managed Memcached or Redis-compatible in-memory cache to speed up your database access.

› Click here to learn more and launch your Cache Cluster

---

 

 

 

Your account does not support the EC2-Classic Platform in this region. DB Security Groups are only needed when the EC2-Classic Platform is supported. Instead, use VPC Security Groups to control access to your DB Instances. Go to the EC2 Console to view and manage your VPC Security Groups. For more information, see AWS Documentation on Supported Platformsand Using RDS in VPC.

List all DB names along with basic details:

SQL> select DBID, NAME, OPEN_MODE from v$database;

      DBID NAME      OPEN_MODE
———- ——— ———-
2337018765 PRODDB01      READ WRITE

SQL>

 

List all DB names along with all details:

SQL> select * from v$database;

      DBID NAME      CREATED   RESETLOGS_CHANGE# RESETLOGS
———- ——— ——— —————– ———
PRIOR_RESETLOGS_CHANGE# PRIOR_RES LOG_MODE     CHECKPOINT_CHANGE#
———————– ——— ———— ——————
ARCHIVE_CHANGE# CONTROL CONTROLFI CONTROLFILE_SEQUENCE# CONTROLFILE_CHANGE#
————— ——- ——— ——————— ——————-
CONTROLFI OPEN_RESETL VERSION_T OPEN_MODE
——— ———– ——— ———-
2337018765 PRODDB01      11-AUG-06                 1 11-AUG-06
                      0           NOARCHIVELOG            5362658
        5321718 CURRENT 11-AUG-06                 33359             5362658
11-APR-14 NOT ALLOWED 11-AUG-06 READ WRITE

SQL>

 

List Instance names along with basic details:

SQL> select instance_name, status, database_status from v$instance;

INSTANCE_NAME STATUS DATABASE_STATUS

—————- ——- —————–

INS03 MOUNTED ACTIVE

SQL>

 

List Instance names along with all details:

SQL> select * from v$instance;

INSTANCE_NUMBER INSTANCE_NAME

————— —————-

HOST_NAME

—————————————————————-

VERSION STARTUP_T STATUS PAR THREAD# ARCHIVE LOG_SWITCH_

—————– ——— ——- — ———- ——- ———–

LOGINS SHU DATABASE_STATUS INSTANCE_ROLE

———- — —————– ——————

1 INS03

dev.test.lab

8.1.7.4.0 11-APR-14 OPEN NO 1 STOPPED

ALLOWED NO ACTIVE PRIMARY_INSTANCE

SQL>

 

List all Users in the DB:

SQL> select * from all_users;

USERNAME                          USER_ID CREATED
—————————— ———- ———
SYS                                     0 11-AUG-06
SYSTEM                                  5 11-AUG-06
OUTLN                                  11 11-AUG-06
DBSNMP                                 16 11-AUG-06
GINFOBOX                               20 11-AUG-06
APPSERV                                25 11-AUG-06

6 rows selected.

SQL>

 

List all Tables in the DB Or Search for specific tables:

SQL> SELECT table_name FROM user_tables;

TABLE_NAME
——————————
TABSUBPART$
TRIGGER$
TRIGGERCOL$
TRIGGERJAVAC$
TRIGGERJAVAF$
TRIGGERJAVAM$
TRIGGERJAVAS$
TRUSTED_LIST$
TS$
TSQ$
TYPE$

..

..

…

TABLE_NAME
——————————
_default_auditing_options_

166 rows selected.

SQL>