发布新帖

查找

问题
· 五月 9, 2024

Samples-FHIRStarter Questions

#FHIR #GitHub #REST API #Health Connect #InterSystems IRIS #InterSystems IRIS for Health

I am trying to create my first call to our Epic FHIR Repository from Health Connect using Samples-FHIRStarter now that I have OAuth2.0 connection tested/working with our Epic Interconnect URL.

When I take a patient example from our Epic environment and test it through Data.BPL.PatientRecordCollector within the Namespace, I keep getting a 404 - File or directory not found 

as it tells me it cannot find the patient. So, I know the connection is being established, I just can't see what is being sent to Epic to see if I could test it through Postman.

So, I enabled the following in the ISCLOG, however when I test, I am not seeing the information in the ISCLOG.

'

The ISCLOG is not being generated under %SYS after I have killed it from the previous attempts. How can I tell IRIS to log the Header and Request that is being made so I can ensure that I am making the correct connection to Epic Interconnect?

讨论 (0)1
登录或注册以继续
问题
· 五月 9, 2024

Erro em consultas após migração de servidor de banco de dados

#SQL #InterSystems IRIS

O nosso sistema funciona normalmente com a versão Iris 2023.2, porém foi necessário mudarmos de serviço de servidor cloud e ao migrar o banco para esse novo servidor e subir nossa aplicação começamos a receber alguns erros, que seguem abaixo:

Caused by: java.sql.SQLException: [SQLCODE: <-400>:<Ocorreu um erro fatal>]
11:12:26,663 INFO  [stdout] (http-/0.0.0.0:8443-17) [Location: <Prepare>]
11:12:26,664 INFO  [stdout] (http-/0.0.0.0:8443-17) [%msg: <Process 161341 failed to compile Cached Query Class %sqlcq.TGDB.cls789 with the following errors:  System:Instance: iris:IRIS, Namespace: TGDB, $Job: 161341
11:12:26,664 INFO  [stdout] (http-/0.0.0.0:8443-17) ERRO #5475: Erro durante a compilação da rotina '%sqlcq.TGDB.cls789'.  Erros:  %sqlcq.TGDB.cls789.cls
11:12:26,664 INFO  [stdout] (http-/0.0.0.0:8443-17) ERROR: %sqlcq.TGDB.cls789.1(20) : <UNDEFINED>fplanar+9^%qaqplansave *pdict("version") : 
11:12:26,664 INFO  [stdout] (http-/0.0.0.0:8443-17) ERRO #5475: Erro durante a compilação da rotina '%sqlcq.TGDB.cls789'.  Erros:  %sqlcq.TGDB.cls789.cls
11:12:26,664 INFO  [stdout] (http-/0.0.0.0:8443-17) ERROR: %sqlcq.TGDB.cls789.1(20) : <UNDEFINED>fplanar+9^%qaqplansave *pdict("version") : >]
11:12:26,664 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at com.intersystems.jdbc.IRISConnection.getServerError(IRISConnection.java:978) ~[na:na]
11:12:26,664 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at com.intersystems.jdbc.IRISConnection.processError(IRISConnection.java:1123) ~[na:na]
11:12:26,664 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at com.intersystems.jdbc.InStream.readMessage(InStream.java:216) ~[na:na]
11:12:26,664 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at com.intersystems.jdbc.InStream.readMessage(InStream.java:183) ~[na:na]
11:12:26,664 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at com.intersystems.jdbc.IRISPreparedStatement.prepareInternal(IRISPreparedStatement.java:597) ~[na:na]
11:12:26,664 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at com.intersystems.jdbc.IRISPreparedStatement.prepare(IRISPreparedStatement.java:558) ~[na:na]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at com.intersystems.jdbc.IRISPreparedStatement.<init>(IRISPreparedStatement.java:23) ~[na:na]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at com.intersystems.jdbc.IRISConnection.getOrCreatePossiblyShardedIRISPreparedStatement(IRISConnection.java:1893) ~[na:na]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at com.intersystems.jdbc.IRISConnection.prepareStatement(IRISConnection.java:1424) ~[na:na]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source) ~[na:na]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_331]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_331]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at net.bull.javamelody.JdbcWrapper$ConnectionInvocationHandler.invoke(JdbcWrapper.java:189) ~[javamelody-core-1.60.0.jar:1.60.0]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at net.bull.javamelody.JdbcWrapper$DelegatingInvocationHandler.invoke(JdbcWrapper.java:286) ~[javamelody-core-1.60.0.jar:1.60.0]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at com.sun.proxy.$Proxy566.prepareStatement(Unknown Source) ~[na:na]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.doPrepareStatement(BaseWrapperManagedConnection.java:748) ~[na:na]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.prepareStatement(BaseWrapperManagedConnection.java:734) ~[na:na]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at org.jboss.jca.adapters.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:405) ~[na:na]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at sun.reflect.GeneratedMethodAccessor69.invoke(Unknown Source) ~[na:na]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_331]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_331]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at org.springframework.jdbc.datasource.LazyConnectionDataSourceProxy$LazyConnectionInvocationHandler.invoke(LazyConnectionDataSourceProxy.java:376) ~[spring-jdbc-4.1.9.RELEASE.jar:4.1.9.RELEASE]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at com.sun.proxy.$Proxy73.prepareStatement(Unknown Source) ~[na:na]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$1.doPrepare(StatementPreparerImpl.java:96) ~[hibernate-core-4.2.19.Final.jar:4.2.19.Final]
11:12:26,665 INFO  [stdout] (http-/0.0.0.0:8443-17) 	at org.hibernate.engine.jdbc.internal.StatementPreparerImpl$StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:183) ~[hibernate-core-4.2.19.Final.jar:4.2.19.Final]

