Tag: sourceedit |
Tag: sourceedit |
||
| (14 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | == |
+ | == touch down setting == |
| + | Please download Touchdown App from any local app store in the device. |
||
| − | [[rcom tips]] - rcom tips |
||
| − | * http://10.90.22.6/reutersmediawiki/index.php/BjMediaDev/SelfDev/Yufei_Ren/Tips - tips on media wiki |
||
| − | * https://thehub.thomsonreuters.com/docs/DOC-697156 - tips on thehub |
||
| + | Open the Airwatch agent, go to profiles > tap on Android exchange active sync profile > click on the refresh symbol and tap on re-apply until you get a pop-up to accept the agreement , accept the agreement and type in the exchange password and check if emails are synching in the touch down application. |
||
| − | ==switch rcom dev env == |
||
| − | * switch network use rcom dns |
||
| − | * switch maven settings.xml use rcom maven repo |
||
| + | if still emails are not synching.Restart the device and do the same procedure mentioned above |
||
| − | ==tips on original wiki == |
||
| − | http://10.90.22.6/reutersmediawiki/index.php/BjMediaDev/SelfDev/Yufei_Ren/Tips |
||
| − | |||
| − | ==foxyproxy addon set blacklist == |
||
| − | '''Please note that all patterns -- white and black -- are ignored when FoxyProxy is set to "Use proxy ABC for all URLs".''' |
||
| − | * http://getfoxyproxy.org/patterns.html |
||
| − | |||
| − | ==dig== |
||
| − | * use dig command to find the domain ip |
||
| − | dig preview.cn.mobile.reuters.com |
||
| − | ;; ANSWER SECTION: |
||
| − | preview.cn.mobile.reuters.com. 30 IN A 167.206.188.34 |
||
| − | |||
| − | ==check tomcat version== |
||
| − | /opt/tomcat/bin/version.sh |
||
| − | |||
| − | ==clear apache disk cache== |
||
| − | * clear apache disk cache, you may find apache cache in folder like: |
||
| − | /rt/apache/cache |
||
| − | |||
| − | ==Chrome tips == |
||
| − | ===view source === |
||
| − | * ctrl + u, check chrome source code (win, linux) |
||
| − | * option + command + u, view source (Mac) |
||
| − | |||
| − | ===open developer tools === |
||
| − | * f12, open chrome develop tools (win, linux) |
||
| − | * option + command + i , (mac) |
||
| − | |||
| − | ===chrome full screen === |
||
| − | * f11, chrome full screen (win, linux) |
||
| − | * ctrl + command + f , chrome full screen (mac), shift + command + f , presentation mode (mac) |
||
| − | |||
| − | ==akamai staging== |
||
| − | |||
| − | How to test using Akamai's Staging Network |
||
| − | |||
| − | Applies To |
||
| − | |||
| − | Description |
||
| − | |||
| − | How do I test using Akamai's Staging Network? |
||
| − | |||
| − | Akamai's Staging Network allows Akamai's customers to test configuration changes prior to going live on the Production Network. How exactly does one test from Staging? |
||
| − | |||
| − | Testing involves two steps: first, find a Staging IP, and second, spoof your domain to this IP and test whether or not your site or application behaves as expected. |
||
| − | |||
| − | 1) Here is how you find an Akamai Staging IP. Say, Akamai is serving your digital property www.foo.com. Typically, this digital property would be cnamed to an Edge Hostname such as www.foo.com.edgesuite.net or www.foo.com.edgekey.net. |
||
| − | |||
| − | (Note, if this is a new property that has not been Akamaized yet, this cname may not be in place yet. In this case, you will have to create an Edge Hostname to which you will be cnaming prior to running this test.) |
||
| − | |||
| − | $ dig www.foo.com |
||
| − | ;; ANSWER SECTION: |
||
| − | www.foo.com. 7200 IN CNAME www.foo.com.edgesuite.net. |
||
| − | www.foo.com.edgesuite.net. 1359 IN CNAME a1234.g.akamai.net. |
||
| − | |||
| − | To find a Staging IP, add "-staging" to your Edge Hostname as follows: |
||
| − | |||
| − | www.foo.com.edgesuite-staging.net or www.foo.com.edgekey-staging.net |
||
| − | |||
| − | Resolve the newly obtained hostname to find a Staging IP. |
||
| − | |||
| − | $ dig www.foo.com.edgesuite-staging.net |
||
| − | ;; ANSWER SECTION: |
||
| − | www.foo.com.edgesuite-staging.net. 1264 IN CNAME a1234.g.akamai-staging.net. |
||
| − | a1234.g.akamai-staging.net. 20 IN A 165.254.92.146 a1234.g.akamai-staging.net. 20 IN A 165.254.92.138 |
||
| − | |||
| − | The "-staging" Edge Hostnames are created automatically when the Production Edge Hostnames "www.foo.com.edgesuite.net" or "www.foo.com.edgekey.net" are created. As with production Edge Hostname, the "-staging" Edge Hostnames resolve to optimal Staging IPs. |
||
| − | |||
| − | 2) Once you have found a Staging IP, spoof www.foo.com to this IP and test your site or application as you would in Production. You can spoof by entering this domain and IP in your hosts file, or use testing tools such as curl, wfetch, or Akamai's homegrown tool EdgeSuite Booster available to download under Tools on the Luna Control Center. |
||
| − | |||
| − | Testing on Staging is strongly recommended when you make your own changes to your configuration. It is required when a change is implemented by Akamai. |
||
| − | |||
| − | You may also want to make sure that once you have correctly spoofed to the staging network, that your test requests are in fact going through it. KB Article 4856 explains these validation steps in further detail. |
||
| − | |||
| − | If you are trying to perform functional or A/B testing for users in China on a property subscribed to China CDN Service, KB 4651 describes special considerations for that testing scenario. |
||
| − | |||
| − | == image files in static server == |
||
| − | * image location , the "view" folder is large image |
||
| − | ** the "thumb" is small image, but seldom use. |
||
| − | /rt/shared/nas02/view/2015/03/30/106156436-1.JPG |
||
| − | |||
| − | * the admin box has write permission to /rt/shared/nas02 , other box can't |
||
| − | |||
| − | * the video image url like: http://10.35.60.120/resources/r/?d=20150330&i=106156436&w=161x90&r=106156436-1&t=2 |
||
| − | the param , i=106156436 , or r=106156436-1 is image name |
||
| − | the d=20150330 , is image folder |
||
Latest revision as of 08:09, 6 April 2017
touch down setting[]
Please download Touchdown App from any local app store in the device.
Open the Airwatch agent, go to profiles > tap on Android exchange active sync profile > click on the refresh symbol and tap on re-apply until you get a pop-up to accept the agreement , accept the agreement and type in the exchange password and check if emails are synching in the touch down application.
if still emails are not synching.Restart the device and do the same procedure mentioned above