Topic
  • 10 replies
  • Latest Post - ‏2012-01-17T20:42:15Z by XHJV_Pramod_J
XHJV_Pramod_J
XHJV_Pramod_J
9 Posts

Pinned topic IBM Lotus mashups

‏2012-01-12T01:29:10Z |
Hello All,

I was able to access Lotus mashups and created a simple page which as shown in the example.

But for some reason when i stopped the server for creating a jdbc provider for SQL Server and restarted it, i am not able to access lotus mashups (i can login to Infosphere mashup center).

I get HTTP500 error. Can any one help me on this?
Thanks
Updated on 2012-01-17T20:42:15Z at 2012-01-17T20:42:15Z by XHJV_Pramod_J
  • Stan
    Stan
    340 Posts

    Re: IBM Lotus mashups

    ‏2012-01-12T02:08:59Z  
    Check the URL being used to connect to Mashup Builder. Make sure the host name and port (usually 9080) are correct. If the failure happens when you are trying to access Lotus Mashups from the Mashup Hub catalog page then goto the General Config Settings page of the Administratior Tasks list (click the SETTINGS link in the upper right portion of the page).

    Check the value for "Mashup Builder URL:" it should have the URL in the format: http://<myhost.mydomain>:<port>/mum

    If you still have problems post the URL that is giving you the error.
  • SystemAdmin
    SystemAdmin
    391 Posts

    Re: IBM Lotus mashups

    ‏2012-01-12T03:38:05Z  
    There might also be something in the SystemOut.log or SystemErr.log with a timestamp close to the time of attempted login.

    The 500 error can happen if the database did not initialize correctly via the scripts, or if content is missing.
    When the Lotus Mashups DB is created it is empty. and a part of the config task should have set some flags set to enable import of the spaces, themes and templates.

    If the logs indicate an error, let us know and we can give some procedures to try to correct that.
  • XHJV_Pramod_J
    XHJV_Pramod_J
    9 Posts

    Re: IBM Lotus mashups

    ‏2012-01-12T04:07:57Z  
    There might also be something in the SystemOut.log or SystemErr.log with a timestamp close to the time of attempted login.

    The 500 error can happen if the database did not initialize correctly via the scripts, or if content is missing.
    When the Lotus Mashups DB is created it is empty. and a part of the config task should have set some flags set to enable import of the spaces, themes and templates.

    If the logs indicate an error, let us know and we can give some procedures to try to correct that.
    Thanks Drik and Stan for your reply..

    I fixed by JDBC driver by
    1. Download SQL Server JDBC Driver Version 2.
    2. Copy sqljdbc4.jar to \Mashup Center\3.0\Config\lib\sqlserver and execute config.bat action-create-db-mashup-sqlserver.
    3. After this I see JDBC Provider in the admin console and i created a data source.

    Please let me know if i am missing any step..

    Following is the SystemOut.log

    com.ibm.mm.server.persistence.rdbms.dao.ibatis.BaseDao getAccountByExternalId BMWSD0429E: An SQLException was encountered while communicating with the database. Error code: 208, SQL State: S0002, Message:
    • The error occurred in com/ibm/mm/server/persistence/rdbms/resources/maps/Account.xml.
    • The error occurred while applying a parameter map.
    • Check the readAccountByExternalId-InlineParameterMap.
    • Check the statement (query failed).
    • Cause: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'MASHUPS.ACCOUNT'.
    com.ibatis.common.jdbc.exception.NestedSQLException:
    • The error occurred in com/ibm/mm/server/persistence/rdbms/resources/maps/Account.xml.
    • The error occurred while applying a parameter map.
    • Check the readAccountByExternalId-InlineParameterMap.
    • Check the statement (query failed).
    • Cause: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'MASHUPS.ACCOUNT'.
    at com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.executeQueryWithCallback(GeneralStatement.java:185)
    at com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.executeQueryForObject(GeneralStatement.java:104)
    at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForObject(SqlMapExecutorDelegate.java:566)
    at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForObject(SqlMapExecutorDelegate.java:541)
    at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.queryForObject(SqlMapSessionImpl.java:106)
    at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.queryForObject(SqlMapClientImpl.java:83)
    at com.ibm.mm.server.persistence.rdbms.dao.ibatis.LoggedSqlMapExecutor.queryForObject(LoggedSqlMapExecutor.java:191)
    at com.ibm.mm.server.persistence.rdbms.dao.ibatis.AccountDaoSqlMap.getAccountByExternalId(AccountDaoSqlMap.java:49)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:600)
    at com.ibatis.dao.engine.impl.DaoProxy.invoke(DaoProxy.java:64)
    at $Proxy45.getAccountByExternalId(Unknown Source)
    at com.ibm.mm.server.persistence.rdbms.service.ibatis.bo.AccountBoIbatis.getAccountByExternalId(AccountBoIbatis.java:46)
    at com.ibm.mm.server.persistence.rdbms.service.ibatis.bo.AccountBoIbatis.provisionAccount(AccountBoIbatis.java:61)
    at com.ibm.mm.server.persistence.rdbms.service.account.AccountInstanceHomeImplRdbms.provisionAccount(AccountInstanceHomeImplRdbms.java:126)
    at com.ibm.mm.was.user.service.handler.AbstractWASUserHandler.getInternalUniqueID(AbstractWASUserHandler.java:67)
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler.processUser(StandardSecureWIMHandler.java:769)
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler.processUserEntities(StandardSecureWIMHandler.java:338)
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler.runWimGetUsers(StandardSecureWIMHandler.java:247)
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler.findUserByUniqueName(StandardSecureWIMHandler.java:996)
    at com.ibm.mm.was.user.service.UserServiceImpl.findUserByUniqueName(UserServiceImpl.java:651)
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler.getCurrentUser(StandardSecureWIMHandler.java:947)
    at com.ibm.mm.was.user.service.UserServiceImpl.getCurrentUser(UserServiceImpl.java:779)
    at com.ibm.mm.server.model.user.UserModelProviderImpl.getCurrentUser(UserModelProviderImpl.java:174)
    at com.ibm.mm.framework.rest.next.servlet.ForwardServlet.service(ForwardServlet.java:273)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.ibm.mm.framework.internal.resources.ServletWrapper.service(ServletWrapper.java:90)
    at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:109)
    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.ibm.mm.was.MMOSGIBridgeServlet.service(MMOSGIBridgeServlet.java:239)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1655)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1595)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)
    at com.ibm.mm.was.filter.CompressionFilter.doFilter(CompressionFilter.java:123)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
    at com.ibm.mm.was.filter.CacheHeaderFilter.doFilter(CacheHeaderFilter.java:107)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
    at com.ibm.mm.was.filter.LoginFilter.doFilter(LoginFilter.java:40)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:932)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500)
    at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
    at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864)
    at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384)
    at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
    at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
    at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
    Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'MASHUPS.ACCOUNT'.
    at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1454)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:388)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:338)
    at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4026)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1416)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:185)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:160)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.execute(SQLServerPreparedStatement.java:320)
    at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecute(WSJdbcPreparedStatement.java:958)
    at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.execute(WSJdbcPreparedStatement.java:634)
    at com.ibatis.sqlmap.engine.execution.SqlExecutor.executeQuery(SqlExecutor.java:186)
    at com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.sqlExecuteQuery(GeneralStatement.java:205)
    at com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.executeQueryWithCallback(GeneralStatement.java:173)
    ... 66 more

    1/11/12 19:56:28:544 PST 0000001a servlet E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0068E: Uncaught exception created in one of the service methods of the servlet mmOSGI in application mm.was. Exception created : java.lang.RuntimeException: com.ibm.mm.server.model.user.exception.CannotLoadUserException: BMWSM0016E: The user data could not be loaded.
    at com.ibm.mm.server.model.user.UserModelProviderImpl.getCurrentUser(UserModelProviderImpl.java:177)
    at com.ibm.mm.framework.rest.next.servlet.ForwardServlet.service(ForwardServlet.java:273)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.ibm.mm.framework.internal.resources.ServletWrapper.service(ServletWrapper.java:90)
    at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:109)
    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.ibm.mm.was.MMOSGIBridgeServlet.service(MMOSGIBridgeServlet.java:239)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1655)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1595)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131)
    at com.ibm.mm.was.filter.CompressionFilter.doFilter(CompressionFilter.java:123)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
    at com.ibm.mm.was.filter.CacheHeaderFilter.doFilter(CacheHeaderFilter.java:107)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
    at com.ibm.mm.was.filter.LoginFilter.doFilter(LoginFilter.java:40)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:932)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:500)
    at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
    at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:864)
    at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:455)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:384)
    at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
    at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
    at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550)
    Caused by: com.ibm.mm.server.model.user.exception.CannotLoadUserException: BMWSM0016E: The user data could not be loaded.
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler.getCurrentUser(StandardSecureWIMHandler.java:956)
    at com.ibm.mm.was.user.service.UserServiceImpl.getCurrentUser(UserServiceImpl.java:779)
    at com.ibm.mm.server.model.user.UserModelProviderImpl.getCurrentUser(UserModelProviderImpl.java:174)
    ... 41 more
    Caused by: com.ibm.mm.server.model.user.exception.CannotLoadUserException: BMWSM0016E: The user data could not be loaded.
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler.findMembership(StandardSecureWIMHandler.java:1054)
    at com.ibm.mm.was.user.service.UserServiceImpl.findMembership(UserServiceImpl.java:585)
    at com.ibm.mm.was.user.service.UserServiceImpl.findUserByUniqueName(UserServiceImpl.java:654)
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler.getCurrentUser(StandardSecureWIMHandler.java:947)
    ... 43 more
    Caused by: com.ibm.mm.server.model.user.exception.CannotLoadUserException: BMWSM0016E: The user data could not be loaded.
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler.runWimGetMembership(StandardSecureWIMHandler.java:408)
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler.findMembership(StandardSecureWIMHandler.java:1051)
    ... 46 more
    Caused by: java.security.PrivilegedActionException: com.ibm.websphere.wim.exception.InvalidIdentifierException: CWWIM1010E The uniqueid = 'null', uniqueName = 'null' identifier is not valid.
    at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4645)
    at com.ibm.ws.security.auth.ContextManagerImpl.runAsSystem(ContextManagerImpl.java:4687)
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler.runWimGetMembership(StandardSecureWIMHandler.java:406)
    ... 47 more
    Caused by: com.ibm.websphere.wim.exception.InvalidIdentifierException: CWWIM1010E The uniqueid = 'null', uniqueName = 'null' identifier is not valid.
    at com.ibm.ws.wim.ProfileManager.getImpl(ProfileManager.java:1496)
    at com.ibm.ws.wim.ProfileManager.genericProfileManagerMethod(ProfileManager.java:303)
    at com.ibm.ws.wim.ProfileManager.get(ProfileManager.java:356)
    at com.ibm.websphere.wim.ServiceProvider.get(ServiceProvider.java:348)
    at com.ibm.websphere.wim.client.LocalServiceProvider.get(LocalServiceProvider.java:364)
    at com.ibm.mm.was.user.service.handler.StandardSecureWIMHandler$7.run(StandardSecureWIMHandler.java:400)
    at com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManagerImpl.java:4599)
    ... 49 more
  • XHJV_Pramod_J
    XHJV_Pramod_J
    9 Posts

    Re: IBM Lotus mashups

    ‏2012-01-12T18:11:20Z  
    • Stan
    • ‏2012-01-12T02:08:59Z
    Check the URL being used to connect to Mashup Builder. Make sure the host name and port (usually 9080) are correct. If the failure happens when you are trying to access Lotus Mashups from the Mashup Hub catalog page then goto the General Config Settings page of the Administratior Tasks list (click the SETTINGS link in the upper right portion of the page).

    Check the value for "Mashup Builder URL:" it should have the URL in the format: http://<myhost.mydomain>:<port>/mum

    If you still have problems post the URL that is giving you the error.
    Hello All,

    Can anyone help me with this issue...or do I need to do a re-install

    Thanks!
  • SystemAdmin
    SystemAdmin
    391 Posts

    Re: IBM Lotus mashups

    ‏2012-01-12T18:52:50Z  
    Hello All,

    Can anyone help me with this issue...or do I need to do a re-install

    Thanks!
    You should not have to reinstall mashups.
    If the ACCOUNT table is missing then i would suspect that the SQL scripts were not run or not configured correctly.
    Can you see in the database if there is an ACCOUNT table with the schema of MASHUPS.

    The task action-create-db-mashup-sqlserver will remove & create the datasource definition in WebSphere.
    It will also generate the scripts again. This is useful if for example the schema name was wrong, or the port, or password were incorrect.
    the config task can be rerun at any time and if the scripts are rerun as well the database is reinitialized.
  • XHJV_Pramod_J
    XHJV_Pramod_J
    9 Posts

    Re: IBM Lotus mashups

    ‏2012-01-12T19:18:38Z  
    You should not have to reinstall mashups.
    If the ACCOUNT table is missing then i would suspect that the SQL scripts were not run or not configured correctly.
    Can you see in the database if there is an ACCOUNT table with the schema of MASHUPS.

    The task action-create-db-mashup-sqlserver will remove & create the datasource definition in WebSphere.
    It will also generate the scripts again. This is useful if for example the schema name was wrong, or the port, or password were incorrect.
    the config task can be rerun at any time and if the scripts are rerun as well the database is reinitialized.
    Thanks for your reply Dirk.

    I still have the same issue.

    Can you please let me know how to validate config process. I do see under data sources, mashupDS and tested the connection its working fine, is there any other parameter which is to be validated.

    Thanks!
  • SystemAdmin
    SystemAdmin
    391 Posts

    Re: IBM Lotus mashups

    ‏2012-01-13T03:16:28Z  
    Thanks for your reply Dirk.

    I still have the same issue.

    Can you please let me know how to validate config process. I do see under data sources, mashupDS and tested the connection its working fine, is there any other parameter which is to be validated.

    Thanks!
    After the config task is run for action-create-db-mashup-sqlserver. There will be a set of scripts in this directory:
    <MashupCenter_install_root>\mm_profile\dbscripts\LotusMashups\SQLServer\<database_name>
    The createTable.sql script has statements which will create the ACCOUNT table.

    Did you have a change to run these scripts according to the instructions found here: http://www-10.lotus.com/ldd/mashupswiki.nsf/dx/Configuring_Microsoft_SQL_Server_for_Lotus_Mashups_imc3001
  • XHJV_Pramod_J
    XHJV_Pramod_J
    9 Posts

    Re: IBM Lotus mashups

    ‏2012-01-14T00:18:52Z  
    After the config task is run for action-create-db-mashup-sqlserver. There will be a set of scripts in this directory:
    <MashupCenter_install_root>\mm_profile\dbscripts\LotusMashups\SQLServer\<database_name>
    The createTable.sql script has statements which will create the ACCOUNT table.

    Did you have a change to run these scripts according to the instructions found here: http://www-10.lotus.com/ldd/mashupswiki.nsf/dx/Configuring_Microsoft_SQL_Server_for_Lotus_Mashups_imc3001
    Thanks for the reply Dirk..Can you please let me know how to connect to a database that is already created and contains the data (which should be displayed using widgets).
  • SystemAdmin
    SystemAdmin
    391 Posts

    Re: IBM Lotus mashups

    ‏2012-01-16T15:07:58Z  
    Thanks for the reply Dirk..Can you please let me know how to connect to a database that is already created and contains the data (which should be displayed using widgets).
    You can do one of two things.
    1) Rerun the config.bat action-create-db-mashup-sqlserver task. If the items in the database_sqlserver.properties are correct for the database you want, then this task will recreate the WebSphere datasource with the info needed to connect to the "new" database. The scripts to format the database will also be created, though they do not have to run it the database you want to use is properly formatted ant populated.
    2) Log into the WebSphere Integrated Console and update the mashupsDS datasource definitions to work with your new database. Usually this means you need to update the authentication info and perhaps the host, database name and port. Effectively you can use the items in database_sqlserver.properties as a checklist of items to look at.
  • XHJV_Pramod_J
    XHJV_Pramod_J
    9 Posts

    Re: IBM Lotus mashups

    ‏2012-01-17T20:42:15Z  
    You can do one of two things.
    1) Rerun the config.bat action-create-db-mashup-sqlserver task. If the items in the database_sqlserver.properties are correct for the database you want, then this task will recreate the WebSphere datasource with the info needed to connect to the "new" database. The scripts to format the database will also be created, though they do not have to run it the database you want to use is properly formatted ant populated.
    2) Log into the WebSphere Integrated Console and update the mashupsDS datasource definitions to work with your new database. Usually this means you need to update the authentication info and perhaps the host, database name and port. Effectively you can use the items in database_sqlserver.properties as a checklist of items to look at.
    Thanks Dirk...I have executed the .sql scripts in dbscripts folder to create mashups db, lotus mashups is working fine.