com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_link3' is unknown.

Upgrading from the Previous Release

Owned by Former user (Deleted)
Last updated: May 28, 2014
2 min read

This page takes you through the steps for upgrading from BAM 2.2.0 version to BAM 2.3.0. For more information on release versions, see the Release Matrix.

Preparing to upgrade

  1. Download WSO2 BAM 2.3.0.
  2. Back up your configurations from <BAM_HOME>/repository/conf/ directory of BAM 2.2.0.
  3. Replace the <BAM_HOME>/repository/conf/ directory of BAM 2.3.0, with the backup obtained in above step.

Configuration upgrades

Make changes in the files inside the <BAM_HOME>/repository/conf/ folder as follows:

Folder PathDescriptionRequired change
advanced/hive-site.xml
Change the value of the hive.jar.path property.

<value>${CARBON_HOME}/repository/components/plugins/hive_0.8.1.wso2v7.jar</value>


Change the value of the hive.aux.jars.path property.
<value>
file:///${CARBON_HOME}/repository/components/plugins/apache-cassandra_1.1.3.wso2v3.jar,
file:///${CARBON_HOME}/repository/components/plugins/guava_12.0.0.wso2v1.jar,
file:///${CARBON_HOME}/repository/components/plugins/json_2.0.0.wso2v1.jar,
file:///${CARBON_HOME}/repository/components/plugins/commons-dbcp_1.4.0.wso2v1.jar,
file:///${CARBON_HOME}/repository/components/plugins/commons-pool_1.5.6.wso2v1.jar
</value>
advanced/hive-site-win.xmlChange the value of the hive.jar.path property.<value>${CARBON_HOME}/repository/components/plugins/hive_0.8.1.wso2v7.jar</value>
Change the value of the hive.aux.jars.path property.
<value>
file:///${CARBON_HOME}/repository/components/plugins/apache-cassandra_1.1.3.wso2v3.jar,
file:///${CARBON_HOME}/repository/components/plugins/guava_12.0.0.wso2v1.jar,
file:///${CARBON_HOME}/repository/components/plugins/json_2.0.0.wso2v1.jar,
file:///${CARBON_HOME}/repository/components/plugins/commons-dbcp_1.4.0.wso2v1.jar,
file:///${CARBON_HOME}/repository/components/plugins/commons-pool_1.5.6.wso2v1.jar
</value>
data-bridge/data-bridge-config.xml

Modify the hostName element. This is a new configuration introduced in BAM 2.3.0.


<keySpaceName>EVENT_KS</keySpaceName>
<!-- Default configuration for thriftDataReceiver -->
	<thriftDataReceiver>
	<!--<hostName>localhost</hostName>-->
    	<port>7611</port>
    	<securePort>7711</securePort>
	</thriftDataReceiver>
datasources/master-datasource.xmlCassandra datasource is not supported in BAM 2.2.0, and this is a new configuration in BAM 2.3.0. You can specify Cassandra datasource in Hive queries after having this configuration.
<datasource>
        	<name>WSO2BAM_CASSANDRA_DATASOURCE</name>
        	<description>The datasource used for Cassandra data
             </description>
        	<definition type="RDBMS">
            	<configuration>
                	<url>jdbc:cassandra://localhost:9160/EVENT_KS
                    </url>
                	<username>admin</username>
                	<password>admin</password>
            	</configuration>
        	</definition>
    	</datasource>
etc/cache.xmlComment this line.<!-- <cacheManager>org.wso2.carbon.caching.core.ehcache.EhcacheManager</cacheManager> -->
Uncomment this line.<cacheManager>org.wso2.carbon.caching.infinispan.InfinispanCacheManager</cacheManager>
tomcat/carbon/META-INF/context.xmlAdd these new configurations that are introduced in BAM 2.3.0.
<Manager pathname="" />

	<JarScanner className="org.wso2.carbon.tomcat.ext.scan.CarbonTomcatJarScanner" scanClassPath="true" scanAllFiles="false" scanAllDirectories="false"/>
	 
	<!-- Following are default values. But we specifically add them in kernel, becuase they get overridden in WSO2 AS -->
	<Loader className="org.apache.catalina.loader.WebappLoader" loaderClass="org.apache.catalina.loader.WebappClassLoader" />
identity.xmlAdd these new configurations that are introduced in BAM 2.3.0.
</OAuthCallbackHandlers>

<!-- Assertions can be used to embedd parameters into access token. -->
   	 <EnableAssertions>
   		 <UserName>false</UserName>
   	 </EnableAssertions>
 
   	 <!-- This should be set to true when using multiple user stores and keys  
   		 should saved into different tables according to the user store. By default  
   		 all the application keys are saved in to the same table. UserName Assertion  
   		 should be 'true' to use this. -->
   	 <EnableAccessTokenPartitioning>false</EnableAccessTokenPartitioning>
   	 <!-- user store domain names and mapping to new table name. eg: if you  
   		 provide 'A:foo.com', foo.com should be the user store domain name and 'A'  
   		 represent the relavant mapping of token store table, i.e. tokens will be  
   		 added to a table called IDN_OAUTH2_ACCESS_TOKEN_A. -->
   	 <AccessTokenPartitioningDomains><!-- A:foo.com, B:bar.com -->
   	 </AccessTokenPartitioningDomains>
   	 <AuthorizationContextTokenGeneration>   	 
   		 <Enabled>true</Enabled>
   		 <TokenGeneratorImplClass>org.wso2.carbon.identity.oauth2.token.JWTTokenGenerator</TokenGeneratorImplClass>
   		 <ClaimsRetrieverImplClass>org.wso2.carbon.identity.oauth2.token.DefaultClaimsRetriever</ClaimsRetrieverImplClass>
   		 <ConsumerDialectURI>http://wso2.org/claims</ConsumerDialectURI>
   		 <SignatureAlgorithm>SHA256withRSA</SignatureAlgorithm>
   		 <AuthorizationContextTTL>15</AuthorizationContextTTL>
   	 </AuthorizationContextTokenGeneration>
</OAuth>


com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.