Thursday, June 4, 2015

Create additional WebSphere application server profile


Assume you have installed WebSphere and Wanted to Create additional WebSphere Profile

1         Run the command “cd C:\Program Files\IBM\SDP\runtimes\base_v7\bin”

2         Once entered into the directory copy the below script and run it in command prompt.
manageProfiles -create -profileName was70profile2 -profilePath "C:\Program Files\IBM\SDP\runtimes\base_v7\profiles\was70profile2" -nodeName [NODENAME] -cellName [NODECELL Name] -hostname localhost -serverName server2 -startingPort 10000 -winserviceCheck false

                      

3         When the profile is complete the following message will appear in the command prompt
             
  

4         Open Servers View in RAD/Eclipse Window > Show View > Servers
5     Right click on the server and select New > Server


6  Change Server name and Click Next



7  Select profile which is created now (was70profile2)



8 Finish.

Initial App Set up for Facebook Share in Web Page



2. Go to My Apps tab Click Add a New App


3. Select Website, enter New app name in the text box (similar below) and click Create New
           Facebook App ID



4. Select appropriate category and test version app or not


5. Answer security check question and submit

6. Unique App Id will be created and need to enter Website URL and/or Mobile Site URL

(highlighted in yellow)

7. Click Next, that’s it. You have successfully Created your Test App

Twitter4j - java.security.cert.CertPathValidatorException: Certificate chaining error

SystemErr R com.ibm.jsse2.util.g: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: java.security.cert.CertPathValidatorException: The certificate issued by CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US is not trusted; internal cause is: java.security.cert.CertPathValidatorException: Certificate chaining error Relevant discussions can be found on the Internet at: http://www.google.co.jp/search?q=8e063946 or http://www.google.co.jp/search?q=c60cdc59 TwitterException{exceptionCode=[8e063946-c60cdc59 8e063946-c60cdc2f 8e063946-c60cdc2f 8e063946-c60cdc2f 8e063946-c60cdc2f 8e063946-c60cdc2f], statusCode=-1, message=null, code=-1, retryAfter=-1, rateLimitStatus=null, version=4.0.2} SystemErr R at twitter4j.HttpClientImpl.handleRequest(HttpClientImpl.java:178) SystemErr R at twitter4j.HttpClientBase.request(HttpClientBase.java:53) SystemErr R at twitter4j.HttpClientBase.post(HttpClientBase.java:82) SystemErr R at twitter4j.auth.OAuthAuthorization.getOAuthRequestToken(OAuthAuthorization.java:107) SystemErr R at twitter4j.auth.OAuthAuthorization.getOAuthRequestToken(OAuthAuthorization.java:92) SystemErr R at twitter4j.TwitterBaseImpl.getOAuthRequestToken(TwitterBaseImpl.java:263) SystemErr R Caused by: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: java.security.cert.CertPathValidatorException: The certificate issued by CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US is not trusted; internal cause is: java.security.cert.CertPathValidatorException: Certificate chaining error SystemErr R at com.ibm.jsse2.n.a(n.java:22) SystemErr R at com.ibm.jsse2.tc.a(tc.java:465) SystemErr R at com.ibm.jsse2.gb.a(gb.java:352) SystemErr R at com.ibm.jsse2.gb.a(gb.java:95) SystemErr R at com.ibm.jsse2.hb.a(hb.java:418) 

Described about the exception in the link (http://www-01.ibm.com/support/docview.wss?uid=swg21369939 ) How to add trust Store for twitter in Websphere

1. Open Administration console In Left Pane Security > SSL Certificate and key management > Key stores and certificates













2. Click on NodeDefaultTrustStore









3. Click on signer Certificates










4. Click Retrieve from port










5. Enter below details

Host: api.twitter.com
Port: 443
Alias: TwitterApi
Click Retrieve signer information.








6. Click Ok, Save and restart server