Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry Push Development

Reply
Contributor
Posts: 14
Registered: ‎01-16-2011
My Device: 8520
Accepted Solution

how to set https in tomcat (BPSS SDK)

Hello Guys...

 

I am new in this tomcat setup, and trying to try the push SDK.

I have followed the http://supportforums.blackberry.com/t5/BlackBerry-Push-Development/Step-by-step-guide-for-the-PushSD... using windows7.

and

http://www.itworld.com/development/80705/how-enable-https-tomcat

 

but not able to make the https://localhost:443 works.

 

would you please anybody assist....

 

many thanks...

 

 

 

Developer
Posts: 235
Registered: ‎11-08-2010
My Device: Not Specified

Re: how to set https in tomcat (BPSS SDK)

Why doesn't it work? What problem or error are you having?

Contributor
Posts: 14
Registered: ‎01-16-2011
My Device: 8520

Re: how to set https in tomcat (BPSS SDK)

Thank for your reply Massimo,

 

I managed to run the localhost:8080,

but to htts://ip:8443 or 443, not able to acces.

the page show like the server offline.

I have check the xml setup, and make it 443, (because using the windows)

 

any other that I should check ?

 

thank.... Massimo...

 

Developer
Posts: 235
Registered: ‎11-08-2010
My Device: Not Specified

Re: how to set https in tomcat (BPSS SDK)

Is there a specfic error in the Tomcat logs?

 

What does your Tomcat conf/server.xml look like?

Contributor
Posts: 14
Registered: ‎01-16-2011
My Device: 8520

Re: how to set https in tomcat (BPSS SDK)

Hello Massimo,...

 

here the server.xml.

 

hope this able to see the problem.

 

thanks.. a lot...

 

 

 

 

--------

<?xml version='1.0' encoding='utf-8'?>
<!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
-->
<!-- Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" at this level.
     Documentation at /docs/config/server.html
 -->
<Server port="8005" shutdown="SHUTDOWN">

  <!--APR library loader. Documentation at /docs/apr.html -->
  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
  <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
  <Listener className="org.apache.catalina.core.JasperListener" />
  <!-- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html -->
  <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />

  <!-- Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
  -->
  <GlobalNamingResources>
    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    -->
    <Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" />
  </GlobalNamingResources>

  <!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" Note:  A "Service" is not itself a "Container",
       so you may not define subcomponents such as "Valves" at this level.
       Documentation at /docs/config/service.html
   -->
  <Service name="Catalina">
 
    <!--The connectors can use a shared executor, you can define one or more named thread pools-->
    <!--
    <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
        maxThreads="150" minSpareThreads="4"/>
    -->
    
    
    <!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8080
    -->
    <Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="443" useBodyEncodingForURI="true" />
    <!-- A "Connector" using the shared thread pool-->
    <!--
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="443" />
    -->           
    <!-- Define a SSL HTTP/1.1 Connector on port 443
         This connector uses the JSSE configuration, when using APR, the
         connector should be using the OpenSSL style configuration
         described in the APR documentation -->
    <Connector port="443" protocol="HTTP/1.1" SSLEnabled="true"
               maxThreads="150" scheme="https" secure="true"
               keystoreFile="keystores/.keystore" keystorePass="balioffice"
               clientAuth="false" sslProtocol="TLS" useBodyEncodingForURI="true" />

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009" protocol="AJP/1.3" redirectPort="443" />


    <!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host).
         Documentation at /docs/config/engine.html -->

    <!-- You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">         
    -->
    <Engine name="Catalina" defaultHost="localhost">

      <!--For clustering, please take a look at documentation at:
          /docs/cluster-howto.html  (simple how to)
          /docs/config/cluster.html (reference documentation) -->
      <!--
      <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
      -->        

      <!-- The request dumper valve dumps useful debugging information about
           the request and response data received and sent by Tomcat.
           Documentation at: /docs/config/valve.html -->
      <!--
      <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
      -->

      <!-- This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase".  Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm.  -->
      <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
             resourceName="UserDatabase"/>

      <!-- Define the default virtual host
           Note: XML Schema validation will not work with Xerces 2.2.
       -->
      <Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true"
            xmlValidation="false" xmlNamespaceAware="false">

        <!-- SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html -->
        <!--
        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
        -->

        <!-- Access log processes all example.
             Documentation at: /docs/config/valve.html -->
        <!-- Enable access logging for the push framework for debugging purposes -->    
        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"  
               prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/>

      </Host>
    </Engine>
  </Service>
</Server>

Developer
Posts: 235
Registered: ‎11-08-2010
My Device: Not Specified

Re: how to set https in tomcat (BPSS SDK)

your server.xml looks ok assuming you are accesing the page via:

 

https://localhost:443/sample-push-initiator

 

Not sure, could it be firewall related? Or perhaps your browser looks like an error because the certificate is not valid and you just have to continue through to the page (browser will give you a warning page and you have to accept the warning).

Highlighted
Contributor
Posts: 14
Registered: ‎01-16-2011
My Device: 8520

Re: how to set https in tomcat (BPSS SDK)

Many thanks Massimo,

 

after I check, I found the ssl certificate is not done yet,

so I follow http://techtracer.com/2007/09/12/setting-up-ssl-on-tomcat-in-3-easy-steps/

and now I can access the https and https://localhost/sample-push-initiator

 

Now I can try to play with this push next step.

Thanks.... a lot and rellay appriciate your assist.

 

 

Rudy