Vocês imaginam o que poderia ser o problema? Poderiam me dar algum auxílio?

Desde já muito obrigado.

8 Comments
讨论 (8)2
登录或注册以继续
讨论 (4)3
登录或注册以继续
文章
· 五月 9, 2024 阅读大约需 2 分钟

Notes on changing the system date for testing purposes

#系统管理 #提示和技巧 #InterSystems IRIS #InterSystems IRIS for Health

InterSystems FAQ rubric

If you change the system date, InterSystems Data Platform (IRIS) may not start properly.

IRIS performs a journal file deletion process when it starts, but if the system date is changed, a journal file with an incorrect date is created. During journal file deletion processing, the process proceeds by referring to the information of the previous and subsequent files recorded inside the journal file. Please note that if a change in the system date causes an inconsistency in the connection of journal files, the deletion process may go into a loop and the IRIS startup process may not be completed. Changing the system date can have various effects, not only on IRIS, but also on dependencies on the OS, middleware, and applications running on it.

If you must change the system date for testing or verification purposes, we recommend testing in an environment (virtual environment, etc.) where you can freely uninstall and reinstall IRIS.

The basic flow of the test is as follows.

  1. System date change
  2. Installing IRIS
  3. Test implementation
  4. Stopping IRIS
  5. Complete uninstallation of IRIS (*)
  6. Change system date (return to current date and time)
  7. Installing IRIS

(*) Even after uninstallation, some files will remain in the IRIS installation directory, so you will need to delete the entire IRIS installation folder.

If you perform a date change test in an environment where IRIS cannot be uninstalled or reinstalled, you may need to perform IRIS recovery work.

Please contact our Worldwide Responce Center for details.

讨论 (0)1
登录或注册以继续
公告
· 五月 9, 2024

Meet the trainers at Global Summit!

#Global Summit 2024 #学习门户

Spotlight on personal training, Global Summit. Sign up for a session with Joel Solon, Principal Technical Trainer.  

At Global Summit (June 9–12), you can meet one-on-one with our technical trainers!

💫This week the spotlight is on @Joel Solon, Principal Technical Trainer!

💭 Talk to him about InterSystems ObjectScript and system admin/mirroring/security.

In a 45-minute personal training session, you can refresh your memory on previous classroom training, discuss a technical concept, or start learning about InterSystems technologies.

📧 Email GSTechExchange@intersystems.com or visit the Tech Exchange concierge desk at the Summit.

讨论 (0)1
登录或注册以继续